Typographical etc. corrections to mop.pod

Author: paultcochrane

lib/Language/mop.pod

@@ -33,8 +33,8 @@ The meta object behind
 an object can be obtained with C<$obj.HOW>, where HOW stands for Higher Order
 Workings (or, I<HOW the *%@$ does this work?>).
 
-Here the calls with C<.^> are calls to the meta object, so C<A.^compose> is a
-shortcut for C<A.HOW.compose(A)>. The invocant is passed along in the
+Here, the calls with C<.^> are calls to the meta object, so C<A.^compose> is a
+shortcut for C<A.HOW.compose(A)>. The invocant is passed in the
 parameter list as well, to make it possible to support prototype-style type
 systems, where there is just one meta object (and not one meta object per
 type, as standard Perl 6 does it).
@@ -84,7 +84,7 @@ stable identity indicator.
 
 =head2 X<HOW|syntax,HOW>
 
-The metaclass object: "Higher Order Workings"
+The metaclass object: "Higher Order Workings".
 
 =head2 X<WHY|syntax,WHY>
 
@@ -93,6 +93,7 @@ The attached Pod value.
 =head2 X<DEFINITE|syntax,DEFINITE>
 
 The object has a valid concrete representation.
+
 Returns C<True> for instances and C<False> for type objects.
 
 =head2 X<VAR|syntax,VAR>
@@ -110,20 +111,21 @@ The presence of a C<Scalar> object indicates that the object is "itemized".
 
 B<Note:> this documentation largely reflects the meta object system as
 implemented by the L<Rakudo Perl 6 compiler|http://rakudo.org/>, since the
-L<design document|http://design.perl6.org/> are very light on details.
+L<design documents|http://design.perl6.org/> are very light on details.
 
-For each type declarator key word, such as C<class>, C<role>, C<enum>,
+For each type declarator keyword, such as C<class>, C<role>, C<enum>,
 C<module>, C<package>, C<grammar> or C<subset>, there is a separate meta
 class in the C<Metamodel::> namespace. (Rakudo implements them in the
 C<Perl6::Metamodel::> namespace, and then maps C<Perl6::Metamodel> to
 C<Metamodel>).
 
 Many of the these meta classes share common functionality. For example roles,
-grammars and classes can all contain methods and attributes, and can do roles.
+grammars and classes can all contain methods and attributes, as well as being
+able to do roles.
 This shared functionality is implemented in roles which are composed into the
 appropriate meta classes. For example
 L<role Metamodel::RoleContainer|/type/Metamodel::RoleContainer> implements the
-functionality that a type can hold roles, and
+functionality that a type can hold roles and
 L<Metamodel::ClassHOW|/type/Metamodel::ClassHOW>, which is the meta class
 behind the C<class> keyword, does this role.