[patch] hb-net-wireless.xml.patch

hb-net-wireless.xml.patch (text/plain), 3.33 KB, created by Jan Kundrát (RETIRED) on 2006-01-07 14:36:45 UTC

Index: doc/en/handbook/hb-net-wireless.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-net-wireless.xml,v
retrieving revision 1.8
diff -u -b -B -r1.8 hb-net-wireless.xml
--- doc/en/handbook/hb-net-wireless.xml	23 Dec 2005 21:28:18 -0000	1.8
+++ doc/en/handbook/hb-net-wireless.xml	7 Jan 2006 22:33:44 -0000
@@ -8,7 +8,7 @@
 
 <sections>
 
-<version>1.3</version>
+<version>1.4</version>
 <date>2005-12-22</date>
 
 <section>
@@ -22,7 +22,7 @@
 </p>
 
 <p>
-<c>wpa_suppliant</c> is the best choice, but it does not support all drivers.
+<c>wpa_supplicant</c> is the best choice, but it does not support all drivers.
 For a list of supported drivers, <uri
 link="http://hostap.epitest.fi/wpa_supplicant">read the wpa_supplicant
 site</uri>. Also, <c>wpa_supplicant</c> can currently only connect to SSID's
@@ -35,12 +35,12 @@
 </p>
 
 <warn>
-The <c>linux-wlan-ng</c> driver is not supported by <c>baselayout</c> at this
+The <c>linux-wlan-ng</c> driver is not supported by baselayout at this
 time. This is because <c>linux-wlan-ng</c> have their own setup and
 configuration which is completely different to everyone else's. The
 <c>linux-wlan-ng</c> devs are rumoured to be changing their setup over to
 <c>wireless-tools</c> - when this happens you may use <c>linux-wlan-ng</c>
-with <c>baselayout</c>.
+with baselayout.
 </warn>
 
 </body>
@@ -82,7 +82,7 @@
 <note>
 If you're using the host-ap driver you will need to put the card in <e>Managed
 mode</e> before it can be used with <c>wpa_supplicant</c> correctly. You can use
-<e>iwconfig_eth0="mode managed"</e> to achieve this in
+<c>iwconfig_eth0="mode managed"</c> to achieve this in
 <path>/etc/conf.d/net</path>.
 </note>
 
@@ -205,7 +205,7 @@
 <note>
 Although you can store your wireless settings in
 <path>/etc/conf.d/wireless</path> this guide recommends you store them in
-<path>/etc/conf.d/net</path>
+<path>/etc/conf.d/net</path>.
 </note>
 
 <impo>
@@ -222,7 +222,9 @@
 # any time so we supply a default index of [1] to set key [1] and then
 # again afterwards to change the active key to [1]
 # We do this incase you define other ESSID's to use WEP keys other than 1
+#
 # Prefixing the key with s: means it's an ASCII key, otherwise a HEX key
+#
 # enc open specified open security (most secure)
 # enc restricted specified restricted security (least secure)</comment>
 key_ESSID1="[1] s:yourkeyhere key [1] enc open"
@@ -281,15 +283,15 @@
 </tr>
 <tr>
   <ti><c>forceany</c></ti>
-  <ti>Same as forcepreferred + connect to any other available AP</ti>
+  <ti>Same as <c>forcepreferred</c> + connect to any other available AP</ti>
 </tr>
 </table>
 
 <p>
 Finally we have some <c>blacklist_aps</c> and <c>unique_ap</c> selection.
 <c>blacklist_aps</c> works in a similar way to <c>preferred_aps</c>.
-<c>unique_ap</c> is a yes or no value that says if a second wireless interface
-can connect to the same Access Point as the first interface.
+<c>unique_ap</c> is a <c>yes</c> or <c>no</c> value that says if a second
+wireless interface can connect to the same Access Point as the first interface.
 </p>
 
 <pre caption="blacklist_aps and unique_ap example">
@@ -410,7 +412,7 @@
   <ti/>
   <ti>
     Some drivers have to scan in ad-hoc mode, so if scanning fails
-    try setting <c>ad-hoc</c> here
+    try setting <c>ad-hoc</c> here.
   </ti>
 </tr>
 <tr>