fix typos

lib/Language/functions.pod

@@ -296,7 +296,7 @@ sub circumfix:<START END>(*@elems) {
 say START 'a', 'b', 'c' END;        # start a b c end
 =end code;
 
-Postcircumfixes also receive the the term after which they are parsed as
+Postcircumfixes also receive the term after which they are parsed as
 an argument:
 
 =begin code
@@ -314,7 +314,7 @@ tighter precedence than the one you specified, but looser than the
 next-tighter precedence level.
 
 For example C<< infix:<*> >> has a tighter precedence than C<< infix:<+> >>,
-and squeezinge one in between works like this:
+and squeezing one in between works like this:
 
 =begin code
 sub infix:<!!>($a, $b) is tighter(&infix:<+>) {
@@ -483,7 +483,7 @@ a 1;        # Int 1\n Any 1\n Bakc in Int with 5
 =end code
 
 Another common use case is to re-dispatch to the next routine in the chain,
-and not do anything else aftwards. That's why we have C<nextwith> and
+and not do anything else afterwards. That's why we have C<nextwith> and
 C<nextsame>, which call the next routine with arbitrary arguments
 (C<nextwith>) or with the same argument as the caller received (C<nextsame>),
 but never return to the caller. Or to phrase it differently, the C<nextsame>
@@ -549,7 +549,7 @@ sub double(Int(Cool) $x) {
 }
 
 say double '21';    # 42
-say dobule Any;     # Type check failed in binding $x; expected 'Cool' but got 'Any'
+say double Any;     # Type check failed in binding $x; expected 'Cool' but got 'Any'
 =end code
 
 Here the C<Int> is the target type to which the argument will be coerced, and
@@ -559,6 +559,6 @@ If the accepted input type is L<Any|/type/Any>, you can abbreviate C<Int(Any)>
 to C<Int()>.
 
 Coercion types are supposed to work wherever types work, but Rakudo currently
-(2015.02) only implements them for subroutine paramters.
+(2015.02) only implements them for subroutine parameters.
 
 =end pod

lib/Language/grammars.pod

@@ -184,7 +184,7 @@ grammar, it tries to call a method of the same name as the grammar rule,
 giving it the newly create L<Match|/type/Match> object as a positional
 argument. If no such method exists, it is skipped.
 
-Here is a contrieved example of a grammar and actions in action:
+Here is a contrived example of a grammar and actions in action:
 
 =begin code
 use v6;
@@ -252,7 +252,7 @@ for @$res -> $p {
 }
 =end code
 
-This produces the following ouput:
+This produces the following output:
 
 =begin code
 Key: second     Value: b

lib/Language/mop.pod

@@ -26,7 +26,7 @@ corresponds to:
 
     A.x();
 
-(except that the declarative form runs at comple time, and the latter form
+(except that the declarative form runs at compile time, and the latter form
 does not).
 
 The meta object behind an object can be obtained with C<$obj.HOW>, where HOW

lib/Language/variables.pod

@@ -453,7 +453,7 @@ grammars, provided you activated the C<MONKEY-TYPING> pragma first.
 
 Since classes are usually C<our> scoped, and thus global, this means modifying
 global state, which is strongly discouraged. For almost all situations, there
-are better soluations.
+are better solutions.
 
     # don't do this
     use MONKEY-TYPING;