update ::Delta for the recent changes

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

diff --git a/lib/Moose/Manual/BestPractices.pod b/lib/Moose/Manual/BestPractices.pod
index 1807c1d..3a8e104 100644 (file)
--- a/lib/Moose/Manual/BestPractices.pod
+++ b/lib/Moose/Manual/BestPractices.pod
@@ -32,15 +32,16 @@ Moose sugar and making your class immutable.
 
   1;
 
-The C<no Moose> bit simply good code hygiene, as it removes all the
-Moose keywords that are no longer needed once your class has been
-built.  C<make_immutable> relinquishes your right to make further
-changes to your class, and allows Moose to speed up a lot of things,
-most notably object construction.
+The C<no Moose> bit is simply good code hygiene, as it removes all the
+Moose keywords from your class's namespace. Once the class has been
+built, these keywords are not needed needed. The C<make_immutable>
+call allows Moose to speed up a lot of things, most notably object
+construction. The trade-off is that you can no longer change the class
+definition.
 
-A more generic way to unimport not only L<Moose>'s exports but also those from
-type libraries and other modules is L<namespace::clean> and
-L<namespace::autoclean>.
+A more generic way to unimport not only L<Moose>'s exports but also
+those from type libraries and other modules is to use
+L<namespace::clean> or L<namespace::autoclean>.
 
 =head2 Never override C<new>
 
@@ -91,7 +92,7 @@ Also, keep your builder methods private.
 
 Lazy is good, and often solves initialization ordering problems. It's
 also good for deferring work that may never have to be done. If you're
-going to be lazy, use I<lazy_build> to save yourself some typing and
+going to be lazy, use C<lazy_build> to save yourself some typing and
 standardize names.
 
 =head2 Consider keeping clearers and predicates private