Don't use future tense.

3 files changed, 94 insertions, 94 deletions

diff --git a/doc/groff.texinfo b/doc/groff.texinfo
index f8cece1b..1e7ed091 100644
--- a/doc/groff.texinfo
+++ b/doc/groff.texinfo
@@ -1295,8 +1295,8 @@ it also implies @code{groff}'s @option{-s} option.
 @w{@code{\X'ps: import}} and @w{@code{\X'ps: file}} escapes.
 @end itemize
 
-The current directory is always searched first. This option may be specified
-more than once; the directories will be searched in the order specified. No
+The current directory is always searched first.  This option may be specified
+more than once; the directories are searched in the order specified.  No
 directory search is performed for files specified using an absolute path.
 @end table
 
@@ -1455,7 +1455,7 @@ are @samp{TR}, @samp{TB}, @samp{TI}, and @samp{TBI}.
 @cindex font path
 @cindex path, for font files
 All font files are kept in the @dfn{font directories} which constitute
-the @dfn{font path}.  The file search functions will always append the
+the @dfn{font path}.  The file search functions always append the
 directory @code{dev}@var{name}, where @var{name} is the name of the
 output device.  Assuming, say, DVI output, and @file{/foo/bar} as a
 font directory, the font files for @code{grodvi} must be in
@@ -2203,11 +2203,11 @@ with some versions of the @code{man} program.  @emph{Always} use the
 request, in preference to such a @samp{.ll @var{length}} request.
 In particular, note that in nroff mode, the request @samp{.ll 65n},
 (with any @var{length} expression which evaluates equal to 65@dmn{n},
-i.e., the formatter's default line length in nroff mode), will @emph{not}
-set the line length to 65@dmn{n} (it will be adjusted to the @code{man}
+i.e., the formatter's default line length in nroff mode), does @emph{not}
+set the line length to 65@dmn{n} (it is adjusted to the @code{man}
 macro package's default setting of 78@dmn{n}), whereas the use of the
 @option{-rLL=65n} option, or the @samp{.nr LL 65n}
-request @emph{will} establish a line length of 65@dmn{n}.}
+request @emph{does} establish a line length of 65@dmn{n}.}
 
 @item -rLT=@var{length}
 Set title length to @var{length}.  If not specified, the title length
@@ -2949,7 +2949,7 @@ Default: 12@dmn{p}.
 @endDefmpreg
 
 @Defmpreg {PSINCR, ms}
-Defines an increment in point size, which will be applied to section
+Defines an increment in point size, which is applied to section
 headings at nesting levels below the value specified in @code{GROWPS}.
 The value of @code{PSINCR} should be specified in points, with the
 @dmn{p} scaling factor, and may include a fractional component; for
@@ -2964,9 +2964,9 @@ Default: 1@dmn{p}.
 @Defmpreg {GROWPS, ms}
 Defines the heading level below which the point size increment set by
 @code{PSINCR} becomes effective.  Section headings at and above the
-level specified by @code{GROWPS} will be printed at the point size set
+level specified by @code{GROWPS} are printed at the point size set
 by @code{PS}; for each level below the value of @code{GROWPS}, the
-point size will be increased in steps equal to the value of
+point size is increased in steps equal to the value of
 @code{PSINCR}.  Setting @code{GROWPS} to any value less than@tie{}2
 disables the incremental heading size feature.
 
@@ -3025,7 +3025,7 @@ Defines the minimum number of initial lines of any paragraph which
 should be kept together, to avoid orphan lines at the bottom of a
 page.  If a new paragraph is started close to the bottom of a page,
 and there is insufficient space to accommodate @code{PORPHANS} lines
-before an automatic page break, then the page break will be forced,
+before an automatic page break, then the page break is forced,
 before the start of the paragraph.
 
 Effective: next paragraph.
@@ -3040,7 +3040,7 @@ should be kept together with any section heading introduced by the
 to the bottom of a page, and there is insufficient space to
 accommodate both the heading and at least @code{HORPHANS} lines of the
 following paragraph, before an automatic page break, then the page
-break will be forced before the heading.
+break is forced before the heading.
 
 Effective: next paragraph.
 
@@ -4010,7 +4010,7 @@ Document Control Registers}, for details.
 @cindex @code{ms} macros, multiple columns
 @cindex multiple columns [@code{ms}]
 
