[PATCH 12/12] Doc: change 'than' to 'as' where appropriate

[John Darrington]

---
 doc/poke.texi | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/doc/poke.texi b/doc/poke.texi
index fd441f8..25217a8 100644
--- a/doc/poke.texi
+++ b/doc/poke.texi
@@ -350,7 +350,7 @@ using comma characters (@code{,}).  Spaces are generally 
ignored.
 @subsection Commands
 @cindex commands
 Regular poke commands are written in Poke and use different
-conventions.  The name of commands follow the same rules than normal
+conventions.  The name of commands follow the same rules as normal
 Poke identifiers, and do not start with a dot character.
 
 An example is the @command{dump} command:
@@ -872,9 +872,9 @@ minus operator as explained below.  Therefore the minus 
symbol
 @subsection The digits separator @code{_}
 @cindex digits separator
 @cindex separator, digits separator
-The character @code{_} can appear anywhere in a numeric literal other
-than leading them.  It is ignored, and its purpose is to make it
-easier for programmers to read them:
+The character @code{_} can appear anywhere in a numeric literal
+except as the first character.  It is ignored, and its purpose is to
+make it easier for programmers to read them:
 
 @example
 0xf000_0000_0000_0000
@@ -913,7 +913,7 @@ explicitly specified using the suffix @code{u} or @code{U} 
(the
 default are signed types).  For example @code{0xffff_ffffU} has type
 @code{uint<32>} and @code{0ub} has type @code{uint<8>}.  It is possible
 to combine width-indicating suffixes with signedness suffixes:
-@code{10UL} denotes the same literal than @code{10LU}.
+@code{10UL} denotes the same literal as @code{10LU}.
 
 The above rules guarantee that it is always possible to determine the
 width and signedness of an integer constant just by looking at it,
@@ -1569,7 +1569,7 @@ Examples:
 0#MB
 @end example
 
-The unit of the result is the same than the unit of the offset
+The unit of the result is the same as the unit of the offset
 operand.
 
 Note that multiplying two offsets is not supported.  This makes sense,
@@ -1602,7 +1602,7 @@ something like the following to convert from kilobits to 
bytes:
 @end example
 
 There is also a ceil-division operator for offsets, with the same
-semantics than the ceil-division for integers:
+semantics as the ceil-division for integers:
 
 @example
 (poke) 10#B /^ 3#B
@@ -1857,11 +1857,11 @@ arrays:
 
 It is possible to refer to specific elements when constructing array
 literals.  For example, @code{[1,2,3,.[3] = 4]} denotes the same
-array than @code{[1,2,3,4]}.
+array as @code{[1,2,3,4]}.
 
 This allows creating arrays without having to specify all its
 elements.  Unspecified elements have the next specified value.  For
-example, @code{[.[2] = 2]} denotes the same array than
+example, @code{[.[2] = 2]} denotes the same array as
 @code{[2,2,2]}.
 
 Note that an array element can be referenced more than once.  When
@@ -2706,7 +2706,7 @@ defun @var{name} = [(@var{formal},@dots{})] 
@var{ret_type}:
 @end example
 
 Where @var{name} is the name of the function, which uses the same
-namespace than variables and types and @var{ret_type} is the type of
+namespace as variables and types and @var{ret_type} is the type of
 the value returned by the function.  If the function returns no value
 then it is @code{void}.
 
@@ -3783,7 +3783,7 @@ Print the integer as an ASCII character.  This only works 
with 8 bit
 integers.
 @end table
 @item %u
-Same than @code{%s}, but for unsigned integers.
+Same as @code{%s}, but for unsigned integers.
 @item %c
 A shorter way to write @code{%u8c}.
 @item %v
-- 
2.11.0