diff options
author | Michael Biebl <mbiebl@gmail.com> | 2009-04-23 17:15:33 +0200 |
---|---|---|
committer | Michael Biebl <mbiebl@gmail.com> | 2009-04-23 17:15:33 +0200 |
commit | c66b32116b95a22beea22a9210241cf5244b3e47 (patch) | |
tree | cbd82922a9b0209835ff3ab63c64aeafee4995d8 | |
parent | e5cdb5bb6a573a36b0c872c889c8b8f25009cc45 (diff) |
Fix a few typos in the documentation
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525253
-rw-r--r-- | man/pm-action.xml | 4 | ||||
-rw-r--r-- | pm/HOWTO.hooks | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/man/pm-action.xml b/man/pm-action.xml index a6e064c..0bacca5 100644 --- a/man/pm-action.xml +++ b/man/pm-action.xml @@ -302,7 +302,7 @@ is specific to this system. The file will be saved in <filename>/etc/hal/fdi/information/99local-pm-utils-quirks.fdi</filename>. This parameter will only save the actual quirks that were - used to sucessfully suspend/resume a system -- if you are + used to successfully suspend/resume a system -- if you are running proprietary video drivers or kernel modesetting video drivers, you will generate a potentially incorrect .fdi file. @@ -492,7 +492,7 @@ <listitem> <para> If your system clock drifts across a suspend/resume or - hiberante/thaw cycle, you should set this to true. + hibernate/thaw cycle, you should set this to true. This will cause pm-utils to synchronize the system clock whenever we go through a sleep/wake cycle at the expense of making suspend/resume take longer. diff --git a/pm/HOWTO.hooks b/pm/HOWTO.hooks index a506759..ad7d4a7 100644 --- a/pm/HOWTO.hooks +++ b/pm/HOWTO.hooks @@ -43,7 +43,7 @@ In normal operation, hooks should only return either 0 or 254 as exit codes. Any other return code is interpreted by the pm-utils machinery as a signal from the hook that it should abort whatever it is doing. When running sleep.d hooks, that means that pm-utils stops running hooks, aborts the suspend/resume -process, calls any hooks that ran sucessfully prior to this one with the +process, calls any hooks that ran successfully prior to this one with the appropriate wakeup options, and exits with a non-zero exit code. When running power.d hooks, any hooks after this one will be skipped. |