man pages: fix typos

diff --git a/udev.7 b/udev.7
index eef10d4afb5b08c566c5fcf404eb82a6f3cded50..cef84de0411576c691762e706e7475a594bb3eb1 100644 (file)
--- a/udev.7
+++ b/udev.7
@@ -52,7 +52,7 @@ and
 .PP
 The udev rules are read from the files located in the
 \fI/etc/udev/rules.d\fR
 .PP
 The udev rules are read from the files located in the
 \fI/etc/udev/rules.d\fR

-directory or at the location specified value in the configuraton file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignement keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. A matching rule may specify the name of the device node, add a symlink pointing to the node, or run a specified program as part of the event handling. If no matching rule is found, the default device node name is used.
+directory or at the location specified value in the configuration file. Every line in the rules file contains at least one key value pair. There are two kind of keys, match and assignment keys. If all match keys are matching against its value, the rule gets applied and the assign keys get the specified value assigned. A matching rule may specify the name of the device node, add a symlink pointing to the node, or run a specified program as part of the event handling. If no matching rule is found, the default device node name is used.

 .PP
 A rule may consists of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are:
 .TP 3n
 .PP
 A rule may consists of a list of one or more key value pairs separated by a comma. Each key has a distinct operation, depending on the used operator. Valid operators are:
 .TP 3n


@@ -119,7 +119,7 @@ Matches zero, or any number of characters.
 Matches any single character.
 .TP 3n
 \fB[]\fR
 Matches any single character.
 .TP 3n
 \fB[]\fR

-Matches any single character specified within the brackets. example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. Ranges are also supported within this match with the '\-' character. For example, to match on the range of all digits, the pattern [0\-9] would be used. If the first character following the '[' is a '!', any characters not enclosed are matched.
+Matches any single character specified within the brackets. For example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'. Ranges are also supported within this match with the '\-' character. For example, to match on the range of all digits, the pattern [0\-9] would be used. If the first character following the '[' is a '!', any characters not enclosed are matched.

 .PP
 The following keys can get values assigned:
 .TP 3n
 .PP
 The following keys can get values assigned:
 .TP 3n


@@ -149,7 +149,7 @@ Import the printed result or the value of a file in environment key format into
 \fBprogram\fR
 will execute an external program and read its output.
 \fBfile\fR
 \fBprogram\fR
 will execute an external program and read its output.
 \fBfile\fR

-will inport a text file. If no option is given, udev will determine it from the executable bit of of the file permissions.
+will import a text file. If no option is given, udev will determine it from the executable bit of of the file permissions.

 .TP 3n
 \fBWAIT_FOR_SYSFS\fR
 Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues.
 .TP 3n
 \fBWAIT_FOR_SYSFS\fR
 Wait for the specified sysfs file of the device to be created. Can be used to fight against kernel sysfs timing issues.

diff --git a/udev.xml b/udev.xml
index 4896c2bb27e8a8abf8399a850eff457f085b4f75..01e9d522ed4d5f2b29499f875b565b65d1c3fa46 100644 (file)
--- a/udev.xml
+++ b/udev.xml
@@ -81,8 +81,8 @@
         <refsect2><title>Rules files</title>
           <para>The udev rules are read from the files located in the
           <filename>/etc/udev/rules.d</filename> directory or at the location specified
         <refsect2><title>Rules files</title>
           <para>The udev rules are read from the files located in the
           <filename>/etc/udev/rules.d</filename> directory or at the location specified

-          value in the configuraton file. Every line in the rules file contains at least
-          one key value pair. There are two kind of keys, match and assignement keys.
+          value in the configuration file. Every line in the rules file contains at least
+          one key value pair. There are two kind of keys, match and assignment keys.

           If all match keys are matching against its value, the rule gets applied and the
           assign keys get the specified value assigned. A matching rule may specify the
           name of the device node, add a symlink pointing to the node, or run a specified
           If all match keys are matching against its value, the rule gets applied and the
           assign keys get the specified value assigned. A matching rule may specify the
           name of the device node, add a symlink pointing to the node, or run a specified


@@ -238,7 +238,7 @@
             <varlistentry>
               <term><option>[]</option></term>
               <listitem>
             <varlistentry>
               <term><option>[]</option></term>
               <listitem>

-                <para>Matches any single character specified within the brackets.
+                <para>Matches any single character specified within the brackets. For

                 example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'.
                 Ranges are also supported within this match with the '-' character.
                 For example, to match on the range of all digits, the pattern [0-9] would
                 example, the pattern string 'tty[SR]' would match either 'ttyS' or 'ttyR'.
                 Ranges are also supported within this match with the '-' character.
                 For example, to match on the range of all digits, the pattern [0-9] would


@@ -315,7 +315,7 @@
               <listitem>
                 <para>Import the printed result or the value of a file in environment key
                 format into the event environment. <option>program</option> will execute an
               <listitem>
                 <para>Import the printed result or the value of a file in environment key
                 format into the event environment. <option>program</option> will execute an

-                external program and read its output. <option>file</option> will inport a
+                external program and read its output. <option>file</option> will import a

                 text file. If no option is given, udev will determine it from the  executable
                 bit of of the file permissions.</para>
               </listitem>
                 text file. If no option is given, udev will determine it from the  executable
                 bit of of the file permissions.</para>
               </listitem>

diff --git a/udevtest.8 b/udevtest.8
index da435bc4e44acf89af3b32b439150db02800f1d1..9e11f93b245aa4254e3f910efd3e1e1b38eed9c8 100644 (file)
--- a/udevtest.8
+++ b/udevtest.8
@@ -17,7 +17,7 @@ udevtest \- simulate a udev run and print the action to the console
 \fBudevtest \fR\fB\fIdevice\-path\fR\fR
 .SH "DESCRIPTION"
 .PP
 \fBudevtest \fR\fB\fIdevice\-path\fR\fR
 .SH "DESCRIPTION"
 .PP

-udevtest simulates a udev run for the given device and prints out the name of the node udev would have created, or the name of the network interface, that would have been renamend.
+udevtest simulates a udev run for the given device and prints out the name of the node udev would have created, or the name of the network interface, that would have been renamed.

 .SH "AUTHOR"
 .PP
 Written by Greg Kroah\-Hartman
 .SH "AUTHOR"
 .PP
 Written by Greg Kroah\-Hartman

diff --git a/udevtest.xml b/udevtest.xml
index 81f674da9d0844f554a712066ce99083294e03bb..259558dd5acad651338db88d8be4aa92b392aa60 100644 (file)
--- a/udevtest.xml
+++ b/udevtest.xml
@@ -32,7 +32,7 @@
       <refsect1><title>DESCRIPTION</title>
         <para>udevtest simulates a udev run for the given device and prints out the
         name of the node udev would have created, or the name of the network interface,
       <refsect1><title>DESCRIPTION</title>
         <para>udevtest simulates a udev run for the given device and prints out the
         name of the node udev would have created, or the name of the network interface,

-        that would have been renamend.</para>
+        that would have been renamed.</para>

       </refsect1>
 
       <refsect1><title>AUTHOR</title>
       </refsect1>
 
       <refsect1><title>AUTHOR</title>