-The @file{ms} macros can set text in as many columns as will
+The @file{ms} macros can set text in as many columns as do
 reasonably fit on the page.  The following macros are available; all
 of them force a page break if a multi-column mode is already set.
 However, if the current mode is single-column, starting a multi-column
@@ -4848,7 +4848,7 @@ groff -Tlatin1 -mlatin9 ...
 @endExample
 
 @noindent
-will fail if you use the Euro character in the input.  Usually, this
+fails if you use the Euro character in the input.  Usually, this
 limitation is present only for devices which have a limited set of
 output glyphs (e.g.@: @option{-Tascii} and @option{-Tlatin1}); for other
 devices it is usually sufficient to install proper fonts which contain
@@ -6139,7 +6139,7 @@ Decimal arabic numbers.  This is the default format: 0, 1, 2,
 Decimal numbers with as many digits as specified.  So, @samp{00} would
 result in printing numbers as 01, 02, 03,@tie{}@enddots{}
 
-In fact, any digit instead of zero will do; @code{gtroff} only counts
+In fact, any digit instead of zero does work; @code{gtroff} only counts
 how many digits are specified.  As a consequence, @code{af}'s default
 format @samp{1} could be specified as @samp{0} also (and exactly this is
 returned by the @code{\g} escape, see below).
@@ -6933,7 +6933,7 @@ invoked by the @file{troffrc} or @file{troffrc-end} file; by default,
 @file{troffrc} loads hyphenation patterns and exceptions for American
 English (in files @file{hyphen.us} and @file{hyphenex.us}).
 
-A second call to @code{hpf} (for the same language) will replace the
+A second call to @code{hpf} (for the same language) replaces the
 hyphenation patterns with the new ones.
 
 Invoking @code{hpf} causes an error if there is no current hyphenation
@@ -7621,7 +7621,7 @@ Set the escape character to@tie{}@var{c}.  With no argument the default
 escape character @samp{\} is restored.  It can be also used to
 re-enable the escape mechanism after an @code{eo} request.
 
