On 11/22/2012 04:00 AM, Markus Becker wrote:
> Hi,
>
> just some small typo fixes in the documentation, that I stumbled over while 
> reading.
>
> --
> Markus
>
>
> Signed-off-by: Markus Becker <m...@comnets.uni-bremen.de>
> ---
>   Documentation/networking/ieee802154.txt |   28 ++++++++++++++--------------
>   1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/Documentation/networking/ieee802154.txt 
> b/Documentation/networking/ieee802154.txt
> index 703cf43..d8fefb3 100644
> --- a/Documentation/networking/ieee802154.txt
> +++ b/Documentation/networking/ieee802154.txt
> @@ -4,13 +4,13 @@
>   
>   Introduction
>   ============
> -The IEEE 802.15.4 working group focuses on standartization of bottom
> -two layers: Medium Accsess Control (MAC) and Physical (PHY). And there
> -are mainly two options available for upper layers:
> +The IEEE 802.15.4 working group focuses on standardization of the Medium
> +Access Control (MAC) and Physical (PHY) (sub-)layers. And there
> +are mainly two options available for the upper layers:
>    - ZigBee - proprietary protocol from ZigBee Alliance
>    - 6LowPAN - IPv6 networking over low rate personal area networks
>   
> -The Linux-ZigBee project goal is to provide complete implementation
> +The Linux-ZigBee project goal is to provide a complete implementation
>   of IEEE 802.15.4 and 6LoWPAN protocols. IEEE 802.15.4 is a stack
>   of protocols for organizing Low-Rate Wireless Personal Area Networks.
>   
> @@ -46,7 +46,7 @@ Like with WiFi, there are several types of devices 
> implementing IEEE 802.15.4.
>      possibly with some kinds of acceleration like automatic CRC computation 
> and
>      comparation, automagic ACK handling, address matching, etc.
>   
> -Those types of devices require different approach to be hooked into Linux 
> kernel.
> +Those types of devices require different approaches to be hooked into Linux 
> kernel.
>   
>   
>   MLME - MAC Level Management
> @@ -80,8 +80,8 @@ We provide an example of simple HardMAC driver at 
> drivers/ieee802154/fakehard.c
>   SoftMAC
>   =======
>   
> -The MAC is the middle layer in the IEEE 802.15.4 Linux stack. This moment it
> -provides interface for drivers registration and management of slave 
> interfaces.
> +The MAC is the middle layer in the IEEE 802.15.4 Linux stack. At the moment 
> it
> +provides interface for driver registration and management of slave 
> interfaces.
>   
>   NOTE: Currently the only monitor device type is supported - it's IEEE 
> 802.15.4
>   stack interface for network sniffers (e.g. WireShark).
> @@ -94,7 +94,7 @@ See header include/net/mac802154.h and several drivers in 
> drivers/ieee802154/.
>   Device drivers API
>   ==================
>   
> -The include/net/mac802154.h defines following functions:
> +The include/net/mac802154.h defines the following functions:
>    - struct ieee802154_dev *ieee802154_alloc_device
>      (size_t priv_size, struct ieee802154_ops *ops):
>      allocation of IEEE 802.15.4 compatible device
> @@ -115,8 +115,8 @@ Fake drivers
>   
>   In addition there are two drivers available which simulate real devices with
>   HardMAC (fakehard) and SoftMAC (fakelb - IEEE 802.15.4 loopback driver)
> -interfaces. This option provides possibility to test and debug stack without
> -usage of real hardware.
> +interfaces. This option provides a possibility to test and debug the stack
> +without usage of real hardware.
>   
>   See sources in drivers/ieee802154 folder for more details.
>   
> @@ -129,22 +129,22 @@ octets of actual MAC payload once security is turned 
> on, on a wireless link
>   with a link throughput of 250 kbps or less.  The 6LoWPAN adaptation format
>   [RFC4944] was specified to carry IPv6 datagrams over such constrained links,
>   taking into account limited bandwidth, memory, or energy resources that are
> -expected in applications such as wireless Sensor Networks.  [RFC4944] defines
> +expected in applications such as Wireless Sensor Networks.  [RFC4944] defines

"Wireless Sensor Networks" shouldn't be capitalized.

>   a Mesh Addressing header to support sub-IP forwarding, a Fragmentation 
> header
>   to support the IPv6 minimum MTU requirement [RFC2460], and stateless header
>   compression for IPv6 datagrams (LOWPAN_HC1 and LOWPAN_HC2) to reduce the
>   relatively large IPv6 and UDP headers down to (in the best case) several 
> bytes.
>   
> -In Semptember 2011 the standard update was published - [RFC6282].
> +In September 2011 the standard update was published - [RFC6282].
>   It deprecates HC1 and HC2 compression and defines IPHC encoding format 
> which is
>   used in this Linux implementation.
>   
>   All the code related to 6lowpan you may find in files: 
> net/ieee802154/6lowpan.*
>   
> -To setup 6lowpan interface you need (busybox release > 1.17.0):
> +To setup a 6lowpan interface you need (busybox release > 1.17.0):
>   1. Add IEEE802.15.4 interface and initialize PANid;
>   2. Add 6lowpan interface by command like:
>      # ip link add link wpan0 name lowpan0 type lowpan
> -3. Set MAC (if needs):
> +3. Set MAC (if needed):
>      # ip link set lowpan0 address de:ad:be:ef:ca:fe:ba:be
>   4. Bring up 'lowpan0' interface

Send this to the netdev mailing list. Also, use 
scripts/get_maintainer.pl to get a list of the people and mailing lists 
it should go to.

Alan.


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to