summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDuncan Roe <duncan_roe@optusnet.com.au>2018-08-07 13:54:01 +1000
committerPablo Neira Ayuso <pablo@netfilter.org>2018-08-07 18:12:07 +0200
commita02bcd16560c495600e55326b113663dbab627cf (patch)
treeb943cece3e93159ce41045f97df1dd7c89111269
parent5d27a91422f74bdc368256ec4087fe30e6f5d73d (diff)
doc: user niggles
- data-types.txt: "user space" -> userspace to match usage in statements.txt & data-types.txt - nft.txt: "an user-defined" sounds odd to a native English speaker (trust me) so change to "a user-defined" These patches are applied on top of Máté's previous 2, but apply fine without them (2 occurrences of "offset -5 lines"). Signed-off-by: Duncan Roe <duncan_roe@optusnet.com.au> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
-rw-r--r--doc/data-types.txt2
-rw-r--r--doc/nft.txt6
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/data-types.txt b/doc/data-types.txt
index 7a02a21a..1d46bdc0 100644
--- a/doc/data-types.txt
+++ b/doc/data-types.txt
@@ -136,7 +136,7 @@ boolean |
integer
|===================
-The boolean type is a syntactical helper type in user space. It's use is in the
+The boolean type is a syntactical helper type in userspace. It's use is in the
right-hand side of a (typically implicit) relational expression to change the
expression on the left-hand side into a boolean check (usually for existence). +
diff --git a/doc/nft.txt b/doc/nft.txt
index 703cca18..5b477d86 100644
--- a/doc/nft.txt
+++ b/doc/nft.txt
@@ -443,8 +443,8 @@ add *set* ['family'] 'table' 'set' { type 'type' ; [flags 'flags' ;] [timeout 't
delete *set* ['family'] 'table' handle 'handle'
{add | delete} *element* ['family'] 'table' 'set' { 'element'[,...] }
-Sets are elements containers of an user-defined data type, they are uniquely
-identified by an user-defined name and attached to tables. Their behaviour can
+Sets are elements containers of a user-defined data type, they are uniquely
+identified by a user-defined name and attached to tables. Their behaviour can
be tuned with the flags that can be specified at set creation time.
[horizontal]
@@ -493,7 +493,7 @@ add *map* ['family'] 'table' 'map' { type 'type' [flags 'flags' ;] [elements = {
{delete | list | flush} *map* ['family'] 'table' 'map'
{add | delete} *element* ['family'] 'table' 'map' { elements = { 'elements'[,...] } ; }
-Maps store data based on some specific key used as input, they are uniquely identified by an user-defined name and attached to tables.
+Maps store data based on some specific key used as input, they are uniquely identified by a user-defined name and attached to tables.
[horizontal]
*add*:: Add a new map in the specified table.