mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
synced 2024-12-28 16:52:18 +00:00
docs: net: bonding: fix typos
The bonding documentation had several "insure" which is not properly used in the context. Suggest to change to "ensure" to improve readability. Signed-off-by: shunlizhou <shunlizhou@aliyun.com> Link: https://patch.msgid.link/20241216135447.57681-1-shunlizhou@aliyun.com Signed-off-by: Jakub Kicinski <kuba@kernel.org>
This commit is contained in:
parent
c9cfced173
commit
65c233d8e3
@ -1963,7 +1963,7 @@ obtain its hardware address from the first slave, which might not
|
||||
match the hardware address of the VLAN interfaces (which was
|
||||
ultimately copied from an earlier slave).
|
||||
|
||||
There are two methods to insure that the VLAN device operates
|
||||
There are two methods to ensure that the VLAN device operates
|
||||
with the correct hardware address if all slaves are removed from a
|
||||
bond interface:
|
||||
|
||||
@ -2078,7 +2078,7 @@ as an unsolicited ARP reply (because ARP matches replies on an
|
||||
interface basis), and is discarded. The MII monitor is not affected
|
||||
by the state of the routing table.
|
||||
|
||||
The solution here is simply to insure that slaves do not have
|
||||
The solution here is simply to ensure that slaves do not have
|
||||
routes of their own, and if for some reason they must, those routes do
|
||||
not supersede routes of their master. This should generally be the
|
||||
case, but unusual configurations or errant manual or automatic static
|
||||
@ -2295,7 +2295,7 @@ active-backup:
|
||||
the switches have an ISL and play together well. If the
|
||||
network configuration is such that one switch is specifically
|
||||
a backup switch (e.g., has lower capacity, higher cost, etc),
|
||||
then the primary option can be used to insure that the
|
||||
then the primary option can be used to ensure that the
|
||||
preferred link is always used when it is available.
|
||||
|
||||
broadcast:
|
||||
@ -2322,7 +2322,7 @@ monitor can provide a higher level of reliability in detecting end to
|
||||
end connectivity failures (which may be caused by the failure of any
|
||||
individual component to pass traffic for any reason). Additionally,
|
||||
the ARP monitor should be configured with multiple targets (at least
|
||||
one for each switch in the network). This will insure that,
|
||||
one for each switch in the network). This will ensure that,
|
||||
regardless of which switch is active, the ARP monitor has a suitable
|
||||
target to query.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user