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>

diff --git a/doc/data-types.txt b/doc/data-types.txt
index 7a02a21a0d2876b36b27b2d62175bcb22f5491c0..1d46bdc079f62e7b1297feb4f56c14e9c3f6ea55 100644 (file)
--- 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 703cca18c84c10d95a1891c947cfa77b19e2262a..5b477d862d8690d9095e1a9ac39848078ffc2496 100644 (file)
--- 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.