Docs: udev.xml: Use normal sentence structure

[elogind.git] / udev / udev.xml

diff --git a/udev/udev.xml b/udev/udev.xml
index f472d9a7b8d4d759780d36a93c9f65080369e249..8cace1a1c68624186f55f54510d07f9b452390e3 100644 (file)
--- a/udev/udev.xml
+++ b/udev/udev.xml
@@ -501,7 +501,7 @@
               <varlistentry>
                 <term><option>static_node=</option></term>
                 <listitem>
-                  <para>Apply the permissions specified in this rule to a static device node with
+                  <para>Apply the permissions specified in this rule to the static device node with
                   the specified name. Static device nodes might be provided by kernel modules
                   or copied from <filename>/lib/udev/devices</filename>. These nodes might not have
                   a corresponding kernel device at the time udevd is started; they can trigger
@@ -528,10 +528,10 @@
 
       <para>The <option>NAME</option>, <option>SYMLINK</option>, <option>PROGRAM</option>,
       <option>OWNER</option>, <option>GROUP</option>, <option>MODE</option>  and  <option>RUN</option>
-      fields support simple printf-like string substitutions. The <option>RUN</option>
-      format chars gets applied after all rules have been processed, right before the program
-      is executed. It allows the use of device properties set by earlier matching
-      rules. For all other fields, substitutions are applied while the individual rule is
+      fields support simple string substitutions. The <option>RUN</option>
+      substitutions are performed after all rules have been processed, right before the program
+      is executed, allowing for the use of device properties set by earlier matching
+      rules. For all other fields, substitutions are performed while the individual rule is
       being processed. The available substitutions are:</para>
       <variablelist>
         <varlistentry>
@@ -580,8 +580,8 @@
             <para>The value of a sysfs attribute found at the device where
             all keys of the rule have matched. If the matching device does not have
             such an attribute, and a previous KERNELS, SUBSYSTEMS, DRIVERS, or
-            ATTRS test selected a parent device, use the attribute from that
-            parent device.
+            ATTRS test selected a parent device, then the attribute from that
+            parent device is used.
             If the attribute is a symlink, the last element of the symlink target is
             returned as the value.</para>
           </listitem>