-Note that changing the escape character globally will likely break
+Note that changing the escape character globally likely breaks
 macro packages since @code{gtroff} has no mechanism to `intern' macros,
 i.e., to convert a macro definition into an internal form which is
 independent of its representation (@TeX{} has this mechanism).
@@ -8220,7 +8220,7 @@ The @samp{|} operator is also affected.
 @cindex @code{\R}, after @code{\c}
 @code{\c} works on the output level.  Anything after this escape on the
 same line is ignored, except @code{\R} which works as usual.  Anything
-before @code{\c} on the same line will be appended to the current partial
+before @code{\c} on the same line is appended to the current partial
 output line.  The next non-command line after an interrupted line counts
 as a new input line.
 
@@ -8232,7 +8232,7 @@ The visual results depend on whether no-fill mode is active.
 @cindex no-fill mode, and @code{\c}
 @cindex mode, no-fill, and @code{\c}
 If no-fill mode is active (using the @code{nf} request), the next input
-text line after @code{\c} will be handled as a continuation of the same
+text line after @code{\c} is handled as a continuation of the same
 input text line.
 
 @Example
@@ -8247,7 +8247,7 @@ test.
 @cindex fill mode, and @code{\c}
 @cindex mode, fill, and @code{\c}
 If fill mode is active (using the @code{fi} request), a word interrupted
-with @code{\c} will be continued with the text on the next input text line,
+with @code{\c} is continued with the text on the next input text line,
 without an intervening space.
 
 @Example
@@ -8459,7 +8459,7 @@ do the following before each paragraph:
 text text text
 @endExample
 
-@code{ne} will then automatically cause a page break if there is space
+@code{ne} then automatically causes a page break if there is space
 for one line only.
 @endDefreq
 
@@ -8477,7 +8477,7 @@ if no argument is given; the default scaling indicator is @samp{v}.
 @cindex @code{sv} request, and no-space mode
 @cindex @code{os} request, and no-space mode
 Both @code{sv} and @code{os} ignore no-space mode.  While the @code{sv}
-request allows negative values for @var{space}, @code{os} will ignore
+request allows negative values for @var{space}, @code{os} ignores
 them.
 @endDefreq
 
@@ -8735,10 +8735,10 @@ which name is the concatenation of the name of the current
 family and the name of the current style.  For example, if the current
 font is@tie{}1 and font position@tie{}1 is associated with style
 @samp{R} and the current font family is @samp{T}, then font
-@samp{TR} will be used.  If the current font is not a style, then the
+@samp{TR} is used.  If the current font is not a style, then the
 current family is ignored.  If the requests @code{cs}, @code{bd},
 @code{tkf}, @code{uf}, or @code{fspecial} are applied to a style,
-they will instead be applied to the member of the current family
+they are instead applied to the member of the current family
 corresponding to that style.
 
 @var{n}@tie{}must be a non-negative integer value.
@@ -9040,7 +9040,7 @@ is called @dfn{groff glyph list (GGL)}.
 @itemize @bullet
 @item
 A glyph for Unicode character U+@var{XXXX}[@var{X}[@var{X}]] which is
-not a composite character will be named
+not a composite character is named
 @code{u@var{XXXX}@r{[}@var{X}@r{[}@var{X}@r{]]}}.  @var{X} must be an
 uppercase hexadecimal digit.  Examples: @code{u1234}, @code{u008E},
 @code{u12DB8}.  The largest Unicode value is 0x10FFFF.  There must be at
@@ -9051,7 +9051,7 @@ represented with character codes from the surrogate area U+D800-U+DFFF)
 are not allowed too.
 
 @item
-A glyph representing more than a single input character will be named
+A glyph representing more than a single input character is named
 
 @display
 @samp{u} @var{component1} @samp{_} @var{component2} @samp{_} @var{component3} @dots{}
@@ -9072,10 +9072,10 @@ acute}.
 @item
 groff maintains a table to decompose all algorithmically derived glyph
 names which are composites itself.  For example, @code{u0100} (@sc{latin
-letter a with macron}) will be automatically decomposed into
+letter a with macron}) is automatically decomposed into
 @code{u0041_0304}.  Additionally, a glyph name of the GGL is preferred
 to an algorithmically derived glyph name; groff also automatically does
-the mapping.  Example: The glyph @code{u0045_0302} will be mapped to
+the mapping.  Example: The glyph @code{u0045_0302} is mapped to
 @code{^E}.
 
 @item
@@ -9108,12 +9108,12 @@ follows:
 
 @itemize @bullet
 @item
-Any component which is found in the GGL will be converted to the
+Any component which is found in the GGL is converted to the
 @code{u@var{XXXX}} form.
 
 @item
 Any component @code{u@var{XXXX}} which is found in the list of
-decomposable glyphs will be decomposed.
+decomposable glyphs is decomposed.
 
 @item
 The resulting elements are then concatenated with @samp{_} inbetween,
@@ -9121,7 +9121,7 @@ dropping the leading @samp{u} in all elements but the first.
 @end itemize
 
 No check for the existence of any component (similar to @code{tr}
-request) will be done.
+request) is done.
 
 Examples:
 
@@ -11582,7 +11582,7 @@ Despite of being silly, the current point is moved horizontally to the
 right by@tie{}@var{n}.
 
 @cindex @w{@code{\D'f @dots{}'}} and horizontal resolution
-Don't use this command!  It has the serious drawback that it will be
+Don't use this command!  It has the serious drawback that it is
 always rounded to the next integer multiple of the horizontal resolution
 (the value of the @code{hor} keyword in the @file{DESC} file).  Use
 @code{\M} (@pxref{Colors}) or @w{@code{\D'Fg @dots{}'}} instead.
@@ -11921,7 +11921,7 @@ Another line.
 An important fact to consider while designing macros is that diversions and
 traps do not interact normally.  For example, if a trap invokes a header
 macro (while outputting a diversion) which tries to change the font on the
-current page, the effect will not be visible before the diversion has
+current page, the effect is not visible before the diversion has
 completely been printed (except for input protected with @code{\!} or
 @code{\?}) since the data in the diversion is already formatted.  In most
 cases, this is not the expected behaviour.
@@ -12544,7 +12544,7 @@ This escape is @code{grohtml} specific.  Provided that this escape
 occurs at the outer nesting level write the @code{filename} to
 @code{stderr}.  The position of the image, @var{P}, must be specified
 and must be one of @code{l}, @code{r}, @code{c}, or@tie{}@code{i} (left,
-right, centered, inline).  @var{filename} will be associated with the
+right, centered, inline).  @var{filename} is associated with the
 production of the next inline image.
 @end table
 @endDefesc
@@ -13470,7 +13470,7 @@ To activate these statements say
 groff -rDB=1 file
 @endExample
 
-If it is known in advance that there will be many errors and no useful
+If it is known in advance that there are many errors and no useful
 output, @code{gtroff} can be forced to suppress formatted output with
 the @option{-z} flag.
 
@@ -13581,7 +13581,7 @@ For example,
 @endExample
 
 @noindent
-will cause a warning if @code{gtroff} must add 0.2@dmn{m} or more for each
+causes a warning if @code{gtroff} must add 0.2@dmn{m} or more for each
 interword space in a line.
 
 This request is active only if text is justified to both margins (using
@@ -13943,7 +13943,7 @@ diversion; it also works in both GNU @code{troff} and @acronym{UNIX}
 @code{troff}.@footnote{To be completely independent of the current
 escape character, use @code{\(rs} which represents a reverse solidus
 (backslash) glyph.}  To store, for some reason, an escape sequence in a
-diversion that will be interpreted when the diversion is reread, either
+diversion that is interpreted when the diversion is reread, either
 use the traditional @code{\!} transparent output facility, or, if this
 is unsuitable, the new @code{\?} escape sequence.
 
@@ -14522,7 +14522,7 @@ while others, such as the color commands, expect plain integers.
 Note that single characters can have the eighth bit set, as can the
 names of fonts and special characters.  The names of characters and
 fonts can be of arbitrary length.  A character that is to be printed
-will always be in the current font.
+is always in the current font.
 
 A string argument is always terminated by the next whitespace
 character (space, tab, or newline); an embedded @samp{#} character is
@@ -15581,7 +15581,7 @@ character set.  For example, the glyph @samp{\[Po]} is
 represented as @samp{£} in @acronym{HTML} 4.0.
 
 Anything on the line after the @var{entity-name} field resp.@: after
-@samp{--} will be ignored.
+@samp{--} is ignored.
 
 The @var{metrics} field has the form:
 
diff --git a/doc/pic.ms b/doc/pic.ms
index 6c6b66a5..edff0ed1 100644
--- a/doc/pic.ms
+++ b/doc/pic.ms
@@ -10,7 +10,7 @@
 .\" This document was written for free use and redistribution by
 .\" Eric S. Raymond <esr@thyrsus.com> in August 1995.
 .\"
-.\"	$Id: pic.ms,v 1.29 2005/04/27 20:52:34 wl Exp $	
+.\"	$Id: pic.ms,v 1.30 2006/01/21 14:14:09 wl Exp $	
 .\"
 .\" Set a proper TeX and LaTeX
 .ie t \{\
@@ -77,7 +77,7 @@ Where differences between Documenter's Work Bench (1991) \fBpic\fP and GNU
 \[lq]DWB pic\[rq].  Details on the history of the program are given at the
 end of this document.
 .PP
-In this document, the \fIgpic\/\fP(1) extensions will be marked as such.
+In this document, the \fIgpic\/\fP(1) extensions are marked as such.
 .
 .
 .NH 1
@@ -97,7 +97,7 @@ on the page.
 .NH 2
 PIC Error Messages
 .PP
-If you make a \fBpic\fP syntax error, \fIgpic\/\fP(1) will issue an
+If you make a \fBpic\fP syntax error, \fIgpic\/\fP(1) issues an
 error message in the standard \fIgcc\/\fP(1)-like syntax.  A typical
 error message looks like this,
 .KS
@@ -195,7 +195,7 @@ purposes.  We'll describe both of these later on.
 .PP
 The box, ellipse, circle, and block composite objects are \fIclosed\/\fR;
 lines, arrows, arcs and splines are \fIopen\fP.  This distinction
-will often be important in explaining command modifiers.
+is often important in explaining command modifiers.
 .PP
 Figure \n[H1]-2 was produced by the following \fBpic\fP program,
 which introduces some more basic concepts:
@@ -315,8 +315,8 @@ Sizes and Spacing
 .PP
 Sizes are specified in inches.  If you don't like inches, it's
 possible to set a global style variable \fBscale\fP that changes the
-unit.  Setting \fBscale = 2.54\fP will effectively change the internal
-unit to centimeters (all other size variable values will be scaled
+unit.  Setting \fBscale = 2.54\fP effectively changes the internal
+unit to centimeters (all other size variable values are scaled
 correspondingly).
 .
 .NH 2
@@ -373,7 +373,7 @@ box width 3 "this text is far too long for a default box"
 .CE "2: Result of \fBbox width 3 \"text far too long\"\fP"
 .PP
 This modifier takes a dimension in inches.  There is also a \[lq]height\[rq]
-modifier that will change a box's height.  The \fBwidth\fP keyword may
+modifier that changes a box's height.  The \fBwidth\fP keyword may
 be abbreviated to \fBwid\fP; the \fBheight\fP keyword to \fBht\fP.
 .
 .NH 2
@@ -627,9 +627,9 @@ and a \fBheight\fP attribute, the length of the arrowhead along the shaft.
 Arrowhead style is controlled by the style variable \fBarrowhead\fP.
 The DWB and GNU versions interpret it differently.  DWB defaults to
 open arrowheads and an \fBarrowhead\fP value of\~2; the Kernighan
-paper says a value of\~7 will make solid arrowheads.  GNU \fBgpic\fP
+paper says a value of\~7 makes solid arrowheads.  GNU \fBgpic\fP
 defaults to solid arrowheads and an \fBarrowhead\fP value of\~1; a
-value of\~0 will produce open arrowheads.  Note that solid arrowheads are
+value of\~0 produces open arrowheads.  Note that solid arrowheads are
 always filled with the current outline color.
 .
 .NH 2
@@ -685,11 +685,11 @@ circle fill; move; circle fill 0.4; move; circle fill 0.9;
 .PP
 GNU \fBgpic\fP makes some additional guarantees.  A fill value greater
 than 1 can also be used: this means fill with the shade of gray that
-is currently being used for text and lines.  Normally this will be
+is currently being used for text and lines.  Normally this is
 black, but output devices may provide a mechanism for changing this.
 The invisible attribute does not affect the filling of objects.  Any
-text associated with a filled object will be added after the object
-has been filled, so that the text will not be obscured by the filling.
+text associated with a filled object is added after the object
+has been filled, so that the text is not obscured by the filling.
 .PP
 The closed-object modifier \fBsolid\fP is equivalent to \fBfill\fP
 with the darkest fill value (DWB \fBpic\fP had this capability but
@@ -752,14 +752,14 @@ about \fI[tg]roff\/\fP(1)'s default point size).
 In GNU \fBgpic\fR, objects can have an
 .B aligned
 attribute.
-This will only work when the postprocessor is
+This only works if the postprocessor is
 \fBgrops\fP.
 Any text associated with an object having the
 .B aligned
-attribute will be rotated about the center of the object
+attribute is rotated about the center of the object
 so that it is aligned in the direction from the start point
 to the end point of the object.
-Note that this attribute will have no effect for objects whose start and
+Note that this attribute has no effect for objects whose start and
 end points are coincident.
 .
 .
@@ -930,13 +930,13 @@ arrow right at A .r;
 .PE
 .CE "1: Example of label use"
 The \fBat\fP statement in the fourth line uses the label \fBA\fP (the
-behavior of \fBat\fP will be explained in the next section).  We'll
+behavior of \fBat\fP is explained in the next section).  We'll
 see later on that labels are most useful for referring to block composite
 objects.  
 .PP
 Labels are not constants but variables (you can view colon as a sort
 of assignment).  You can say something like \fBA: A + (1,0);\fP
-and the effect will be to reassign the label \fBA\fR to designate a
+and the effect is to reassign the label \fBA\fR to designate a
 position one inch to the right of its old value. 
 .
 .
@@ -1257,7 +1257,7 @@ you can change the amount of chopping.
 If you say \fBline .\|.\|.\& chop \fIr1\fP chop \fIr2\fP\fR with \fIr1\fP
 and \fIr2\fP both numbers, you can vary the amount of chopping at both
 ends.  You can use this in combination with trigonometric functions
-to write code that will deal with more complex intersections.
+to write code that deals with more complex intersections.
 .
 .
 .NH 1
@@ -1389,7 +1389,7 @@ arrow from 2nd last [];
 .DE
 .KE
 .LP
-the arrow in the last line will be attached to object \fBP\fP, not 
+the arrow in the last line is attached to object \fBP\fP, not 
 object \fBQ\fP.
 .PP
 In DWB \fBpic\fP, only references one level deep into enclosed blocks
@@ -1469,7 +1469,7 @@ internally as floating-point).  Decimal-point notation is acceptable;
 in GNU \fBgpic\fR, scientific notation in C's `e' format (like
 \f(CW5e-2\fP) is accepted.
 .PP
