Rephrasing slightly

Author: JJ

doc/Language/objects.pod6

@@ -9,7 +9,7 @@ Although Perl 6 allows programmers to program in multiple paradigms,
 Object Oriented Programming is at the heart of the language.
 
 Perl 6 comes with a wealth of predefined types, which can be classified
-in two categories: normal and L<I<native> types|/language/nativetypes>.
+in two categories: regular and L<I<native> types|/language/nativetypes>.
 Everything that you can store in a variable is either a I<native value>
 or an I<object>. That includes literals, types (type objects), code and
 containers.
@@ -19,7 +19,8 @@ types do not have the same capabilities as objects, if you call methods on them,
 they are automatically I<boxed> into normal objects.
 
 Everything that is not a I<native> value is an I<object>.
-Objects do allow for both L<inheritance|https://en.wikipedia.org/wiki/Object-oriented_programming#Inheritance_and_behavioral_subtyping> and
+Objects do allow for both
+L<inheritance|https://en.wikipedia.org/wiki/Object-oriented_programming#Inheritance_and_behavioral_subtyping> and
 L<encapsulation|https://en.wikipedia.org/wiki/Object-oriented_programming#Encapsulation>.
 
 
@@ -687,14 +688,14 @@ attributes can be supplied as named arguments.
 See document for L<clone|/routine/clone> for details on how non-scalar attributes get cloned,
 as well as examples of implementing your own custom clone methods.
 
-=head1 X<Roles|declarator,role>
+=head1 The X<role> declarator
 X<|does>
 
-Roles are in some ways similar to classes, in that they are a collection of
-attributes and methods. They differ in that roles are also meant for
-describing only parts of an object's behavior and in how roles are applied
-to classes. Or to phrase it differently, classes are meant for managing
-objects and roles are meant for managing behavior and code reuse.
+Roles are a collection of attributes and methods; however, unlike classes, roles
+are meant for describing only parts of an object's behavior; this why, in
+general, roles are intended to be I<mixed in> classes and objects. In general,
+classes are meant for managing objects and roles are meant for managing behavior
+and code reuse within objects.
 
     =begin code
     use MONKEY-SEE-NO-EVAL;