man/systemd-hibernate-resume: generator now enables rather than creates the service

Follow-up for a628d933cc67cc8b183dc809ba1451aa5b2996e5

diff --git a/man/systemd-hibernate-resume-generator.xml b/man/systemd-hibernate-resume-generator.xml
index 6de5c19b5106dd0d114673d0a73cb20e3b009074..5adc14ee0025b914752eae33fbda08985ceda2d1 100644 (file)
--- a/man/systemd-hibernate-resume-generator.xml
+++ b/man/systemd-hibernate-resume-generator.xml
@@ -28,14 +28,11 @@
   <refsect1>
     <title>Description</title>
 
-    <para><command>systemd-hibernate-resume-generator</command> is a
-    generator that initiates the procedure to resume the system from hibernation.
-    It creates the
+    <para><command>systemd-hibernate-resume-generator</command> is a generator that initiates the procedure
+    to resume the system from hibernation. When <option>resume=</option> kernel command line option or
+    <varname>HibernateLocation</varname> EFI variable is detected, it enables the
     <citerefentry><refentrytitle>systemd-hibernate-resume.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
-    unit according to the value of <option>resume=</option> parameter
-    specified on the kernel command line, or the value of EFI variable
-    <varname>HibernateLocation</varname>, which will instruct the kernel
-    to resume the system from the hibernation image on that device.</para>
+    unit, which will instruct the kernel to resume the system from the hibernation image.</para>
   </refsect1>
 
   <refsect1>

diff --git a/man/systemd-hibernate-resume.service.xml b/man/systemd-hibernate-resume.service.xml
index 6bbce20000078c219ef4722b08bf2850c7f49cd7..f6cdefdd3a0fb6fe3e7b6533080ead8daa581adf 100644 (file)
--- a/man/systemd-hibernate-resume.service.xml
+++ b/man/systemd-hibernate-resume.service.xml
@@ -33,7 +33,7 @@
 
     <para><command>systemd-hibernate-resume</command> only supports the in-kernel hibernation
     implementation, see <ulink url="https://docs.kernel.org/power/swsusp.html">Swap suspend</ulink>.
-    Internally, it works by writing the major:minor of specified device node to
+    Internally, it works by writing the major:minor of selected device node to
     <filename>/sys/power/resume</filename>, along with the offset in memory pages
     (<filename>/sys/power/resume_offset</filename>) if supported.</para>