-Anywhere a number is expected, the language will also accept a
+Anywhere a number is expected, the language also accepts a
 variable.  Variables may be the built-in style variable described in
 the last section, or new variables created by assignment.
 .PP
@@ -1482,7 +1482,7 @@ variable within a block shadows a variable with the same name outside of
 the block.
 .PP
 GNU \fBgpic\fP supports an alternate form of assignment using \fB:=\fP.
-The variable must already be defined, and the value will be assigned to
+The variable must already be defined, and the value is assigned to
 that variable without creating a variable local to the current block.
 For example, this
 .KS
@@ -1566,7 +1566,7 @@ text (not including the braces).  The macro may be called as
 .R
 .DE
 .LP
-The arguments (if any) will be substituted for tokens \fB$1\fP, \fB$2\fP
+The arguments (if any) are substituted for tokens \fB$1\fP, \fB$2\fP
 \&.\|.\|.\& \fB$n\fP
 appearing in the replacement text.
 .PP
@@ -1605,7 +1605,7 @@ define jumperblock {
     box with .nw at 6th last [].nw wid 6*jwidth ht jheight;
 
     # Use {} to avoid changing position from last box draw.
-    # This is necessary so move in any direction will work as expected
+    # This is necessary so move in any direction works as expected
     {"Jumpers in state $1$2$3$4$5$6" at last box .s + (0,-0.2);}
 }
 
