Fix trivial typos in Kconfig* files

Fix several typos in help text in Kconfig* files.

Signed-off-by: David Sterba <dave@jikos.cz>
Signed-off-by: Adrian Bunk <bunk@stusta.de>

3 files changed, 4 insertions, 4 deletions

diff --git a/net/ipv4/Kconfig b/net/ipv4/Kconfig
index e62aee0ec4c5..c68196cc56ab 100644
--- a/net/ipv4/Kconfig
+++ b/net/ipv4/Kconfig
@@ -130,7 +130,7 @@ config IP_ROUTE_MULTIPATH_RR
         tristate "MULTIPATH: round robin algorithm"
         depends on IP_ROUTE_MULTIPATH_CACHED
         help
-          Mulitpath routes are chosen according to Round Robin
+          Multipath routes are chosen according to Round Robin
 
 config IP_ROUTE_MULTIPATH_RANDOM
         tristate "MULTIPATH: random algorithm"
@@ -651,7 +651,7 @@ config TCP_MD5SIG
         select CRYPTO
         select CRYPTO_MD5
         ---help---
-          RFC2385 specifices a method of giving MD5 protection to TCP sessions.
+          RFC2385 specifies a method of giving MD5 protection to TCP sessions.
           Its main (only?) use is to protect BGP sessions between core routers
           on the Internet.
 
diff --git a/net/ipv6/netfilter/Kconfig b/net/ipv6/netfilter/Kconfig
index bbe99f842f9f..838b8ddee8c0 100644
--- a/net/ipv6/netfilter/Kconfig
+++ b/net/ipv6/netfilter/Kconfig
@@ -28,7 +28,7 @@ config IP6_NF_QUEUE
           packets which enables users to receive the filtered packets
           with QUEUE target using libipq.
 
-          THis option enables the old IPv6-only "ip6_queue" implementation
+          This option enables the old IPv6-only "ip6_queue" implementation
           which has been obsoleted by the new "nfnetlink_queue" code (see
           CONFIG_NETFILTER_NETLINK_QUEUE).
 
diff --git a/net/netfilter/Kconfig b/net/netfilter/Kconfig
index ea6211cade0a..a567dae8e5fd 100644
--- a/net/netfilter/Kconfig
+++ b/net/netfilter/Kconfig
@@ -197,7 +197,7 @@ config NF_CONNTRACK_PPTP
 
           Please note that not all PPTP modes of operation are supported yet.
           Specifically these limitations exist:
-            - Blindy assumes that control connections are always established
+            - Blindly assumes that control connections are always established
               in PNS->PAC direction. This is a violation of RFC2637.
             - Only supports a single call within each session