fix typo in man page

Thanks to Frans Pop for the "patch".

2 files changed, 7 insertions, 7 deletions

diff --git a/docs/udev.xml b/docs/udev.xml
index 8c07f0e687..b2e2df0aa3 100644
--- a/docs/udev.xml
+++ b/docs/udev.xml
@@ -176,7 +176,7 @@
             <varlistentry>
               <term><option>BUS</option></term>
               <listitem>
-                <para>Match the typ of bus the device is connected to.</para>
+                <para>Match the type of bus the device is connected to.</para>
               </listitem>
             </varlistentry>
 
@@ -263,8 +263,8 @@
             <varlistentry>
               <term><option>NAME</option></term>
               <listitem>
-                <para>The name of the node to be created, or the name, the network interface
-                should be renamed to. Only one rule can set the a name, all later rules with
+                <para>The name of the node to be created, or the name the network interface
+                should be renamed to. Only one rule can set the node name, all later rules with
                 a NAME key will be ignored.</para>
               </listitem>
             </varlistentry>
@@ -282,7 +282,7 @@
             <varlistentry>
               <term><option>OWNER, GROUP, MODE</option></term>
               <listitem>
-                <para>The permissions for the device node. Every specified value over writes
+                <para>The permissions for the device node. Every specified value overwrites
                 the compiled-in default value.</para>
               </listitem>
             </varlistentry>
diff --git a/udev.8 b/udev.8
index c6ab83e805..4ca8107265 100644
--- a/udev.8
+++ b/udev.8
@@ -82,7 +82,7 @@ Match the kernel devpath.
 Match the kernel subsystem name
 .TP
 \fBBUS\fR
-Match the typ of bus the device is connected to.
+Match the type of bus the device is connected to.
 .TP
 \fBDRIVER\fR
 Match the kernel driver name.
@@ -116,13 +116,13 @@ Matches any single character specified within the brackets. example, the pattern
 The following keys can get values assigned:
 .TP
 \fBNAME\fR
-The name of the node to be created, or the name, the network interface should be renamed to. Only one rule can set the a name, all later rules with a NAME key will be ignored.
+The name of the node to be created, or the name the network interface should be renamed to. Only one rule can set the node name, all later rules with a NAME key will be ignored.
 .TP
 \fBSYMLINK\fR
 The name of a symlink targeting the node. Every matching rule can add this value to the list of symlinks to be created along with the device node. Multiple symlinks may be specified by separating the names by the space character.
 .TP
 \fBOWNER, GROUP, MODE\fR
-The permissions for the device node. Every specified value over writes the compiled\-in default value.
+The permissions for the device node. Every specified value overwrites the compiled\-in default value.
 .TP
 \fBENV{\fR\fB\fIkey\fR\fR\fB}\fR
 Export the key to the environment. Depending on the specified operation, this key is also used as a match.