[PATCH] Small textual improvements to wpa_supplicant man page

[Remco Rijnders]

Small textual improvements to wpa_supplicant man page

Signed-off-by: Remco Rijnders <remco at webconquest.com>
---
  .../doc/docbook/wpa_supplicant.sgml           | 32 +++++++++----------
  1 file changed, 16 insertions(+), 16 deletions(-)

diff --git a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
index 9a7d60119..241f80cfb 100644
--- a/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
+++ b/wpa_supplicant/doc/docbook/wpa_supplicant.sgml
@@ -29,8 +29,8 @@
      <title>Overview</title>

      <para>
-    Wireless networks do not require physical access to the network equipment
-    in the same way as wired networks. This makes it easier for unauthorized
+    Wireless networks do not require physical access to the network equipment in
+    the same way that wired networks do. This makes it easier for unauthorized
      users to passively monitor a network and capture all transmitted frames.
      In addition, unauthorized use of the network is much easier. In many cases,
      this can happen even without user's explicit knowledge since the wireless
@@ -41,15 +41,15 @@
      <para>
      Link-layer encryption can be used to provide a layer of security for
      wireless networks. The original wireless LAN standard, IEEE 802.11,
-    included a simple encryption mechanism, WEP. However, that proved to
-    be flawed in many areas and network protected with WEP cannot be consider
+    included a simple encryption mechanism, WEP. However, that proved to be
+    flawed in many areas and networks protected with WEP cannot be considered
      secure. IEEE 802.1X authentication and frequently changed dynamic WEP keys
      can be used to improve the network security, but even that has inherited
      security issues due to the use of WEP for encryption. Wi-Fi Protected
-    Access and IEEE 802.11i amendment to the wireless LAN standard introduce
-    a much improved mechanism for securing wireless networks. IEEE 802.11i
-    enabled networks that are using CCMP (encryption mechanism based on strong
-    cryptographic algorithm AES) can finally be called secure used for
+    Access and IEEE 802.11i amendments to the wireless LAN standard introduce a
+    much improved mechanism for securing wireless networks. IEEE 802.11i enabled
+    networks that are using CCMP (an encryption mechanism based on the strong
+    cryptographic algorithm AES) can finally be called secure and used for
      applications which require efficient protection against unauthorized
      access.
      </para>
@@ -70,13 +70,13 @@
      wpa_supplicant.</para>

      <para>Before wpa_supplicant can do its work, the network interface
-    must be available.  That means that the physical device must be
+    must be available. That means that the physical device must be
      present and enabled, and the driver for the device must be
      loaded. The daemon will exit immediately if the device is not already
      available.</para>

-    <para>After <command>wpa_supplicant</command> has configured the
-    network device, higher level configuration such as DHCP may
+    <para>After <command>wpa_supplicant</command> has configured the network
+    device, higher level configuration of the device, such as DHCP, may
      proceed.  There are a variety of ways to integrate wpa_supplicant
      into a machine's networking scripts, a few of which are described
      in sections below.</para>
@@ -87,7 +87,7 @@
      <itemizedlist>
        <listitem>
  	<para><command>wpa_supplicant</command> requests the kernel
-	driver to scan neighboring BSSes</para>
+	driver to scan neighboring BSSes (Basic Service Set)</para>
        </listitem>

        <listitem>
@@ -520,10 +520,10 @@
  wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0
  </programlisting></blockquote>

-    <para>This makes the process fork into background.</para>
+    <para>This makes the process fork into the background.</para>

-    <para>The easiest way to debug problems, and to get debug log for
-    bug reports, is to start <command>wpa_supplicant</command> on
+    <para>The easiest way to debug problems, and to get a debug log for
+    bug reports, is to start <command>wpa_supplicant</command> in the
      foreground with debugging enabled:</para>

  <blockquote><programlisting>
@@ -707,7 +707,7 @@ wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -B
    <refsect1>
      <title>Interface to pcmcia-cs/cardmrg</title>

-    <para>For example, following small changes to pcmcia-cs scripts
+    <para>For example, the following small changes to pcmcia-cs scripts
      can be used to enable WPA support:</para>

      <para>Add MODE="Managed" and WPA="y" to the network scheme in
--
2.38.2