diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:52:05 +0200 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:52:05 +0200 |
| commit | 992caacf1141b31e94540eb31e0540e3da3a5e25 (patch) | |
| tree | f50d22577c2dd45c31a8fe9e2f952b4a93a44249 /Documentation/power | |
| parent | 2fe0ae78c6975d6fa2fc0c84f2b8944543054105 (diff) | |
| download | linux-992caacf1141b31e94540eb31e0540e3da3a5e25.tar.bz2 | |
Fix typos in Documentation/: 'N'-'P'
This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letters 'N'-'P'.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/power')
| -rw-r--r-- | Documentation/power/userland-swsusp.txt | 2 | ||||
| -rw-r--r-- | Documentation/power/video.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/power/userland-swsusp.txt b/Documentation/power/userland-swsusp.txt index 94058220aaf0..64755e9285db 100644 --- a/Documentation/power/userland-swsusp.txt +++ b/Documentation/power/userland-swsusp.txt @@ -91,7 +91,7 @@ unfreeze user space processes frozen by SNAPSHOT_UNFREEZE if they are still frozen when the device is being closed). Currently it is assumed that the userland utilities reading/writing the -snapshot image from/to the kernel will use a swap parition, called the resume +snapshot image from/to the kernel will use a swap partition, called the resume partition, as storage space. However, this is not really required, as they can use, for example, a special (blank) suspend partition or a file on a partition that is unmounted before SNAPSHOT_ATOMIC_SNAPSHOT and mounted afterwards. diff --git a/Documentation/power/video.txt b/Documentation/power/video.txt index d859faa3a463..2b358498d095 100644 --- a/Documentation/power/video.txt +++ b/Documentation/power/video.txt @@ -16,7 +16,7 @@ problem for S1 standby, because hardware should retain its state over that. We either have to run video BIOS during early resume, or interpret it -using vbetool later, or maybe nothing is neccessary on particular +using vbetool later, or maybe nothing is necessary on particular system because video state is preserved. Unfortunately different methods work on different systems, and no known method suits all of them. |