@@ -1651,7 +1651,7 @@ define jumperblock {
     box with .nw at 6th last [].nw wid 6*jwidth ht jheight;
 
     # Use {} to avoid changing position from last box draw.
-    # This is necessary so move in any direction will work as expected
+    # This is necessary so move in any direction works as expected
     {"Jumpers in state $1$2$3$4$5$6" at last box .s + (0,-0.2);}
 }
 
@@ -1667,7 +1667,7 @@ and variable assignment to write true functions.
 .PP
 One detail the example above does not illustrate is the fact that
 macro argument parsing is not token-oriented.  If you call
-\fBjumper(\ 1\ )\fP, the value of $1 will be \fB"\ 1\ "\fP.  You could
+\fBjumper(\ 1\ )\fP, the value of $1 is \fB"\ 1\ "\fP.  You could
 even call \fBjumper(big\ string)\fP to give $1 the value
 \fB"big\ string"\fP.
 .PP
@@ -1699,7 +1699,7 @@ The statement
 .DE
 .LP
 inserts the contents of \fIfilename\fR in the \fBpic\fP input stream.
-Any \fB.PS\fP/\fB.PE\fP pair in the file will be ignored.  You
+Any \fB.PS\fP/\fB.PE\fP pair in the file is ignored.  You
 can use this to include pre-generated images.
 .PP
 A variant of this statement replicates the \fBcopy thru\fP feature of
