From: Leon Brocard <acme@astray.com>
Date: Wed, 8 Jul 2009 11:23:11 +0000 (+0100)
Subject: mark up lazy_build as code
X-Git-Tag: 0.88~36^2~4
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e691bebfeb02a6b789af3a7d4441d9f8d44b5f3e;p=gitmo%2FMoose.git

mark up lazy_build as code
---

diff --git a/lib/Moose/Manual/BestPractices.pod b/lib/Moose/Manual/BestPractices.pod
index b1feea7..1db01de 100644
--- a/lib/Moose/Manual/BestPractices.pod
+++ b/lib/Moose/Manual/BestPractices.pod
@@ -92,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