[commit: ghc] master: Typos in comments (ae1f271)

[git at git.haskell.org]

Repository : ssh://git@git.haskell.org/ghc

On branch  : master
Link       : http://ghc.haskell.org/trac/ghc/changeset/ae1f2718e795feb908fdeba87b4945f5566d6d1a/ghc

>---------------------------------------------------------------

commit ae1f2718e795feb908fdeba87b4945f5566d6d1a
Author: Gabor Greif <ggreif at gmail.com>
Date:   Wed Dec 17 16:13:26 2014 +0100

    Typos in comments


>---------------------------------------------------------------

ae1f2718e795feb908fdeba87b4945f5566d6d1a
 compiler/simplCore/Simplify.hs     | 2 +-
 compiler/typecheck/TcHsType.hs     | 2 +-
 compiler/typecheck/TcSimplify.hs   | 2 +-
 compiler/typecheck/TcTyClsDecls.hs | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/compiler/simplCore/Simplify.hs b/compiler/simplCore/Simplify.hs
index b950f57..db7f5a6 100644
--- a/compiler/simplCore/Simplify.hs
+++ b/compiler/simplCore/Simplify.hs
@@ -2644,7 +2644,7 @@ Note [Funky mkPiTypes]
 ~~~~~~~~~~~~~~~~~~~~~~
 Notice the funky mkPiTypes.  If the contructor has existentials
 it's possible that the join point will be abstracted over
-type varaibles as well as term variables.
+type variables as well as term variables.
  Example:  Suppose we have
         data T = forall t.  C [t]
  Then faced with
diff --git a/compiler/typecheck/TcHsType.hs b/compiler/typecheck/TcHsType.hs
index 44ba79b..1221b7f 100644
--- a/compiler/typecheck/TcHsType.hs
+++ b/compiler/typecheck/TcHsType.hs
@@ -1374,7 +1374,7 @@ Here the type of x's first component is called 'a1' in one branch and
 they definitely won't have the sane lexical Name.
 
 I think we could solve this by recording in a SigTv a list of all the
-in-scope varaibles that it should not unify with, but it's fiddly.
+in-scope variables that it should not unify with, but it's fiddly.
 
 
 ************************************************************************
diff --git a/compiler/typecheck/TcSimplify.hs b/compiler/typecheck/TcSimplify.hs
index 7e9c408..01da61f 100644
--- a/compiler/typecheck/TcSimplify.hs
+++ b/compiler/typecheck/TcSimplify.hs
@@ -634,7 +634,7 @@ and if so refrain from quantifying over *any* equalites.
 simplifyRule :: RuleName
              -> WantedConstraints       -- Constraints from LHS
              -> WantedConstraints       -- Constraints from RHS
-             -> TcM ([EvVar], WantedConstraints)   -- LHS evidence varaibles
+             -> TcM ([EvVar], WantedConstraints)   -- LHS evidence variables
 -- See Note [Simplifying RULE constraints] in TcRule
 simplifyRule name lhs_wanted rhs_wanted
   = do {         -- We allow ourselves to unify environment
diff --git a/compiler/typecheck/TcTyClsDecls.hs b/compiler/typecheck/TcTyClsDecls.hs
index 2ff482c..595e853 100644
--- a/compiler/typecheck/TcTyClsDecls.hs
+++ b/compiler/typecheck/TcTyClsDecls.hs
@@ -1095,7 +1095,7 @@ Then in the family instance we want to
                      KindFam (Maybe k) k' a b = T k k' a b -> Int
 
 Notice that in the third step we quantify over all the visibly-mentioned
-type variables (a,b), but also over the implicitly mentioned kind varaibles
+type variables (a,b), but also over the implicitly mentioned kind variables
 (k, k').  In this case one is bound explicitly but often there will be
 none. The role of the kind signature (a :: Maybe k) is to add a constraint
 that 'a' must have that kind, and to bring 'k' into scope.