diff --git a/doc/ref/scheme-scripts.texi b/doc/ref/scheme-scripts.texi
index 5a151a4fd..225b34b88 100644
--- a/doc/ref/scheme-scripts.texi
+++ b/doc/ref/scheme-scripts.texi
@@ -199,13 +199,13 @@ If @var{p} is not given, the default is local port 37146.  If you look
 at it upside down, it almost spells ``Guile''.  If you have netcat
 installed, you should be able to @kbd{nc localhost 37146} and get a
 Guile prompt.  Alternately you can fire up Emacs and connect to the
-procedure; see @ref{Using Guile in Emacs} for more details.
+process; see @ref{Using Guile in Emacs} for more details.
 
 Note that opening a port allows anyone who can connect to that port---in
 the TCP case, any local user---to do anything Guile can do, as the user
 that the Guile process is running as.  Don't use @option{--listen} on
-multi-user machines.  Of course, if there is no @option{--listen}
-argument, no port will be opened.
+multi-user machines.  Of course, if you don't pass @option{--listen} to
+Guile, no port will be opened.
 
 That said, @code{--listen} is great for interactive debugging and
 development.
diff --git a/doc/ref/scheme-using.texi b/doc/ref/scheme-using.texi
index 5749f027c..810ee1574 100644
--- a/doc/ref/scheme-using.texi
+++ b/doc/ref/scheme-using.texi
@@ -57,21 +57,22 @@ scheme@@(guile-user)> (use-modules (ice-9 readline))
 scheme@@(guile-user)> (activate-readline)
 @end lisp
 
-It's a good idea to put these two lines (without the ``scheme@@(guile-user)>''
-prompts) in your @file{.guile} file.  Guile reads this file when it
-starts up interactively, so anything in this file has the same effect
-as if you type it in by hand at the ``scheme@@(guile-user)>'' prompt.
+It's a good idea to put these two lines (without the
+@code{scheme@@(guile-user)>} prompts) in your @file{.guile} file.  Guile
+reads this file when it starts up interactively, so anything in this
+file has the same effect as if you type it in by hand at the
+@code{scheme@@(guile-user)>} prompt.
 
 
 @node Value History
 @subsection Value History
 
 Just as Readline helps you to reuse a previous input line, @dfn{value
-history} allows you to use the @emph{result} of a previous evaluation
-in a new expression.  When value history is enabled, each evaluation
-result is automatically assigned to the next in the sequence of
-variables @code{$1}, @code{$2}, @dots{}, and you can then use these
-variables in subsequent expressions.
+history} allows you to use the @emph{result} of a previous evaluation in
+a new expression.  When value history is enabled, each evaluation result
+is automatically assigned to the next in the sequence of variables
+@code{$1}, @code{$2}, @dots{}.  You can then use these variables in
+subsequent expressions.
 
 @lisp
 scheme@@(guile-user)> (iota 10)
@@ -175,7 +176,7 @@ had by typing @samp{,help}. Indeed, @code{help} is a command, and a
 particularly useful one, as it allows the user to discover the rest of
 the commands.
 
-@deffn {REPL Command} help [@samp{all} | group | @samp{[-c]} command]
+@deffn {REPL Command} help [@code{all} | group | @code{[-c]} command]
 Show help.
 
 With one argument, tries to look up the argument as a group name, giving
diff --git a/doc/ref/tour.texi b/doc/ref/tour.texi
index 9d378da8c..2215cf034 100644
--- a/doc/ref/tour.texi
+++ b/doc/ref/tour.texi
@@ -59,7 +59,7 @@ script is simply a file of Scheme code with some extra information at
 the beginning which tells the operating system how to invoke Guile, and
 then tells Guile how to handle the Scheme code.
 
-Here is a trivial Guile script, for more details @xref{Guile Scripting}.
+Here is a trivial Guile script.  @xref{Guile Scripting}, for more details.
 
 @example
 #!/usr/local/bin/guile -s
@@ -136,8 +136,8 @@ You can link Guile into your program and make Scheme available to the
 users of your program.  You can also link your library into Guile and
 make its functionality available to all users of Guile.
 
-A library that is linked into Guile is called an @dfn{extensions}, but
-it really just is an ordinary object library.
+A library that is linked into Guile is called an @dfn{extension}, but it
+really just is an ordinary object library.
 
 The following example shows how to write a simple extension for Guile
 that makes the @code{j0} function available to Scheme code.
@@ -357,7 +357,7 @@ If you built Guile yourself, the build configuration that you used:
 
 @example
 $ ./config.status --config
-'--enable-error-on-warning' '--disable-deprecated' '--prefix=/opt/guile' '--libdir=/opt/guile/lib64' 'CC=ccache gcc'
+'--enable-error-on-warning' '--disable-deprecated'...
 @end example
 
 @item