1.0.11.16: Fix tyops in the manual

  * Patch submitted by Eugene Ossintsev

diff --git a/doc/manual/compiler.texinfo b/doc/manual/compiler.texinfo
index e9c2e82..c23af6a 100644 (file)
--- a/doc/manual/compiler.texinfo
+++ b/doc/manual/compiler.texinfo
@@ -1098,7 +1098,7 @@ a more efficient calling convention that forbids redefinition.
 
 By default SBCL implements @code{eval} by calling the native code
 compiler. SBCL also includes an interpreter for use in special cases
-where using the compiler is undesireable, for example due to compilation
+where using the compiler is undesirable, for example due to compilation
 overhead. Unlike in some other Lisp implementations, in SBCL interpreted
 code is not safer or more debuggable than compiled code.
 

diff --git a/doc/manual/ffi.texinfo b/doc/manual/ffi.texinfo
index cfdd1d2..b4fc8ca 100644 (file)
--- a/doc/manual/ffi.texinfo
+++ b/doc/manual/ffi.texinfo
@@ -64,7 +64,7 @@ use of extensions to the Lisp language.
 
 SBCL, like CMUCL before it, relies primarily on the automatic
 conversion and direct manipulation approaches. The @code{SB-ALIEN}
-package provices a facility wherein foreign values of simple scalar
+package provides a facility wherein foreign values of simple scalar
 types are automatically converted and complex types are directly
 manipulated in their foreign representation.  Additionally the
 lower-level System Area Pointers (or @acronym{SAP}s) can be used where
@@ -462,7 +462,7 @@ argument, but it does refer to the same foreign data bits.
 
 The @code{sb-alien:sap-alien} function converts @var{sap} (a system
 area pointer) to a foreign value with the specified
-@var{type}. @var{type} is not evaluated.  </para>
+@var{type}. @var{type} is not evaluated.
 
 The @var{type} must be some foreign pointer, array, or record type.
 @end defun

diff --git a/doc/manual/intro.texinfo b/doc/manual/intro.texinfo
index 0f8fc41..ca6ab0f 100644 (file)
--- a/doc/manual/intro.texinfo
+++ b/doc/manual/intro.texinfo
@@ -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

diff --git a/doc/manual/package-locks-extended.texinfo b/doc/manual/package-locks-extended.texinfo
index 1dbbdd3..4e34560 100644 (file)
--- a/doc/manual/package-locks-extended.texinfo
+++ b/doc/manual/package-locks-extended.texinfo
@@ -149,7 +149,7 @@ runtime, and code compiled with packages locked may or may not signal
 spurious package-lock-violations at runtime even if the packages are
 unlocked.
 
-In practice all this means that package-locks have a neglible
+In practice all this means that package-locks have a negligible
 performance penalty in compiled code as long as they are not violated.
 
 @node Operations Violating Package Locks
@@ -313,7 +313,7 @@ Syntax: @code{(sb-ext:enable-package-locks symbol*)}
 
 Re-enables package locks affecting the named symbols during compilation
 in the lexical scope of the declaration. Enabling locks that were not
-first disabled with @code{sb-ext:disable-package-locks} declararion, or
+first disabled with @code{sb-ext:disable-package-locks} declaration, or
 enabling locks that are already enabled has no effect.
 @end deftp
 

diff --git a/doc/manual/threading.texinfo b/doc/manual/threading.texinfo
index 57eaf58..6219f67 100644 (file)
--- a/doc/manual/threading.texinfo
+++ b/doc/manual/threading.texinfo
@@ -116,7 +116,7 @@ if you want a bounded wait.
 @comment  node-name,  next,  previous,  up
 @section Semaphores
 
-escribed here should be considered
+described here should be considered
 experimental, subject to API changes without notice.
 
 @include struct-sb-thread-semaphore.texinfo

diff --git a/doc/manual/timers.texinfo b/doc/manual/timers.texinfo
index 45e617e..f4687e5 100644 (file)
--- a/doc/manual/timers.texinfo
+++ b/doc/manual/timers.texinfo
@@ -4,7 +4,7 @@
 
 SBCL supports a system-wide scheduler implemented on top of
 @code{setitimer} that also works with threads but does not require a
-separate schduler thread.
+separate scheduler thread.
 
 @menu
 @end menu

diff --git a/version.lisp-expr b/version.lisp-expr
index bb8085f..63b0325 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.11.15"
+"1.0.11.16"