17503: fix various typos, spelling mistakes and poor wordings in the docs

Doc/Zsh/builtins.yo

@@ -656,7 +656,7 @@ If the tt(PUSHD_MINUS) option is set, the meanings of `tt(PLUS())' and
 findex(print)
 item(tt(print) [ tt(-bnrslzpNDPoOicm) ] [ tt(-u)var(n) ] [ tt(-f) var(format) ] [ tt(-R) [ tt(-en) ]] [ var(arg) ... ])(
 With the `tt(-f)' option the arguments are printed as described by tt(printf).
-With no flags or with flag `tt(-)', the arguments are printed on
+With no flags or with the flag `tt(-)', the arguments are printed on
 the standard output as described by tt(echo), with the following differences:
 the escape sequence `tt(\M-)var(x)' metafies the character
 var(x) (sets the highest bit),

Doc/Zsh/compsys.yo

@@ -274,10 +274,10 @@ the var(cmd)s be completed as those for the var(services).
 
 The var(function) may actually be a string containing any shell code
 and that string will be executed via the tt(eval) builtin command. 
-This allows to easily define completions for commands that need to call
-one of the completion functions with arguments.  For example to make
-files ending in `tt(.h)' be completed as arguments to the command
-tt(foo), one would use:
+This allows for the easy definition of completions for commands that
+need to call one of the completion functions with arguments.  For
+example to make files ending in `tt(.h)' be completed as arguments to
+the command tt(foo), one would use:
 
 example(compdef '_files -g "*.h"' foo)
 
@@ -568,7 +568,7 @@ for names of builtin commands
 kindex(characters, completion tag)
 item(tt(characters))(
 used for commands like tt(stty) when completing characters; also used
-when completing character classes after a opening bracket
+when completing character classes after an opening bracket
 )
 kindex(colormapids, completion tag)
 item(tt(colormapids))(
@@ -3090,7 +3090,7 @@ options and arguments which may be passed to the command for which
 completion is being performed.  The description is given as arguments to
 this function, with each var(spec) describing one option or normal
 argument of the command.  To separate these var(spec)s from the
-options given to tt(_arguments) itself, they can be preceeded by an
+options given to tt(_arguments) itself, they can be preceded by an
 argument containing a single colon.  The forms of var(spec)
 understood are:
 
@@ -4274,7 +4274,7 @@ function the tt(context) parameter will be set to the name of the
 value whose argument is to be completed.
 
 Note also that tt(_values) normally adds the character used as the
-separator between values as a auto-removable suffix so that users don't
+separator between values as an auto-removable suffix so that users don't
 have to type it themselves.  But when using a `tt(->)var(string)' action
 tt(_values) can't do that because the matches for the argument will be
 generated by the calling function.  To get the usual behaviour, the

Doc/Zsh/contrib.yo

@@ -438,7 +438,7 @@ and tt(down-line-or-search):  if in a multiline buffer they move up or
 down within the buffer, otherwise they search for a history line matching
 the start of the current line.  In this case, however, they search for
 a line which matches the current line up to the current cursor position, in
-the manner of tt(history-begining-search-backward) and tt(-forward), rather
+the manner of tt(history-beginning-search-backward) and tt(-forward), rather
 than the first word on the line.
 )
 tindex(incarg)
@@ -909,7 +909,7 @@ evaluated using radians, and so on.
 Each line typed is evaluated as an expression.  The prompt shows a number,
 which corresponds to a positional parameter where the result of that
 calculation is stored.  For example, the result of the calculation on the
-line preceeded by `tt(4> )' is available as tt($4).  Full command line
+line preceded by `tt(4> )' is available as tt($4).  Full command line
 editing, including the history of previous calculations, is available; the
 history is saved in the file tt(~/.zcalc_history).  To exit, enter a blank
 line or type `tt(q)' on its own.
@@ -923,7 +923,7 @@ Parameter assignment is possible, but note that all parameters will be put
 into the global namespace.
 
 An extra facility is provided for changing the default output base.  Use,
-for example, `tt([#16])' to display hexadecimal output preceeded by an
+for example, `tt([#16])' to display hexadecimal output preceded by an
 indication of the base, or `tt([##16])' just to display the raw number in
 the given base.  Bases themselves are always specified in decimal.
 `tt([#])' restores the normal output format.

Doc/Zsh/expn.yo

@@ -1680,11 +1680,11 @@ If the qualifier `tt(f)' is followed by any other character anything
 up to the next matching character (`tt([)', `tt({)', and `tt(<)' match 
 `tt(])', `tt(})', and `tt(>)' respectively, any other character
 matches itself) is taken as a list of comma-separated
-var(sub-spec)s. Each var(sub-spec) may be either a octal number as
+var(sub-spec)s. Each var(sub-spec) may be either an octal number as
 described above or a list of any of the characters `tt(u)', `tt(g)',
 `tt(o)', and `tt(a)', followed by a `tt(=)', a `tt(PLUS())', or a
 `tt(-)', followed by a list of any of the characters `tt(r)', `tt(w)', 
-`tt(x)', `tt(s)', and `tt(t)', or a octal digit. The first list of
+`tt(x)', `tt(s)', and `tt(t)', or an octal digit. The first list of
 characters specify which access rights are to be checked. If a `tt(u)'
 is given, those for the owner of the file are used, if a `tt(g)' is
 given, those of the group are checked, a `tt(o)' means to test those
@@ -1886,5 +1886,5 @@ example(print b*.pro(#q:s/pro/shmo/)(#q.:s/builtin/shmiltin/))
 demonstrates how colon modifiers and other qualifiers may be chained
 together.  The ordinary qualifier `tt(.)' is applied first, then the colon
 modifiers in order from left to right.  So if tt(EXTENDED_GLOB) is set and
-the base battern matches the regular file tt(builtin.pro), the shell will
+the base pattern matches the regular file tt(builtin.pro), the shell will
 print `tt(shmiltin.shmo)'.

Doc/Zsh/files.yo

@@ -10,7 +10,7 @@ pindex(GLOBAL_RCS, use of)
 pindex(NO_RCS, use of)
 pindex(NO_GLOBAL_RCS, use of)
 vindex(ZDOTDIR, use of)
-@cindex(zshenv)
+cindex(zshenv)
 Commands are first read from tt(/etc/zshenv); this cannot be overridden.
 Subsequent behaviour is modified by the tt(RCS) and
 tt(GLOBAL_RCS) options; the former affects all startup files, while the

Doc/Zsh/params.yo

@@ -707,9 +707,8 @@ vindex(FIGNORE)
 item(tt(fignore) <S> <Z> (tt(FIGNORE) <S>))(
 An array (colon separated list)
 containing the suffixes of files to be ignored
-during filename completion.  However, if the completion generates only files
-which would match if this variable would be ignored, than these files are
-completed anyway.
+during filename completion.  However, if completion only generates files
+with suffixes in this list, then these files are completed anyway.
 )
 vindex(fpath)
 vindex(FPATH)

Doc/Zsh/zle.yo

@@ -1045,7 +1045,7 @@ history offset which applies to successive calls to this widget: if is -1,
 the default behaviour is used, while if it is 1, successive calls will move
 forwards through the history.  The value 0 can be used to indicate that the
 history line examined by the previous execution of the command will be
-reexamined.  Note that negative numbers should be preceeded with a
+reexamined.  Note that negative numbers should be preceded with a
 `tt(-)tt(-)' argument to avoid confusing them with options.
 
 If two arguments are given, the second specifies the word on the command