A bunch of typofixes

4 files changed, 8 insertions, 8 deletions

diff --git a/docs/ghci/ghci.tex b/docs/ghci/ghci.tex
index c4638a6719..e4fbb0b771 100644
--- a/docs/ghci/ghci.tex
+++ b/docs/ghci/ghci.tex
@@ -458,9 +458,9 @@ date.  There are three parts to it:
    \item
       {\bf Package Symbol Table (PST)} @:: FiniteMap Module ModDetails@
 
-   Adding an package interface to PIT doesn't make it directly usable
+   Adding a package interface to PIT doesn't make it directly usable
    to @compile@, because it first needs to be wired (renamed +
-   typechecked) into the sphagetti of the HST.  On the other hand,
+   typechecked) into the spaghetti of the HST.  On the other hand,
    most modules only use a few entities from any imported interface,
    so wiring-in the interface at PIT-entry time might be a big time
    waster.  Also, wiring in an interface could mean reading other
@@ -886,14 +886,14 @@ trees in the GHCI heap.  References from other modules to these
 entities is direct -- when you have a @TyCon@ in your hand, you really
 have a pointer directly to the @TyCon@ structure in the defining module,
 rather than some kind of index into a global symbol table.  So there
-is a global symbol table, but it has a distributed (sphagetti-like?)
+is a global symbol table, but it has a distributed (spaghetti-like?)
 nature.
 
 This gives fast and convenient access to tycon, class, instance,
 etc, information.  But because there are no levels of indirection,
 there's a problem when we replace @M@ with an updated version of @M@.
 We then need to find all references to entities in the old @M@'s
-sphagetti, and replace them with pointers to the new @M@'s sphagetti.
+spaghetti, and replace them with pointers to the new @M@'s spaghetti.
 This problem motivates a large part of the design.
 
 
diff --git a/docs/users_guide/glasgow_exts.rst b/docs/users_guide/glasgow_exts.rst
index edfee6c7ee..9402885774 100644
--- a/docs/users_guide/glasgow_exts.rst
+++ b/docs/users_guide/glasgow_exts.rst
@@ -8868,7 +8868,7 @@ you must ``import Data.Kind`` to get ``*`` (but only with :ghc-flag:`-XTypeInTyp
 enabled).
 
 The only way ``*`` is unordinary is in its parsing. In order to be backward
-compatible, ``*`` is parsed as if it were an alphanumeric idenfifier; note
+compatible, ``*`` is parsed as if it were an alphanumeric identifier; note
 that we do not write ``Int :: (*)`` but just plain ``Int :: *``. Due to the
 bizarreness with which ``*`` is parsed--and the fact that it is the only such
 operator in GHC--there are some corner cases that are
@@ -12189,7 +12189,7 @@ A simple example of the new notation is the expression ::
 We call this a procedure or arrow abstraction. As with a lambda
 expression, the variable ``x`` is a new variable bound within the
 ``proc``-expression. It refers to the input to the arrow. In the above
-example, ``-<`` is not an identifier but an new reserved symbol used for
+example, ``-<`` is not an identifier but a new reserved symbol used for
 building commands from an expression of arrow type and an expression to
 be fed as input to that arrow. (The weird look will make more sense
 later.) It may be read as analogue of application for arrows. The above
diff --git a/docs/users_guide/safe_haskell.rst b/docs/users_guide/safe_haskell.rst
index 7be442e036..6b32826235 100644
--- a/docs/users_guide/safe_haskell.rst
+++ b/docs/users_guide/safe_haskell.rst
@@ -358,7 +358,7 @@ imported module ``N`` changing the behaviour of existing code. For example,
 if the second condition isn't violated, then the module author ``M`` must
 depend either on a type-class or type defined in ``N``.
 
-When an particular type-class method call is considered unsafe due to
+When a particular type-class method call is considered unsafe due to
 overlapping instances, and the module being compiled is using :ghc-flag:`-XSafe`
 or :ghc-flag:`-XTrustworthy`, then compilation will fail. For :ghc-flag:`-XUnsafe`, no
 restriction is applied, and for modules using safe inference, they will
diff --git a/docs/users_guide/separate_compilation.rst b/docs/users_guide/separate_compilation.rst
index 29ee7bb1aa..0de5eb59cd 100644
--- a/docs/users_guide/separate_compilation.rst
+++ b/docs/users_guide/separate_compilation.rst
@@ -650,7 +650,7 @@ There are several points to note here:
 
 -  Just as compiling ``A.hs`` produces an interface file ``A.hi``, and
    an object file ``A.o``, so compiling ``A.hs-boot`` produces an
-   interface file ``A.hi-boot``, and an pseudo-object file ``A.o-boot``:
+   interface file ``A.hi-boot``, and a pseudo-object file ``A.o-boot``:
 
    -  The pseudo-object file ``A.o-boot`` is empty (don't link it!), but
       it is very useful when using a Makefile, to record when the