More cleanup in native documentation

[gitmo/Moose.git] / lib / Moose / Manual / MooseX.pod

diff --git a/lib/Moose/Manual/MooseX.pod b/lib/Moose/Manual/MooseX.pod
index f4bfa72..27e1999 100644 (file)
--- a/lib/Moose/Manual/MooseX.pod
+++ b/lib/Moose/Manual/MooseX.pod
@@ -151,11 +151,10 @@ From the command line, someone can execute the script:
 To be honest, using a singleton is just a way to have a magic global
 variable in languages that don't actually have global variables.
 
-In perl, you should almost certaintly just use a global.
-
-However, if your colleagues are too used to java to understand that a
-singleton is a slow, stupid way of hacking around its lack of globals,
-L<MooseX::Singleton> lets you have a Moose class that's a singleton:
+In perl, you can just as easily use a global. However, if your
+colleagues are Java-infected, they might prefer a singleton. Also, if
+you have an existing class that I<isn't> a singleton but should be,
+using L<MooseX::Singleton> is the easiest way to convert it.
 
   package Config;
 
@@ -234,7 +233,7 @@ attributes.
 
   class_has 'Cache' => ( ... );
 
-Note however that this class attribute does -not- inherit like a
+Note however that this class attribute does I<not> inherit like a
 L<Class::Data::Inheritable> or similar attribute - calling
 
   $subclass->Cache($cache);
@@ -273,6 +272,14 @@ Automatically names all accessors I<Perl Best Practices>-style,
 Automatically names all accessors with an explicit set and implicit
 get, "size" and "set_size".
 
+=head2 L<MooseX::NonMoose>
+
+MooseX::NonMoose allows for easily subclassing non-Moose classes with Moose,
+taking care of the annoying details connected with doing this, such as
+setting up proper inheritance from Moose::Object and installing
+(and inlining, at make_immutable time) a constructor that makes sure things
+like BUILD methods are called.
+
 =head1 AUTHOR
 
 Dave Rolsky E<lt>autarch@urth.orgE<gt>