Fix a few more speelling errors
Reviewed by: bjk Reviewed by: jilles (incl formal "accept") Differential Revision: https://reviews.freebsd.org/D13650
This commit is contained in:
parent
6134b18696
commit
837fe32558
@ -190,7 +190,7 @@ The
|
||||
.Fa ext[2]
|
||||
and
|
||||
.Fa ext[3]
|
||||
members are always passed throught the kernel as-is,
|
||||
members are always passed through the kernel as-is,
|
||||
making additional context available to application.
|
||||
.El
|
||||
.Pp
|
||||
|
@ -190,7 +190,7 @@ may read ahead when reading the file.
|
||||
A macro
|
||||
.Fn SF_FLAGS
|
||||
is provided to combine readahead amount and flags.
|
||||
Example shows specifing readahead of 16 pages and
|
||||
An example showing specifying readahead of 16 pages and
|
||||
.Dv SF_NOCACHE
|
||||
flag:
|
||||
.Pp
|
||||
|
@ -347,7 +347,7 @@ On success
|
||||
returns a pointer to the buffer; on failure it returns NULL.
|
||||
.Pp
|
||||
.Fn ibuf_dynamic
|
||||
allocates a resizeable buffer of initial length
|
||||
allocates a resizable buffer of initial length
|
||||
.Fa len
|
||||
and maximum size
|
||||
.Fa max .
|
||||
|
@ -3020,7 +3020,7 @@ supports in-kernel IPv6/IPv4 network address and protocol translation.
|
||||
Stateful NAT64 translation allows IPv6-only clients to contact IPv4 servers
|
||||
using unicast TCP, UDP or ICMP protocols.
|
||||
One or more IPv4 addresses assigned to a stateful NAT64 translator are shared
|
||||
among serveral IPv6-only clients.
|
||||
among several IPv6-only clients.
|
||||
When stateful NAT64 is used in conjunction with DNS64, no changes are usually
|
||||
required in the IPv6 client or the IPv4 server.
|
||||
The kernel module
|
||||
|
@ -2550,7 +2550,7 @@ While this is generally a feature
|
||||
as it allows for quick recovery if a server key has changed,
|
||||
a properly forged and appropriately delivered crypto\-NAK packet
|
||||
can be used in a DoS attack.
|
||||
If you have active noticable problems with this type of DoS attack
|
||||
If you have active noticeable problems with this type of DoS attack
|
||||
then you should consider
|
||||
disabling this option.
|
||||
You can check your
|
||||
@ -2598,7 +2598,7 @@ While this is generally a feature
|
||||
as it allows for quick recovery if a server key has changed,
|
||||
a properly forged and appropriately delivered crypto\-NAK packet
|
||||
can be used in a DoS attack.
|
||||
If you have active noticable problems with this type of DoS attack
|
||||
If you have active noticeable problems with this type of DoS attack
|
||||
then you should consider
|
||||
disabling this option.
|
||||
You can check your
|
||||
@ -2618,7 +2618,7 @@ While this is generally a feature
|
||||
as it allows for quick recovery,
|
||||
if this type of packet is carefully forged and sent
|
||||
during an appropriate window it can be used for a DoS attack.
|
||||
If you have active noticable problems with this type of DoS attack
|
||||
If you have active noticeable problems with this type of DoS attack
|
||||
then you should consider
|
||||
disabling this option.
|
||||
You can check your
|
||||
|
Loading…
Reference in New Issue
Block a user