doc: fix some man-page mistakes

Correct one typo and two non-native usages.

Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
Signed-off-by: Florian Westphal <fw@strlen.de>

diff --git a/doc/nft.txt b/doc/nft.txt
index 7d01163e1deff5589eb800597f0dc84fcf99aaf1..b1f7a83aeb78a7e054991973c674c1b21fc03473 100644 (file)
--- a/doc/nft.txt
+++ b/doc/nft.txt
@@ -810,7 +810,7 @@ map policy |
 string: performance [default], memory
 |=================
 
-Users can specifiy the properties/features that the set/map must support.
+Users can specify the properties/features that the set/map must support.
 This allows the kernel to pick an optimal internal representation.
 If a required flag is missing, the ruleset might still work, as
 nftables will auto-enable features if it can infer this from the ruleset.

diff --git a/doc/payload-expression.txt b/doc/payload-expression.txt
index ce0c6a237db9f95ed9f0a55714d9ebcabd6fcade..351c79bce310dfaae49a3b074afbcbe789fdb65b 100644 (file)
--- a/doc/payload-expression.txt
+++ b/doc/payload-expression.txt
@@ -562,7 +562,7 @@ GRE HEADER EXPRESSION
 *gre* *ip6* {*version* | *dscp* | *ecn* | *flowlabel* | *length* | *nexthdr* | *hoplimit* | *saddr* | *daddr*}
 
 The gre expression is used to match on the gre header fields. This expression
-also allows to match on the IPv4 or IPv6 packet within the gre header.
+also allows one to match on the IPv4 or IPv6 packet within the gre header.
 
 .GRE header expression
 [options="header"]

diff --git a/doc/statements.txt b/doc/statements.txt
index 3475ef4e1a3c8bedca0d3b262bebc69685e1c80f..0b14398117de6a307428a5eaeed9d4c5809241e9 100644 (file)
--- a/doc/statements.txt
+++ b/doc/statements.txt
@@ -469,7 +469,7 @@ Before kernel 4.18 nat statements require both prerouting and postrouting base c
 to be present since otherwise packets on the return path won't be seen by
 netfilter and therefore no reverse translation will take place.
 
-The optional *prefix* keyword allows to map *n* source addresses to *n*
+The optional *prefix* keyword allows one to map *n* source addresses to *n*
 destination addresses.  See 'Advanced NAT examples' below.
 
 If the 'address' for *dnat* is an IPv4 loopback address