fragments are executed with @|me| bound to an instance pointer of the
appropriate superclass type, immediately after that superclass's slots (if
any) have been initialized; therefore, fragments defined by a more specific
-superclass are executed after fragments defined by a more specific
+superclass are executed after fragments defined by a less specific
superclass. A class may define more than one initialization fragment: the
fragments are executed in the order in which they appear in the class
definition. It is possible for an initialization fragment to use @|return|
executed to shut down an instance. Each superclass's teardown fragments are
executed with @|me| bound to an instance pointer of the appropriate
superclass type; fragments defined by a more specific superclass are executed
-before fragments defined by a more specific superclass. A class may define
+before fragments defined by a less specific superclass. A class may define
more than one teardown fragment: the fragments are executed in the order in
which they appear in the class definition. It is possible for an
initialization fragment to use @|return| or @|goto| for special control-flow