Fix typos

[madwifi/.git] / README

diff --git a/README b/README
index 11fc1b949034361894b2bd4c248f3c2634924802..f4f74d694dd2bf2ca93c1029f82b1bac88ff1a96 100644 (file)
--- a/README
+++ b/README
@@ -1,5 +1,5 @@
-MADWIFI: Multimode Atheros Driver for WiFi on Linux (VAP branch)
-================================================================
+MADWIFI: Multimode Atheros Driver for WiFi on Linux
+===================================================
 
 * Copyright (c) 2002-2005 Sam Leffler.  All rights reserved.
 
@@ -44,9 +44,9 @@ support needed by any 802.11 device.  This code is derived from work
 that first appeared in NetBSD and then FreeBSD.  The wlan module may
 also force the loading of additional modules for crypto support
 (wlan_wep, wlan_tkip, wlan_ccmp, etc.), for MAC-based ACL support
-(wlan_acl), and for 802.1x authenticator support (wlan_auth,
-wlan_radius).  The latter modules are only used when operating as an AP. 
-The crypto modules are loaded when keys of that type are created.
+(wlan_acl), and for 802.1x authenticator support (wlan_xauth).  The 
+latter modules are only used when operating as an AP.  The crypto 
+modules are loaded when keys of that type are created.
 
 The ath_hal module contains the Atheros Hardware Access Layer (HAL).
 This code manages much of the chip-specific operation of the driver. 
@@ -64,7 +64,7 @@ binary-only form it is marked "Proprietary"; this means when you load it
 you will see messages that your system is now "tainted".
 
 A detailed discussion of the pros and cons of this design can be found
-at http://madwifi.org/wiki/HAL
+at http://madwifi-project.org/wiki/HAL
 
 If you wish to use this driver on a platform for which an ath_hal module
 is not already provided please contact the author.  Note that this is
@@ -95,7 +95,7 @@ http://customerproducts.atheros.com/customerproducts
 
 A list of products that have been reported to be supported by MadWifi
 can be found here:
-http://madwifi.org/wiki/Compatibility
+http://madwifi-project.org/wiki/Compatibility
 
 In general, if a device is identified as ``11a only'', it is almost
 certain to contain an Atheros 5210 part in it.  Most retail a+b products
@@ -107,7 +107,7 @@ the PCI vendor ID with a tool like lspci, the Atheros vendor ID is
   00:13.0 Ethernet controller: Unknown device 168c:0012 (rev 01)
 
 but beware that some vendors use alternate vendor IDs (e.g 3Com, IBM).
-The file hal/ah_devid.h has a list of known PCI IDs.
+The file ath_hal/ah_devid.h has a list of known PCI IDs.
 
 
 Building the driver
@@ -167,7 +167,7 @@ Autocreation can be disabled:
   modprobe ath_pci autocreate=none
 
 Please see the following link for more information:
-http://madwifi.org/wiki/UserDocs/autocreate
+http://madwifi-project.org/wiki/UserDocs/autocreate
 
 
 Virtual APs (VAPs) and wlanconfig
@@ -192,13 +192,17 @@ To create an access point, use:
 To create an access point and a station, use:
 
   wlanconfig ath0 create wlandev wifi0 wlanmode ap
-  wlanconfig ath1 create wlandev wifi0 wlanmode sta nosbeacon
+  wlanconfig ath1 create wlandev wifi0 wlanmode sta
 
-To create APs that share a single MAC address, use the -bssid flag when
-creating the VAPs:
+To create APs that share a single MAC address, just create the VAPs:
 
-  wlanconfig ath0 create wlandev wifi0 wlanmode ap -bssid
-  wlanconfig ath1 create wlandev wifi0 wlanmode ap -bssid
+  wlanconfig ath0 create wlandev wifi0 wlanmode ap
+  wlanconfig ath1 create wlandev wifi0 wlanmode ap
+
+To create an VAP with a unique MAC address, use the bssid parameter:
+
+  wlanconfig ath0 create wlandev wifi0 wlanmode ap
+  wlanconfig ath1 create wlandev wifi0 wlanmode ap bssid
 
 Finally, to destroy a VAP, issue the command:
 
@@ -253,7 +257,7 @@ summary of all non-zero statistics from the time the driver was loaded.
 By default the ath0 device is used; to override this use the -i option.
 
 A wiki page describes common MadWifi debugging methods here:
-http://madwifi.org/wiki/DevDocs/AthDebug
+http://madwifi-project.org/wiki/DevDocs/AthDebug
 
 
 Security/Crypto Support
@@ -325,7 +329,7 @@ Known Problems
 1. Ad-hoc mode is broken; symptoms are intermittent operation.
 
 Other issues might be mentioned in our ticket tracker:
-http://madwifi.org/report/1
+http://madwifi-project.org/report/1
 
 
 Getting Support
@@ -343,7 +347,7 @@ sending your request (see below).
 We also offer an IRC channel that might be a better help in urgent
 cases.  Learn more about the different ways to get support by visiting:
 
-  http://madwifi.org/wiki/Support
+  http://madwifi-project.org/wiki/Support
 
 When sending a support request or problem report be sure to include the
 version of the driver and the part identification the driver prints to
@@ -372,6 +376,6 @@ Feedback and Contributions
 Reports about reproducible bugs, feature requests and patches should be
 submitted in the form of a trouble ticket:
 
-  http://madwifi.org/newticket
+  http://madwifi-project.org/wiki/TicketSubmissionGuidelines
         
 Fixes and enhancements are encouraged.