Lots of little typo errors on man pages.
Found by running codespell
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
- either 802.1Q or 802.1ad.
.BI id " VLANID "
-- specifies the VLAN Identifer to use. Note that numbers with a leading " 0 " or " 0x " are interpreted as octal or hexadeimal, respectively.
+- specifies the VLAN Identifier to use. Note that numbers with a leading " 0 " or " 0x " are interpreted as octal or hexadecimal, respectively.
.BR reorder_hdr " { " on " | " off " } "
- specifies whether ethernet headers are reordered or not (default is
.in +8
.sp
.BI id " VNI "
-- specifies the VXLAN Network Identifer (or VXLAN Segment
+- specifies the VXLAN Network Identifier (or VXLAN Segment
Identifier) to use.
.BI dev " PHYS_DEV"
.in +8
.sp
.BI id " VNI "
-- specifies the Virtual Network Identifer to use.
+- specifies the Virtual Network Identifier to use.
.sp
.BI remote " IPADDR"
.PP
.I "TYPE"
-specifies which help of link type to dislpay.
+specifies which help of link type to display.
.SS
.I GROUP
.SH NOTES
This tool can be used to configure the 802.1AE keys of the interface. Note that 802.1AE uses GCM-AES
with a initialization vector (IV) derived from the packet number. The same key must not be used
-with the same IV more than once. Instead, keys must be frequently regenerated and distibuted.
+with the same IV more than once. Instead, keys must be frequently regenerated and distributed.
This tool is thus mostly for debugging and testing, or in combination with a user-space application
that reconfigures the keys. It is wrong to just configure the keys statically and assume them to work
indefinitely. The suggested and standardized way for key management is 802.1X-2010, which is implemented
.TP
.BI proxy
-indicates whether we are proxying for this neigbour entry
+indicates whether we are proxying for this neighbour entry
.TP
.BI router
-indicates whether neigbour is a router
+indicates whether neighbour is a router
.TP
.BI extern_learn
.TP
.BI proxy
-indicates whether we should lookup a proxy neigbour entry
+indicates whether we should lookup a proxy neighbour entry
.TP
.BI to " ADDRESS " (default)
.P
.TP
.B <retrans>
-how many times the retransmission occured
+how many times the retransmission occurred
.RE
.TP
.B \-e, \-\-extended
.SH FLOW ISOLATION PARAMETERS
With flow isolation enabled, CAKE places packets from different flows into
different queues, each of which carries its own AQM state. Packets from each
-queue are then delivered fairly, according to a DRR++ algorithm which minimises
+queue are then delivered fairly, according to a DRR++ algorithm which minimizes
latency for "sparse" flows. CAKE uses a set-associative hashing algorithm to
-minimise flow collisions.
+minimize flow collisions.
These keywords specify whether fairness based on source address, destination
address, individual flows, or any combination of those is desired.
Remove any conntrack state and metadata (mark/label) from the packet (must only option specified).
.TP
.BI force
-Forces conntrack direction for a previously commited connections, so that current direction will become the original direction (only valid with commit).
+Forces conntrack direction for a previously committed connections, so that current direction will become the original direction (only valid with commit).
.SH EXAMPLES
Example showing natted firewall in conntrack zone 2, and conntrack mark usage:
.TQ
.IR \fBsrc_port " { " MASKED_NUMBER " | " " MIN_VALUE-MAX_VALUE " }
Match on layer 4 protocol source or destination port number, with an
-optional mask. Alternatively, the mininum and maximum values can be
+optional mask. Alternatively, the minimum and maximum values can be
specified to match on a range of layer 4 protocol source or destination
port numbers. Only available for
.BR ip_proto " values " udp ", " tcp " and " sctp
.RS
.TP
.I CT_STATE
-Match the connection state, and can ne combination of [{+|-}flag] flags, where flag can be one of
+Match the connection state, and can be combination of [{+|-}flag] flags, where flag can be one of
.RS
.TP
trk - Tracked connection.
.EE
.RE
-The first command creats an ingress qdisc with handle
+The first command creates an ingress qdisc with handle
.BR ffff:
on device
.BR eth1
.EE
.RE
-The first command creats an egress qdisc with handle
+The first command creates an egress qdisc with handle
.BR 1:
that replaces the root qdisc on device
.BR eth1
PIE is designed to control delay effectively. First, an average dequeue rate is
estimated based on the standing queue. The rate is used to calculate the current
delay. Then, on a periodic basis, the delay is used to calculate the dropping
-probabilty. Finally, on arrival, a packet is dropped (or marked) based on this
+probability. Finally, on arrival, a packet is dropped (or marked) based on this
probability.
PIE makes adjustments to the probability based on the trend of the delay i.e.
the deviation between the current and target latency changes probability. beta exerts
additional adjustments depending on the latency trend.
-The drop probabilty is used to mark packets in ecn mode. However, as in RED,
+The drop probability is used to mark packets in ecn mode. However, as in RED,
beyond 10% packets are dropped based on this probability. The bytemode is used
to drop packets proportional to the packet size.
.TP
max
Maximum length of a buckets queue, in packets, before packets start being
-dropped. Should be sightly larger than
+dropped. Should be slightly larger than
.B target
, but should not be set to values exceeding 1.5 times that of
.B target .
listed using a comma delimiter.
.TP
.B vxlan_opts
-Vxlan metatdata options.
+Vxlan metadata options.
.B vxlan_opts
is specified in the form GBP, as a 32bit number. Multiple options is not
supported.
.TP
.B erspan_opts
-Erspan metatdata options.
+Erspan metadata options.
.B erspan_opts
is specified in the form VERSION:INDEX:DIR:HWID, where VERSION is represented
as a 8bit number, INDEX as an 32bit number, DIR and HWID as a 8bit number.
projects / mirror_iproute2.git / commitdiff