diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:53:09 +0200 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:53:09 +0200 |
| commit | 84eb8d0608af1576175307ed8fb3c8fde329e579 (patch) | |
| tree | 13f3223e6907ebe309328d460fe51ce7ac346ae1 /Documentation/pm.txt | |
| parent | 992caacf1141b31e94540eb31e0540e3da3a5e25 (diff) | |
Fix "can not" in Documentation and Kconfig
Randy brought it to my attention that in proper english "can not" should always
be written "cannot". I donot see any reason to argue, even if I mightnot
understand why this rule exists. This patch fixes "can not" in several
Documentation files as well as three Kconfigs.
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/pm.txt')
| -rw-r--r-- | Documentation/pm.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/pm.txt b/Documentation/pm.txt index 79c0f32a760e..da8589a0e07d 100644 --- a/Documentation/pm.txt +++ b/Documentation/pm.txt @@ -18,10 +18,10 @@ enabled by default). If a working ACPI implementation is found, the ACPI driver will override and disable APM, otherwise the APM driver will be used. -No sorry, you can not have both ACPI and APM enabled and running at +No, sorry, you cannot have both ACPI and APM enabled and running at once. Some people with broken ACPI or broken APM implementations would like to use both to get a full set of working features, but you -simply can not mix and match the two. Only one power management +simply cannot mix and match the two. Only one power management interface can be in control of the machine at once. Think about it.. User-space Daemons @@ -106,7 +106,7 @@ void pm_unregister_all(pm_callback cback); * * Returns: 0 if the request is successful * EINVAL if the request is not supported - * EBUSY if the device is now busy and can not handle the request + * EBUSY if the device is now busy and cannot handle the request * ENOMEM if the device was unable to handle the request due to memory * * Details: The device request callback will be called before the |