@@ -1884,7 +1884,7 @@ is prefixed by\~\c
 .B *
 then
 .I variable
-will instead be multiplied by
+is multiplied instead by
 \fIexpr3\fR.
 The value of
 .I expr3
@@ -1926,7 +1926,7 @@ or
 pairs may instead be balanced pairs of
 braces ({ and\~}) as in the \fBsh\fR command.  In either case, the
 \fIif-true\fR may contain balanced pairs of braces.  None of these
-delimiters will be seen inside strings.
+delimiters are seen inside strings.
 .PP
 All the usual relational operators my be used in conditional expressions;
 \fB!\&\fP (logical negation, not factorial), \fB&&\fP, \fB|\||\fP, \fB==\fP,
@@ -1947,16 +1947,16 @@ present in \fIgroff\/\fP(1) that are not present in \fItroff\/\fP(1).
 .NH 2
 Scaling Arguments
 .PP
-The DWB \fIpic\/\fP(1) program will accept one or two arguments to
+The DWB \fIpic\/\fP(1) program accepts one or two arguments to
 \&\fB.PS\fP, which is interpreted as a width and height in inches to
 which the results of \fIpic\/\fP(1) should be scaled (width and height
 scale independently).  If there is only one argument, it is
-interpreted as a width to scale the picture to, and height will be
+interpreted as a width to scale the picture to, and height is
 scaled by the same proportion.
 .PP
-GNU \fBgpic\fP is less general; it will accept a single width to scale
+GNU \fBgpic\fP is less general; it accepts a single width to scale
 to, or a zero width and a maximum height to scale to.  With
-two non-zero arguments, it will scale to the maximum height.
+two non-zero arguments, it scales to the maximum height.
 .
 .NH 2
 How Scaling is Handled
