Manual: whitespace and missing @noindent

Thanks, once again, to Mark Harig.

3 files changed, 12 insertions, 5 deletions

diff --git a/doc/install.texi b/doc/install.texi
index 745f398..38703e0 100644
--- a/doc/install.texi
+++ b/doc/install.texi
@@ -52,6 +52,7 @@ git clone git://git.sv.gnu.org/geiser.git
 git clone http://git.sv.gnu.org/r/geiser.git
 @end example
 
+@noindent
 You can also follow Geiser's development in
 @uref{https://github.com/jaor/geiser, one}
 @uref{http://repo.or.cz/w/geiser.git, or}
@@ -181,6 +182,7 @@ also probably a good idea to require @code{quack} @i{after} loading
 @file{geiser.el} (or requiring a compiled version).
 @end itemize
 
+@noindent
 You just need to install and setup them as usual, for every package's
 definition of usual.  Geiser will notice their presence and react
 accordingly.
diff --git a/doc/parens.texi b/doc/parens.texi
index b72e03f..89b60a1 100644
--- a/doc/parens.texi
+++ b/doc/parens.texi
@@ -103,6 +103,7 @@ subsection}.
 @cindex scheme implementation, choosing
 To determine what Scheme implementation corresponds to a given source
 file, Geiser uses the following algorithm:
+
 @enumerate
 @item
 If the file-local variable @code{geiser-scheme-implementation} is
@@ -137,6 +138,7 @@ See?  That's the problem of being a smart aleck: one's always outsmarted
 by people around.  At this point, @i{geiser-mode} will humbly give up and
 ask you to explicitly choose the Scheme implementation.
 @end enumerate
+
 As you can see in the list above, there are several ways to influence
 Geiser's guessing by mean customizable variables.  The most direct (and
 most impoverishing) is probably limiting the active implementations to a
@@ -150,7 +152,8 @@ default value for the latter variable:
  ((regexp "\\.rkt$") racket))
 @end example
 
-@noindent which describes the simple heuristic that files with @file{.scm} as
+@noindent
+which describes the simple heuristic that files with @file{.scm} as
 extension are by default associated to a Guile REPL while those ending
 in @file{.ss} or @file{.rkt} correspond to Racket's implementation (with
 the caveat that these rules are applied only if the previous heuristics
@@ -286,7 +289,7 @@ madness).
 You can change the way Geiser displays the module/identifier combo by
 customizing @code{geiser-autodoc-identifier-format}.  For example, if you
 wanted a tilde surrounded by spaces instead of a colon as a separator,
-you would write something like
+you would write something like:
 
 @example
 (setq geiser-autodoc-identifier-format "%s ~ %s")
diff --git a/doc/repl.texi b/doc/repl.texi
index 03361fd..bded2b7 100644
--- a/doc/repl.texi
+++ b/doc/repl.texi
@@ -282,13 +282,14 @@ directly your Scheme of choice via @command{run-racket} or
 variable @code{geiser-active-implementations} contains a list of those
 Schemes Geiser should be aware of.  Thus, if you happen to be, say, a
 racketeer not to be beguiled by other schemes, you can tell Geiser to
-forget about the richness of the Scheme ecosystem with something like
+forget about the richness of the Scheme ecosystem with something like:
 
 @example
 (setq geiser-active-implementations '(racket))
 @end example
 
-@noindent in your initialisation files.
+@noindent
+in your initialisation files.
 
 @cindex scheme binary
 @cindex scheme executable path
@@ -322,7 +323,8 @@ example, my Geiser configuration includes the following line:
 (setq geiser-repl-history-filename "~/.emacs.d/geiser-history")
 @end example
 
-@noindent which makes the files @file{geiser-history.guile} and
+@noindent
+which makes the files @file{geiser-history.guile} and
 @file{geiser-history.racket} to live inside my home's @file{.emacs.d}
 directory.