X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Fmanual%2Fpackage-locks-extended.texinfo;h=4e3456075696513e4a042d4eedb95ed8027c7097;hb=7f96d22df74999904529adc41639b64f88f5a144;hp=f99388854c6f6c63416af46f68e6a5d853ea513d;hpb=25d4ea4f108159b9782f21212374a1631cfe9a56;p=sbcl.git

diff --git a/doc/manual/package-locks-extended.texinfo b/doc/manual/package-locks-extended.texinfo
index f993888..4e34560 100644
--- a/doc/manual/package-locks-extended.texinfo
+++ b/doc/manual/package-locks-extended.texinfo
@@ -10,7 +10,7 @@ The interface described here is experimental: incompatible changes in
 future SBCL releases are possible, even expected: the concept of
 ``implementation packages'' and the associated operators may be renamed;
 more operations (such as naming restarts or catch tags) may be added to
-the the list of operations violating package locks.
+the list of operations violating package locks.
 
 @menu
 * Package Lock Concepts::       
@@ -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