Revert incorrect fixes for parsing of attributes with empty parens

[catagits/Catalyst-Runtime.git] / README.mkdn

diff --git a/README.mkdn b/README.mkdn
index 318faab..ad3aa2d 100644 (file)
--- a/README.mkdn
+++ b/README.mkdn
@@ -14,6 +14,11 @@ Catalyst - The Elegant MVC Web Application Framework
 See the [Catalyst::Manual](https://metacpan.org/pod/Catalyst::Manual) distribution for comprehensive
 documentation and tutorials.
 
+    # Building Catalyst for development
+    cpanm --local-lib=~/perl5 local::lib && eval $(perl -I ~/perl5/lib/perl5/ -Mlocal::lib)
+    cpanm --installdeps --with-develop .
+    perl Makefile.PL
+
     # Install Catalyst::Devel for helpers and other development tools
     # use the helper to create a new application
     catalyst.pl MyApp
@@ -1497,7 +1502,7 @@ This has been done since not all people need this feature and we wish to restric
 
 - `skip_complex_post_part_handling`
 
-    When creating body parameters from a POST, if we run into a multpart POST
+    When creating body parameters from a POST, if we run into a multipart POST
     that does not contain uploads, but instead contains inlined complex data
     (very uncommon) we cannot reliably convert that into field => value pairs.  So
     instead we create an instance of [Catalyst::Request::PartData](https://metacpan.org/pod/Catalyst::Request::PartData).  If this causes
@@ -1517,7 +1522,7 @@ This has been done since not all people need this feature and we wish to restric
     If true, then do not try to character decode any wide characters in your
     request URL query or keywords.  Most readings of the relevant specifications
     suggest these should be UTF-\* encoded, which is the default that [Catalyst](https://metacpan.org/pod/Catalyst)
-    will use, hwoever if you are creating a lot of URLs manually or have external
+    will use, however if you are creating a lot of URLs manually or have external
     evil clients, this might cause you trouble.  If you find the changes introduced
     in Catalyst version 5.90080+ break some of your query code, you may disable 
     the UTF-8 decoding globally using this configuration.
@@ -1528,7 +1533,7 @@ This has been done since not all people need this feature and we wish to restric
 - `default_query_encoding`
 
     By default we decode query and keywords in your request URL using UTF-8, which
-    is our reading of the relevent specifications.  This setting allows one to
+    is our reading of the relevant specifications.  This setting allows one to
     specify a fixed value for how to decode your query.  You might need this if
     you are doing a lot of custom encoding of your URLs and not using UTF-8.
 
@@ -1553,15 +1558,15 @@ This has been done since not all people need this feature and we wish to restric
 - `data_handlers` - See ["DATA HANDLERS"](#data-handlers).
 - `stats_class_traits`
 
-    An arrayref of [Moose::Role](https://metacpan.org/pod/Moose::Role)s that get componsed into your stats class.
+    An arrayref of [Moose::Role](https://metacpan.org/pod/Moose::Role)s that get composed into your stats class.
 
 - `request_class_traits`
 
-    An arrayref of [Moose::Role](https://metacpan.org/pod/Moose::Role)s that get componsed into your request class.
+    An arrayref of [Moose::Role](https://metacpan.org/pod/Moose::Role)s that get composed into your request class.
 
 - `response_class_traits`
 
-    An arrayref of [Moose::Role](https://metacpan.org/pod/Moose::Role)s that get componsed into your response class.
+    An arrayref of [Moose::Role](https://metacpan.org/pod/Moose::Role)s that get composed into your response class.
 
 - `inject_components`