diff --git a/find/find.1 b/find/find.1
index b916ad0..4a3e0e9 100644
--- a/find/find.1
+++ b/find/find.1
@@ -257,7 +257,7 @@ need to stat the file first.
If you use the
.B \-fstype
.I FOO
-predicate and specify a filsystem type
+predicate and specify a filesystem type
.I FOO
which is not known (that is, present in `/etc/mtab') at the time
.B find
@@ -265,7 +265,7 @@ starts, that predicate is equivalent to
.BR \-false .
.IP 3
At this optimisation level, the full cost-based query optimiser is
-enabled. The order of tests is modified so that cheap (i.e. fast)
+enabled. The order of tests is modified so that cheap (i.e.\& fast)
tests are performed first and more expensive ones are performed later,
if necessary. Within each cost band, predicates are evaluated earlier
or later according to whether they are likely to succeed or not. For
@@ -286,7 +286,7 @@ not actually improve the performance of
.BR find ,
it will be removed again. Conversely, optimisations that prove to be
reliable, robust and effective may be enabled at lower optimisation
-levels over time. However, the default behaviour (i.e. optimisation
+levels over time. However, the default behaviour (i.e.\& optimisation
level 1) will not be changed in the 4.3.x release series. The
findutils test suite runs all the tests on
.B find
@@ -429,7 +429,7 @@ searching filesystems that do not follow the Unix directory-link
convention, such as CD-ROM or MS-DOS filesystems or AFS volume mount
points. Each directory on a normal Unix filesystem has at least 2
hard links: its name and its `.' entry. Additionally, its
-subdirectories (if any) each have a `..' entry linked to that
+subdirectories (if any) each have a `..\&' entry linked to that
directory. When
.B find
is examining a directory, after it has statted 2 fewer subdirectories
@@ -613,7 +613,7 @@ Like
but the match is case insensitive.
.IP "\-iwholename \fIpattern\fR"
-See \-ipath. This alternative is less portable than
+See \-ipath. This alternative is less portable than
.BR \-ipath .
.IP "\-links \fIn\fR"
@@ -784,7 +784,7 @@ section for some illustrative examples.
.IP "\-perm \-\fImode\fR"
All of the permission bits \fImode\fR are set for the file.
Symbolic modes are accepted in this form, and this is usually the way
-in which would want to use them. You must specify `u', `g' or `o' if
+in which you would want to use them. You must specify `u', `g' or `o' if
you use a symbolic mode. See the
.B EXAMPLES
section for some illustrative examples.
@@ -860,7 +860,7 @@ handle sparse files
differently. The `b' suffix always denotes 512-byte blocks and never
1 Kilobyte blocks, which is different to the behaviour of
.BR \-ls .
-The + and - prefixes signifiy greater than and less than, as usual,
+The + and - prefixes signify greater than and less than, as usual,
but bear in mind that the size is rounded up to the next unit (so a
1-byte file is not matched by
.BR "-size -1M" ).
@@ -905,7 +905,7 @@ File was last accessed \fIn\fR days after its status was last changed.
File is owned by user \fIuname\fR (numeric user ID allowed).
.IP "\-wholename \fIpattern\fR"
-See \-path. This alternative is less portable than
+See \-path. This alternative is less portable than
.BR \-path .
.IP "\-writable"
@@ -1213,7 +1213,7 @@ available on all systems, due to differences in `strftime' between
systems.
.RS
.IP @
-seconds since Jan. 1, 1970, 00:00 GMT, with fractional part.
+seconds since Jan.\& 1, 1970, 00:00 GMT, with fractional part.
.PP
Time fields:
.IP H
@@ -1283,7 +1283,7 @@ last two digits of year (00..99)
year (1970...)
.RE
.IP %b
-The amount of disk space used for this file in 512-byte blocks. Since disk
+The amount of disk space used for this file in 512-byte blocks. Since disk
space is allocated in multiples of the filesystem block size this is usually
greater than %s/512, but it can also be smaller if the file is a sparse file.
.IP %c
@@ -1315,7 +1315,7 @@ Starting-point under which file was found.
.IP %i
File's inode number (in decimal).
.IP %k
-The amount of disk space used for this file in 1K blocks. Since disk space is
+The amount of disk space used for this file in 1K blocks. Since disk space is
allocated in multiples of the filesystem block size this is usually greater
than %s/1024, but it can also be smaller if the file is a sparse file.
.IP %l
@@ -1405,7 +1405,7 @@ section for information about how unusual characters in filenames are handled.
.RE
.IP \-prune
-True; if the file is a directory, do not descend into it. If
+True; if the file is a directory, do not descend into it. If
.B \-depth
is given, false; no effect. Because
.B \-delete
@@ -1423,7 +1423,7 @@ paths specified on the command line will be processed. For example,
will print only
.BR /tmp/foo .
Any command lines which have been built up with
-.B \-execdir ... {} +
+.B \-execdir \&...\& {} +
will be invoked before
.B find
exits. The exit status may or may not be zero, depending on whether
@@ -1533,7 +1533,7 @@ Same as \fIexpr1\fR
.IP "\fIexpr1\fR , \fIexpr2\fR"
List; both \fIexpr1\fR and \fIexpr2\fR are always evaluated. The
value of \fIexpr1\fR is discarded; the value of the list is the value
-of \fIexpr2\fR. The comma operator can be useful for searching for
+of \fIexpr2\fR. The comma operator can be useful for searching for
several different types of thing, but traversing the filesystem
hierarchy only once. The
.B \-fprintf
@@ -1571,7 +1571,7 @@ Interpretation of the response is according to the "yes" and "no"
patterns selected by setting the `LC_MESSAGES' environment variable.
When the `POSIXLY_CORRECT' environment variable is set, these patterns
are taken system's definition of a positive (yes) or negative (no)
-response. See the system's
+response. See the system's
documentation for \fBnl_langinfo\fP(3), in particular YESEXPR and
NOEXPR. When `POSIXLY_CORRECT' is not set, the patterns are instead
taken from
@@ -1639,7 +1639,7 @@ The
.B find
utility shall detect infinite loops; that is, entering a
previously visited directory that is an ancestor of the last file
-encountered. When it detects an infinite loop, find shall write a
+encountered. When it detects an infinite loop, find shall write a
diagnostic message to standard error and shall either recover its
position in the hierarchy or terminate.
.P
@@ -1839,7 +1839,7 @@ on every file.
.P
.nf
-.B find . \-type f \-exec file \(aq{}\(aq \e\;
+.B find . \-type f \-exec file \(aq{}\(aq \e;
.fi
Runs `file' on every file in or below the current directory. Notice
@@ -1971,7 +1971,7 @@ but omits files and directories named
ends in
.BR ~ ,
but not their contents. The construct
-.B \-prune \-o \e( ... \-print0 \e)
+.B \-prune \-o \e( \&...\& \-print0 \e)
is quite common. The idea here is that the expression before
.B \-prune
matches things which are to be pruned. However, the
@@ -2030,12 +2030,12 @@ on the correctness of the results of
When some error occurs,
.B find
-may stop immeidately, without completing all the actions specified.
+may stop immediately, without completing all the actions specified.
For example, some starting points may not have been examined or some
pending program invocations for
-.B \-exec ... {} +
+.B \-exec \&...\& {} +
or
-.B \-execdir ... {} +
+.B \-execdir \&...\& {} +
may not have been performed.
@@ -2045,7 +2045,7 @@ may not have been performed.
\fBlstat\fP(2), \fBls\fP(1), \fBprintf\fP(3), \fBstrftime\fP(3),
\fBctime\fP(3)
-The full documentation for
+The full documentation for
.B find
is maintained as a Texinfo manual. If the
.B info