Typos in comments [ci skip]

compiler/hsSyn/HsImpExp.hs

@@ -139,7 +139,7 @@ instance (OutputableBndrId pass) => Outputable (ImportDecl pass) where
 ************************************************************************
 -}
 
--- | A name in an import or export specfication which may have adornments. Used
+-- | A name in an import or export specification which may have adornments. Used
 -- primarily for accurate pretty printing of ParsedSource, and API Annotation
 -- placement.
 data IEWrappedName name

compiler/main/HscMain.hs

@@ -1119,7 +1119,7 @@ markUnsafeInfer tcg_env whyUnsafe = do
              mkPlainWarnMsg dflags (warnUnsafeOnLoc dflags) (whyUnsafe' dflags))
 
     liftIO $ writeIORef (tcg_safeInfer tcg_env) (False, whyUnsafe)
-    -- NOTE: Only wipe trust when not in an explicity safe haskell mode. Other
+    -- NOTE: Only wipe trust when not in an explicitly safe haskell mode. Other
     -- times inference may be on but we are in Trustworthy mode -- so we want
     -- to record safe-inference failed but not wipe the trust dependencies.
     case safeHaskell dflags == Sf_None of

compiler/typecheck/TcHsType.hs

@@ -1845,7 +1845,7 @@ tcHsPartialSigType ctxt sig_ty
 
         ; explicit_tvs <- mapM zonkTyCoVarKind explicit_tvs
         ; let all_tvs = implicit_tvs ++ explicit_tvs
-                        -- The implicit_tvs alraedy have zonked kinds
+                        -- The implicit_tvs already have zonked kinds
 
         ; theta   <- mapM zonkTcType theta
         ; tau     <- zonkTcType tau

docs/users_guide/ffi-chap.rst

@@ -34,7 +34,7 @@ The FFI addendum stipulates that an implementation is free to implement an
 arbitrary thread and may be subject to concurrent garbage collection). This
 greatly constrains library authors since it implies that it is never safe to
 pass any heap object reference to a foreign function, even if invoked with an
-``unsafe`` call. For instance, it is often desireable to pass an unpinned
+``unsafe`` call. For instance, it is often desirable to pass an unpinned
 ``ByteArray#``\s directly to native code to avoid making an
 otherwise-unnecessary copy. However, this can only be done safely under
 ``unsafe`` call semantics as otherwise the array may be moved by the garbage

includes/stg/Ticky.h

@@ -30,7 +30,7 @@ extern W_ ticky_entry_ctrs[];
 extern W_ top_ct[];
 #endif
 
-/* The rest are not explicity declared in rts/Ticky.c.  Instead
+/* The rest are not explicitly declared in rts/Ticky.c.  Instead
    we use the same trick as in the former StgTicky.h: recycle the 
    same declarations for both extern decls (which are included everywhere)
    and initializations (which only happen once) 

rts/Apply.cmm

@@ -462,7 +462,7 @@ middle of an ST action multiple times, resulting in duplication of effects.
 In short, the construction of an AP_STACK allows us to suspend a computation
 which should not be duplicated. When running with lazy blackholing, we can then
 enter this AP_STACK multiple times, duplicating the computation with potentially
-disasterous consequences.
+disastrous consequences.
 
 For instance, consider the case of a simple ST program which computes a sum
 using in─place mutation,

rts/PrimOps.cmm

@@ -148,7 +148,7 @@ stg_isByteArrayPinnedzh ( gcptr ba )
     W_ bd, flags;
     bd = Bdescr(ba);
     // Pinned byte arrays live in blocks with the BF_PINNED flag set.
-    // We also consider BF_LARGE objects to be unmoveable. See #13894.
+    // We also consider BF_LARGE objects to be immovable. See #13894.
     // See the comment in Storage.c:allocatePinned.
     flags = TO_W_(bdescr_flags(bd));
     return (flags & (BF_PINNED | BF_LARGE) != 0);

utils/hpc/HpcFlags.hs

@@ -194,7 +194,7 @@ data Plugin = Plugin { name           :: String
 -- filterModules takes a list of candidate modules,
 -- and
 --  * excludes the excluded modules
---  * includes the rest if there are no explicity included modules
+--  * includes the rest if there are no explicitly included modules
 --  * otherwise, accepts just the included modules.
 
 allowModule :: Flags -> String -> Bool