Remove extra word and add relevant links

doc/Language/mop.pod6

@@ -136,7 +136,7 @@ C<module>, C<package>, C<grammar> or C<subset>, there is a separate metaclass in
 C<Perl6::Metamodel::> namespace, and then maps C<Perl6::Metamodel> to
 C<Metamodel>).
 
-Many of the these metaclasses share common functionality. For example
+Many of these metaclasses share common functionality. For example
 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 metaclasses. For example
@@ -157,7 +157,8 @@ responsible for role handling can be roles. The answer is I<by magic>.
 
 Just kidding. Bootstrapping is implementation specific. Rakudo does it by
 using the object system of the language in which itself is implemented,
-which happens to be (nearly) a subset of Perl 6: NQP, Not Quite Perl. NQP
+which happens to be (nearly) a subset of Perl 6 known as
+L<NQP|/language/faq#What_language_is_NQP_written_in?>. NQP
 has a primitive, class-like kind called C<knowhow>, which is used to
 bootstrap its own classes and roles implementation. C<knowhow> is built on
 primitives that the virtual machine under NQP provides.
@@ -218,8 +219,8 @@ composing the Scalar that the C<$>-sigiled variable implies, not C<MyType>.
 
 The consequence is that you need to have a rather detailed understanding of
 the subtleties of Perl 6 in order to avoid pitfalls when working with the MOP,
-and can't expect the same "do what I mean" convenience that ordinary Perl 6
-code offers.
+and can't expect the same L<"do what I mean"|/language/glossary#DWIM>
+convenience that ordinary Perl 6 code offers.
 
 =end pod