@@ -1993,7 +1993,7 @@ the following definitions:
 .vs
 .KE
 .LP
-Equivalent definition will be supplied by GNU \fIpic\/\fP(1) if you use
+Equivalent definition is supplied by GNU \fIpic\/\fP(1) if you use
 the \-mpic option; this should make it usable with macro pages other
 than \fIms\/\fR(1).
 .PP
@@ -2015,7 +2015,7 @@ PIC and [gt]roff commands
 By default, input lines that begin with a period are passed to the
 postprocessor, embedded at the corresponding point in the output.
 Messing with horizontal or vertical spacing is an obvious recipe for
-bugs, but point size and font changes will usually be safe.
+bugs, but point size and font changes are usually safe.
 .PP
 Point sizes and font changes are also safe within text strings, as
 long as they are undone before the end of string.
@@ -2069,7 +2069,7 @@ Interface to TeX
 \*[tx] mode is enabled by the
 .B \-t
 option.
-In \*[tx] mode, pic will define a vbox called
+In \*[tx] mode, pic defines a vbox called
 .B \egraph
 for each picture; the name can be changed with the pseudo-variable
 .B figname
@@ -2082,7 +2082,7 @@ You must yourself print that vbox using, for example, the command
 .RE
 .LP
 Actually, since the vbox has a height of zero (it is defined with \evtop)
-this will produce slightly more vertical space above the picture than
+this produces slightly more vertical space above the picture than
 below it;
 .RS
 .LP
@@ -2122,7 +2122,7 @@ change the value of \fB\ebaselineskip\fP.
 Anything else may well produce undesirable results; use at your own risk.
 Lines beginning with a period are not given any special treatment.
 .PP
-The \*[tx] mode of \fIpic\/\fP(1) will \fInot\fP translate \fBtroff\fP
+The \*[tx] mode of \fIpic\/\fP(1) does \fInot\fP translate \fBtroff\fP
 font and size changes included in text strings!
 .PP
 Here an example how to use \fBfigname\fP.
@@ -2441,7 +2441,7 @@ A line starting with a command character (`.' in groff mode, `\e' in
 A string either enclosed by `{' and `}' or with \fIX\fP and \fIX\fP,
 where \fIX\fP doesn't occur in the string.
 .IP \s[-1]BALANCED-BODY\s[0]
-Delimiters as in \s[-1]BALANCED-TEXT\s[0]; the body will be interpreted as
+Delimiters as in \s[-1]BALANCED-TEXT\s[0]; the body is interpreted as
 `\fB\[la]command\[ra].\|.\|.\fP'.
 .IP \s[-1]FILENAME\s[0]
 The name of a file.  This has the same semantics as \s[-1]TEXT\s[0].
@@ -2480,7 +2480,7 @@ The top-level \fBpic\fP object is a picture.
 .PP
 The arguments, if present, represent the width and height of the picture,
 causing \fBpic\fR to attempt to scale it to the given dimensions in
-inches.  In no case, however, will the X and Y\~dimensions of the
+inches.  In no case, however, the X and Y\~dimensions of the
 picture exceed the values of the style variables \fBmaxpswid\fP and
 \fBmaxpsheight\fP (which default to the normal 8.5\^i by 11\^i page size).
 .PP
@@ -2546,7 +2546,7 @@ else
 .R
 .DE
 .PP
-will fail.  You have to use the braces on the same line as the keywords:
+fails.  You have to use the braces on the same line as the keywords:
 .DS
 .CW
 if {
@@ -2925,7 +2925,7 @@ text (not including the braces).  The macro may be called as
 .R
 .DE
 .LP
-The arguments (if any) will be substituted for tokens $1, $2 .\|.\|.\& $n
+The arguments (if any) are substituted for tokens $1, $2 .\|.\|.\& $n
 appearing in the replacement text.  To undefine a macro, say \fBundef\fP
 \fIname\fR, specifying the name to be undefined.
 .\"%%POSTLUDE%%
diff --git a/doc/webpage.ms b/doc/webpage.ms
index 442c456f..3c159f91 100644
--- a/doc/webpage.ms
+++ b/doc/webpage.ms
@@ -122,7 +122,7 @@ macros contributed by
 .MTO jh@\:axis.se "J\[:o]rgen H\[:a]gg" .
 
 See the file INSTALL for installation instructions.
-You will require a C++ compiler.
+You require a C++ compiler.
 
 The file NEWS describes recent user-visible changes to groff.
 
@@ -156,7 +156,7 @@ cvs -d:pserver:anoncvs@savannah.gnu.org:/cvsroot/groff -z5 co groff
 
 When asked for a password during the `login' call, simply press Enter.
 
