use double bracketed formatting codes so < and > don't need to be escaped

[catagits/Catalyst-Manual.git] / lib / Catalyst / Manual / ExtendingCatalyst.pod

diff --git a/lib/Catalyst/Manual/ExtendingCatalyst.pod b/lib/Catalyst/Manual/ExtendingCatalyst.pod
index 9e4a4e4..73af1bd 100644 (file)
--- a/lib/Catalyst/Manual/ExtendingCatalyst.pod
+++ b/lib/Catalyst/Manual/ExtendingCatalyst.pod
@@ -115,7 +115,7 @@ L<Catalyst::Model::Adaptor|Catalyst::Model::Adaptor>.
 =head2 Using Moose roles to apply method modifiers
 
 Rather than having a complex set of base classes which you have to mixin
-via multiple inheritence, if your functionality is well structured, then
+via multiple inheritance, if your functionality is well structured, then
 it's possible to use the composability of L<Moose> roles, and method modifiers
 to hook onto to provide functionality.
 
@@ -238,18 +238,12 @@ array reference. As you can see, you can use attributes to configure
 your actions. You can specify or alter these attributes via
 L</"Component Configuration">, or even react on them as soon as
 Catalyst encounters them by providing your own L<component base
-class|/"Component Base Classes">.
-
-=head2 Creating custom accessors
-
-L<Catalyst::Component> uses L<Class::Accessor::Fast> for accessor
-creation. Please refer to the modules documentation for usage
-information.
+class|/"Component base classes">.
 
 =head2 Component Configuration
 
 At creation time, the class configuration of your component (the one
-available via C<$self-E<gt>config>) will be merged with possible
+available via C<< $self->config >>) will be merged with possible
 configuration settings from the applications configuration (either
 directly or via config file). This is done by Catalyst, and the
 correctly merged configuration is passed to your component's
@@ -318,10 +312,10 @@ method. The execute method of the action will naturally call the
 methods code. You can surround this by overriding the method in a
 subclass:
 
-  package Catalyst::Action::MyFoo; 
+  package Catalyst::Action::MyFoo;
   use Moose;
   use namespace::autoclean;
-  use MRO::Compat; 
+  use MRO::Compat;
   extends 'Catalyst::Action';
 
   sub execute {
@@ -335,12 +329,12 @@ subclass:
   1;
 
 We are using L<MRO::Compat> to ensure that you have the next::method
-call, from L<Class::C3> (in older perls), or natively (if you are using 
-perl 5.10) to re-dispatch to the original C<execute> method in the 
+call, from L<Class::C3> (in older perls), or natively (if you are using
+perl 5.10) to re-dispatch to the original C<execute> method in the
 L<Catalyst::Action> class.
 
 The Catalyst dispatcher handles an incoming request and, depending
-upon the dispatch type, will call the appropriate target or chain. 
+upon the dispatch type, will call the appropriate target or chain.
 From time to time it asks the actions themselves, or through the
 controller, if they would match the current request. That's what the
 C<match> method does.  So by overriding this, you can change on what
@@ -349,7 +343,7 @@ the action will match and add new matching criteria.
 For example, the action class below will make the action only match on
 Mondays:
 
-  package Catalyst::Action::OnlyMondays; 
+  package Catalyst::Action::OnlyMondays;
   use Moose;
   use namespace::autoclean;
   use MRO::Compat;
@@ -472,7 +466,7 @@ with some custom actions by sub-classing it:
   package MyApp::Controller::Foo;
   use Moose;
   use namespace::autoclean;
-  
+
   BEGIN { extends 'MyApp::Base::Controller::ModelBase'; }
 
   __PACKAGE__->config( model_name => 'DB::Foo',
@@ -543,7 +537,7 @@ Here is some example code for a fictional view:
   package Catalyst::View::MyView;
   use Moose;
   use namespace::autoclean;
-  
+
   extends 'Catalyst::View';
 
   sub process {
@@ -643,7 +637,7 @@ A simple example like this is actually better as a L<Moose> role, for example:
       if (!blessed($_[0]) || !$_[0]->isa('Catalyst::Action'));
     return $uri;
   };
-  
+
 Note that Catalyst will load any Moose Roles in the plugin list,
 and apply them to your application class.
 
@@ -666,13 +660,13 @@ Here is a stub C<COMPONENT> method:
   package CatalystX::Component::Foo;
   use Moose;
   use namespace::autoclean;
-  
+
   extends 'Catalyst::Component';
 
   sub COMPONENT {
       my $class = shift;
       # Note: $app is like $c, but since the application isn't fully
-      # initialized, we don't want to call it $c yet.  $config 
+      # initialized, we don't want to call it $c yet.  $config
       # is a hashref of config options possibly set on this component.
       my ($app, $config) = @_;