Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit c17cb8b5 authored by Masanari Iida's avatar Masanari Iida Committed by David S. Miller
Browse files

doc:net: Fix typo in Documentation/networking 



Correct spelling typo in Documentation/networking

Signed-off-by: default avatarMasanari Iida <standby24x7@gmail.com>
Acked-by: default avatarRandy Dunlap <rdunlap@infradead.org>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent b757a62e

Documentation/networking/dccp.txt

+2 −2
Original line number Diff line number Diff line
@@ -18,8 +18,8 @@ Introduction 
Datagram Congestion Control Protocol (DCCP) is an unreliable, connection

oriented protocol designed to solve issues present in UDP and TCP, particularly

for real-time and multimedia (streaming) traffic.

It divides into a base protocol (RFC 4340) and plugable congestion control

modules called CCIDs. Like plugable TCP congestion control, at least one CCID

It divides into a base protocol (RFC 4340) and pluggable congestion control

modules called CCIDs. Like pluggable TCP congestion control, at least one CCID

needs to be enabled in order for the protocol to function properly. In the Linux

implementation, this is the TCP-like CCID2 (RFC 4341). Additional CCIDs, such as

the TCP-friendly CCID3 (RFC 4342), are optional.

Documentation/networking/e100.txt

+1 −1
Original line number Diff line number Diff line
@@ -103,7 +103,7 @@ Additional Configurations 
  PRO/100 Family of Adapters is e100.



  As an example, if you install the e100 driver for two PRO/100 adapters

  (eth0 and eth1), add the following to a configuraton file in /etc/modprobe.d/

  (eth0 and eth1), add the following to a configuration file in /etc/modprobe.d/



       alias eth0 e100

       alias eth1 e100

Documentation/networking/ieee802154.txt

+2 −2
Original line number Diff line number Diff line
@@ -4,7 +4,7 @@ 


Introduction

============

The IEEE 802.15.4 working group focuses on standartization of bottom

The IEEE 802.15.4 working group focuses on standardization of bottom

two layers: Medium Access Control (MAC) and Physical (PHY). And there

are mainly two options available for upper layers:

 - ZigBee - proprietary protocol from ZigBee Alliance
@@ -66,7 +66,7 @@ net_device, with .type = ARPHRD_IEEE802154. Data is exchanged with socket family 
code via plain sk_buffs. On skb reception skb->cb must contain additional

info as described in the struct ieee802154_mac_cb. During packet transmission

the skb->cb is used to provide additional data to device's header_ops->create

function. Be aware, that this data can be overriden later (when socket code

function. Be aware that this data can be overridden later (when socket code

submits skb to qdisc), so if you need something from that cb later, you should

store info in the skb->data on your own.

Documentation/networking/l2tp.txt

+1 −1
Original line number Diff line number Diff line
@@ -197,7 +197,7 @@ state information because the file format is subject to change. It is 
implemented to provide extra debug information to help diagnose

problems.) Users should use the netlink API.



/proc/net/pppol2tp is also provided for backwards compaibility with

/proc/net/pppol2tp is also provided for backwards compatibility with

the original pppol2tp driver. It lists information about L2TPv2

tunnels and sessions only. Its use is discouraged.

Documentation/networking/netdev-FAQ.txt

+1 −1
Original line number Diff line number Diff line
@@ -68,7 +68,7 @@ A: To understand this, you need to know a bit of background information 


   The "net" tree continues to collect fixes for the vX.Y content, and

   is fed back to Linus at regular (~weekly) intervals.  Meaning that the

   focus for "net" is on stablilization and bugfixes.

   focus for "net" is on stabilization and bugfixes.



   Finally, the vX.Y gets released, and the whole cycle starts over.