X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FExtendingCatalyst.pod;h=1d5b6ec581f7ee55667e19a3746a7369e85ea071;hp=9f73e8d13044d313c634e7a65e6d85afc31fcc37;hb=080bb6202ae1dc9a786bb32afcb391f542c2f0fc;hpb=f9ce297698249b24617c5a60e7c625f2005be144
diff --git a/lib/Catalyst/Manual/ExtendingCatalyst.pod b/lib/Catalyst/Manual/ExtendingCatalyst.pod
index 9f73e8d..1d5b6ec 100644
--- a/lib/Catalyst/Manual/ExtendingCatalyst.pod
+++ b/lib/Catalyst/Manual/ExtendingCatalyst.pod
@@ -14,7 +14,7 @@ Catalyst's behaviour, and this can be confusing. This document is
written to help you understand the possibilities, current practices
and their consequences.
-Please read the L section before deciding on a design,
+Please read the L section before deciding on a design,
especially if you plan to release your code to CPAN. The Catalyst
developer and user communities, which B, will benefit
most if we all work together and coordinate.
@@ -255,7 +255,7 @@ in the controller object's hash reference, and available from the
accessor.
The C accessor always only contains the original class configuration
-and you B call $self->config to get your component configuration,
+and you B call C<< $self->config >> to get your component configuration,
as the data there is likely to be a subset of the correct config.
For example:
@@ -580,7 +580,7 @@ lifecycle. If your functionality needs to change some C or
C stages, you won't get around a plugin.
Note, if you just want to hook into such a stage, and run code before,
-or after it, then it is recommended that you use Ls method modifiers
+or after it, then it is recommended that you use L's method modifiers
to do this.
Another valid target for a plugin architecture are things that