X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Fmanual%2Fintro.texinfo;h=26b130770bb40b6f6bedcd068faa0f95ad8d473a;hb=007bcd5aac2f3a1e714563bd39f7a2db2d0bf7c2;hp=0f8fc418b58dc585c735ac6cadc0dcc997145d58;hpb=ffc7fbeb5717ecf9e3dcb85bb4c98b4ea16dc39a;p=sbcl.git

diff --git a/doc/manual/intro.texinfo b/doc/manual/intro.texinfo
index 0f8fc41..26b1307 100644
--- a/doc/manual/intro.texinfo
+++ b/doc/manual/intro.texinfo
@@ -30,8 +30,8 @@ distribution.
 
 The recommended way to report bugs is through the @cite{sbcl-help} or
 @cite{sbcl-devel} mailing lists. For mailing list addresses,
-see @ref{SBCL Homepage}.
-
+see @ref{SBCL Homepage}; note that as a spam-reduction measure you
+must subscribe before you can post.
 
 
 
@@ -93,7 +93,7 @@ processes, accessing environment variables, etc.
 facilities.
 
 @item Extensible Streams
-@code{sb-gray} is an implentation of @emph{Gray Streams}. @xref{Gray
+@code{sb-gray} is an implementation of @emph{Gray Streams}. @xref{Gray
 Streams}.
 
 @code{sb-simple-streams} is an implementation of the @emph{simple
@@ -123,7 +123,7 @@ standardization process.
 
 @item Executable Fasl Packaging
 @code{sb-executable} can be used to concatenate multiple fasls into a
-single executable (though the presense of an SBCL runtime and core image
+single executable (though the presence of an SBCL runtime and core image
 is still required to run it).
 
 The @code{:executable} argument to @ref{Function
@@ -134,7 +134,7 @@ runtime.
 @item Bitwise Rotation
 @code{sb-rotate-byte} provides an efficient primitive for bitwise
 rotation of integers, an operation required by eg. numerous
-cryptographic algorightms, but not available as a primitive in ANSI
+cryptographic algorithms, but not available as a primitive in ANSI
 Common Lisp. @xref{sb-rotate-byte}.
 
 @item Test Harness
@@ -388,10 +388,10 @@ case the documentation strings are only readable in the source code.
 @subsection Internals Documentation
 
 If you're interested in the development of the SBCL system itself,
-then subcribing to @cite{sbcl-devel} is a good idea.
+then subscribing to @cite{sbcl-devel} is a good idea.
 
 SBCL internals documentation -- besides comments in the source -- is
-currenly maitained as a @emph{wiki-like} website:
+currently maintained as a @emph{wiki-like} website:
 @uref{http://sbcl-internals.cliki.net/}.
 
 Some low-level information describing the programming details of the
@@ -494,7 +494,7 @@ freely available at @uref{http://www.lisp.org/mop/}.
 @comment  node-name,  next,  previous,  up
 @section History and Implementation of SBCL
 
-You can work productively with SBCL without knowing anything
+You can work productively with SBCL without knowing or
 understanding anything about where it came from, how it is
 implemented, or how it extends the ANSI Common Lisp standard. However,
 a little knowledge can be helpful in order to understand error
@@ -544,7 +544,7 @@ can't be used interactively, and in fact the change is largely invisible
 to the casual user, since SBCL still can and does execute code
 interactively by compiling it on the fly. (It is visible if you know how
 to look, like using @code{compiled-function-p}; and it is visible in the
-way that that SBCL doesn't have many bugs which behave differently in
+way that SBCL doesn't have many bugs which behave differently in
 interpreted code than in compiled code.) What it means is that in SBCL,
 the @code{eval} function only truly ``interprets'' a few easy kinds of
 forms, such as symbols which are @code{boundp}. More complicated forms