Spelling fixes.

3 files changed, 3 insertions, 4 deletions

diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi
index 6a18bea2977..79fd352adfb 100644
--- a/doc/lispref/loading.texi
+++ b/doc/lispref/loading.texi
@@ -615,7 +615,7 @@ specified by an autoload object:
 
 @defun autoload-do-load autoload &optional name macro-only
 This function performs the loading specified by @var{autoload}, which
-whould be an autoload object.  The optional argument @var{name}, if
+should be an autoload object.  The optional argument @var{name}, if
 non-@code{nil}, should be a symbol whose function value is
 @var{autoload}; in that case, the return value of this function is the
 symbol's new function value.  If the value of the optional argument
diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi
index 580dd8258df..88b7909126e 100644
--- a/doc/lispref/variables.texi
+++ b/doc/lispref/variables.texi
@@ -2033,7 +2033,7 @@ itself be a valid @var{place} form.  For example, @code{(setf (nthcdr
 @c to standard Common Lisp.
 
 @c FIXME I don't think is a particularly good way to do it,
-@c but these macros are introduced before gvs are.
+@c but these macros are introduced before generalized variables are.
 The macros @code{push} (@pxref{List Variables}) and @code{pop}
 (@pxref{List Elements}) can manipulate generalized variables,
 not just lists.  @code{(pop @var{place})} removes and returns the first
diff --git a/doc/misc/cl.texi b/doc/misc/cl.texi
index d01798497da..10735420534 100644
--- a/doc/misc/cl.texi
+++ b/doc/misc/cl.texi
@@ -991,7 +991,7 @@ has been made.  @xref{Obsolete Setf Customization}.
 
 @c FIXME should this be in lispref?  It seems self-evident.
 @c Contrast with the cl-incf example later on.
-@c Here it really only serves as a constrast to wrong-order.
+@c Here it really only serves as a contrast to wrong-order.
 The @code{setf} macro takes care to evaluate all subforms in
 the proper left-to-right order; for example,
 
@@ -5129,4 +5129,3 @@ defined later.
 @printindex vr
 
 @bye
-