-This will create a subdirectory, ~/cvswork/groff, with a `checked out'
+This creates a subdirectory, ~/cvswork/groff, with a `checked out'
 copy of the CVS repository.
 An update of this working copy may be
 achieved, at any later time by invoking the commands
@@ -221,9 +221,9 @@ Note that texinfo and bison or byacc are required only for building from
 CVS sources (either a checked out working copy, or a daily snapshot).
 They are not required for building from a stable release tarball.
 Also note that the version numbers stated are the minimum supported.
-No version of texinfo < 4.8 will work, and the original release of bison
+No version of texinfo < 4.8 work, and the original release of bison
 1.875 is known not to work; you \fImay\fP find that bison releases < 1.875
-will work, but in case of difficulty, please update to a later version
+do work, but in case of difficulty, please update to a later version
 \fIbefore\fP posting a bug report.
 
 For \fIall\fP sources, you need ghostscript for creation of either PDF or
@@ -240,7 +240,7 @@ is to make sure that FSF has all the information it needs to fix the bug.
 At the very least, read the BUG-REPORT form and make sure that you supply
 all the information that it asks for.
 Even if you are not sure that something is a bug, report it using
-BUG-REPORT: this will enable us to determine whether it really is a bug or
+BUG-REPORT: this enables us to determine whether it really is a bug or
 not.
 
 .SH
@@ -482,15 +482,15 @@ Sets number of lines of following paragraph which must be kept with a
 heading, defined by `NH' or `SH', before any automatic page break.
 
 .IP GROWPS
-Sets the first level of heading (set with `NH') which will keep the
+Sets the first level of heading (set with `NH') which keeps the
 same point size as body text.
 
 .IP PSINCR
 Sets the point size increment for each level of heading (set with
 `NH'), below the threshold level set by `GROWPS'; e.g., if
 \en[PS]\~=\~10, \en[GROWPS]\~=\~3 and \en[PSINCR]\~=\~2.0p, then `.NH\~1'
-will produce 14pt headings, `.NH\~2' will produce 12pt, and all other levels
-will remain at 10pt (because \en[PS]\~=\~10).
+produces 14pt headings, `.NH\~2' produces 12pt, and all other levels
+remain at 10pt (because \en[PS]\~=\~10).
 
 .LI
 The `SH' macro now accepts a numeric argument, to make heading size
@@ -559,7 +559,7 @@ files named in `so' and `psbb' requests, and files named in \eX'ps:\~file'
 and \eX'ps:\~import' escapes.
 
 .LI
-If option `\-V' is used more than once, the commands will be both printed
+If option `\-V' is used more than once, the commands are both printed
 on standard error and run.
 .ULE
 .
@@ -802,7 +802,7 @@ The new request
 .ft R
 .in
 
-will change the mapping while a composite glyph name is constructed.
+changes the mapping while a composite glyph name is constructed.
 To make \e[A\~ho] yield the expected result,
 
 .in 2m
@@ -1377,7 +1377,7 @@ final `0' can be omitted.
 
 .LI
 `trin' (translate input) is a new request which is similar to `tr' with
-the exception that the `asciify' request will use the character code (if
+the exception that the `asciify' request uses the character code (if
 any) before the character translation.
 Example:
 
@@ -1557,12 +1557,12 @@ The image position parameter names in `IMG' have been changed to `\-L',
 `\-R', and `\-C'.
 
 .LI
-New macro `PIMG' for inclusion of a PNG image (it will automatically
-convert it into an EPS file if not \-Thtml is used).
+New macro `PIMG' for inclusion of a PNG image (it automatically
+converts it into an EPS file if not \-Thtml is used).
 
 .LI
 New macro `MPIMG' for putting a PNG image into the left or right margin
-(it will automatically convert it into an EPS file if not \-Thtml is used).
+(it automatically converts it into an EPS file if not \-Thtml is used).
 
 .LI
 New macros `HnS', `HnE' to start and end a header line block.
@@ -1813,7 +1813,7 @@ Miscellaneous
 A new manual page `ditroff.7' is available.
 
 .LI
-The groff texinfo manual will now be installed, together with a bunch
+The groff texinfo manual is now installed, together with a bunch
 of examples.
 
 .LI