Fix typos

6 files changed, 6 insertions, 6 deletions

diff --git a/docs/users_guide/debugging.rst b/docs/users_guide/debugging.rst
index f0a929df5e..cc96dbc775 100644
--- a/docs/users_guide/debugging.rst
+++ b/docs/users_guide/debugging.rst
@@ -1062,7 +1062,7 @@ Other
     :shortdesc: Don't generate bindings for Typeable methods
     :type: dynamic
 
-    This avoid generating Typeable-related bindings for modules and types. This
+    This avoids generating Typeable-related bindings for modules and types. This
     is useful when debugging because it gives smaller modules and dumps, but the
     compiler will panic if you try to use Typeable instances of things that you
     built with this flag.
diff --git a/docs/users_guide/exts/gadt.rst b/docs/users_guide/exts/gadt.rst
index 00820739c9..3463bd63da 100644
--- a/docs/users_guide/exts/gadt.rst
+++ b/docs/users_guide/exts/gadt.rst
@@ -132,7 +132,7 @@ also sets :extension:`GADTSyntax` and :extension:`MonoLocalBinds`.
       alternatives must be rigid.
 
    A type is "rigid" if it is completely known to the compiler at its
-   binding site. The easiest way to ensure that a variable a rigid type
+   binding site. The easiest way to ensure that a variable has a rigid type
    is to give it a type signature. For more precise details see `Simple
    unification-based type inference for
    GADTs <https://research.microsoft.com/%7Esimonpj/papers/gadt/>`__. The
diff --git a/docs/users_guide/exts/safe_haskell.rst b/docs/users_guide/exts/safe_haskell.rst
index da62f093b2..5ceb15aa9f 100644
--- a/docs/users_guide/exts/safe_haskell.rst
+++ b/docs/users_guide/exts/safe_haskell.rst
@@ -173,7 +173,7 @@ guarantee that the code is safe. Or those modules compiled with
 Safe.
 
 This is why the RIO module is compiled with :extension:`Safe` or
-:extension:`Trustworthy`>, to allow the ``Danger`` module to import it. The
+:extension:`Trustworthy`, to allow the ``Danger`` module to import it. The
 :extension:`Trustworthy` flag doesn't place any restrictions on the module like
 :extension:`Safe` does (expect to restrict overlapping instances to `safe
 overlapping instances <#safe-overlapping-instances>`__). Instead the
diff --git a/docs/users_guide/ghci.rst b/docs/users_guide/ghci.rst
index 427829da99..9995814920 100644
--- a/docs/users_guide/ghci.rst
+++ b/docs/users_guide/ghci.rst
@@ -534,7 +534,7 @@ not to replace module loading but to make definitions in .ghci-files
 Any exceptions raised during the evaluation or execution of the
 statement are caught and printed by the GHCi command line interface (for
 more information on exceptions, see the module :base-ref:`Control.Exception.` in
-the libraries documentation.
+the libraries documentation.)
 
 Every new binding shadows any existing bindings of the same name,
 including entities that are in scope in the current module context.
diff --git a/docs/users_guide/hints.rst b/docs/users_guide/hints.rst
index 0d011a2563..7365cb5696 100644
--- a/docs/users_guide/hints.rst
+++ b/docs/users_guide/hints.rst
@@ -236,7 +236,7 @@ Look at the Core syntax!
     their Core code. ``lets`` are bad, ``cases`` are good, dictionaries
     (``d.⟨Class⟩.⟨Unique⟩``) [or anything overloading-ish] are bad,
     nested lambdas are bad, explicit data constructors are good,
-    primitive operations (e.g., ``eqInt#``) are good, ...
+    primitive operations (e.g., ``==#``) are good, ...
 
 Use strictness annotations:
     Putting a strictness annotation (``!``) on a constructor field helps
diff --git a/docs/users_guide/using-optimisation.rst b/docs/users_guide/using-optimisation.rst
index 36fc057890..37e4a4aae6 100644
--- a/docs/users_guide/using-optimisation.rst
+++ b/docs/users_guide/using-optimisation.rst
@@ -1311,7 +1311,7 @@ by saying ``-fno-wombat``.
     sub-demand* that says "Called at most once, where the result is used
     according to ``L``". The expression ``f `seq` f 1`` puts ``f`` under
     demand ``SC1(L)`` and serves as an example where the upper bound on
-    evaluation cardinality doesn't conincide with that of the call cardinality.
+    evaluation cardinality doesn't coincide with that of the call cardinality.
 
     Cardinality is always relative to the enclosing call cardinality, so
     ``g 1 2 + g 3 4`` puts ``g`` under demand ``SCS(C1(L))``, which says