Fix typos

7 files changed, 9 insertions, 9 deletions

diff --git a/docs/users_guide/debugging.rst b/docs/users_guide/debugging.rst
index 87a689c268..83d093cd06 100644
--- a/docs/users_guide/debugging.rst
+++ b/docs/users_guide/debugging.rst
@@ -980,8 +980,8 @@ Checking for consistency
     :type: dynamic
 
     Turn on linearity checking in GHC. Currently, some optimizations
-    in GHC might not preserve linearity and they valid programs might
-    fail Linear Core Lint.
+    in GHC might not preserve linearity and there are valid programs
+    that fail Linear Core Lint.
     In the near future, this option will be removed and folded into
     normal Core Lint.
 
diff --git a/docs/users_guide/exts/existential_quantification.rst b/docs/users_guide/exts/existential_quantification.rst
index 87b15acd0d..568eb63b7b 100644
--- a/docs/users_guide/exts/existential_quantification.rst
+++ b/docs/users_guide/exts/existential_quantification.rst
@@ -248,7 +248,7 @@ constructors can be used.
 
 -  You can't use ``deriving`` to define instances of a data type with
    existentially quantified data constructors. Reason: in most cases it
-   would not make sense. For example:; ::
+   would not make sense. For example: ::
 
        data T = forall a. MkT [a] deriving( Eq )
 
diff --git a/docs/users_guide/exts/lambda_case.rst b/docs/users_guide/exts/lambda_case.rst
index ca648fa904..4712da3d74 100644
--- a/docs/users_guide/exts/lambda_case.rst
+++ b/docs/users_guide/exts/lambda_case.rst
@@ -18,7 +18,7 @@ which is equivalent to ::
 
       \freshName -> case freshName of { p1 -> e1; ...; pN -> eN }
 
-Since GHC 9.4.1, it also allow expressions with multiple scrutinees (see GHC
+Since GHC 9.4.1, it also allows expressions with multiple scrutinees (see GHC
 proposal `#302 <https://github.com/ghc-proposals/ghc-proposals/blob/master/proposals/0302-cases.rst>`_)
 of the form ::
 
diff --git a/docs/users_guide/exts/qualified_do.rst b/docs/users_guide/exts/qualified_do.rst
index 71c43c5655..050a5bfce6 100644
--- a/docs/users_guide/exts/qualified_do.rst
+++ b/docs/users_guide/exts/qualified_do.rst
@@ -85,7 +85,7 @@ The semantics of ``do`` notation statements with ``-XQualifiedDo`` is as follows
     M.do { pat <- u; stmts }  =  u M.>>= \case pat -> M.do { stmts }
 
 *  The desugaring of ``-XApplicativeDo`` uses ``M.fmap``, ``(M.<*>)``,
-   and ``M.join`` (after the the applicative-do grouping has been performed) ::
+   and ``M.join`` (after the applicative-do grouping has been performed) ::
 
     M.do { (x1 <- u1 | … | xn <- un); M.return e }  =
       (\x1 … xn -> e) `M.fmap` u1 M.<*> … M.<*> un
diff --git a/docs/users_guide/exts/record_field_resolution.rst b/docs/users_guide/exts/record_field_resolution.rst
index 3209387d26..fba686d42a 100644
--- a/docs/users_guide/exts/record_field_resolution.rst
+++ b/docs/users_guide/exts/record_field_resolution.rst
@@ -21,7 +21,7 @@ Those rules are amended by the following extensions:
 * :extension:`DisambiguateRecordFields`: In record construction and pattern matching
   (``C{ x = …}``), an unqualified field name ``x`` is unambiguous if and only if the data constructor (``C``)
   has a field ``x``, and that field is in scope unqualified, or qualified as ``Q.x``, regardless of ``Q``.
-  Similarly, in record construction and pattern matching, a qualified field name ``M.x`` is unambiguous if and only if the the data
+  Similarly, in record construction and pattern matching, a qualified field name ``M.x`` is unambiguous if and only if the data
   constructor (``C``) has a field ``x``, and that field is in scope qualified as ``M.x``.
 
   In record updates (``r{ x = 3 }``), the field name x is unambiguous if and only if there is just one field name x in scope unqualified.
@@ -51,7 +51,7 @@ refer unambiguously to data type ``S``.
     data T = MkT { x :: Int }
 
     x :: String
-    x = "Hello
+    x = "Hello"
 
     f = x
 
diff --git a/docs/users_guide/exts/record_wildcards.rst b/docs/users_guide/exts/record_wildcards.rst
index d926a85b39..aff4cccf73 100644
--- a/docs/users_guide/exts/record_wildcards.rst
+++ b/docs/users_guide/exts/record_wildcards.rst
@@ -75,7 +75,7 @@ More details:
    ``c`` is not in scope (apart from the binding of the record selector
    ``c``, of course).
 
--  When record wildcards are use in record construction, a field ``f``
+-  When record wildcards are used in record construction, a field ``f``
    is initialised only if ``f`` is in scope,
    and is not imported or bound at top level.
    For example, ``f`` can be bound by an enclosing pattern match or
diff --git a/docs/users_guide/using-optimisation.rst b/docs/users_guide/using-optimisation.rst
index 02f1fd50f6..b5f8c5bb29 100644
--- a/docs/users_guide/using-optimisation.rst
+++ b/docs/users_guide/using-optimisation.rst
@@ -335,7 +335,7 @@ by saying ``-fno-wombat``.
 
     CPR analysis will see that each code path produces a *constructed product*
     such as ``I# 0#`` in the first branch (where ``GHC.Exts.I#`` is the data
-    constructor of ``Int``, boxing up the the primitive integer literal ``0#``
+    constructor of ``Int``, boxing up the primitive integer literal ``0#``
     of type ``Int#``) and optimise to ::
 
          sum xs = I# ($wsum xs)