more spelling fixes

diff --git a/lib/Catalyst/ActionRole/Scheme.pm b/lib/Catalyst/ActionRole/Scheme.pm
index fecd2c0..240538d 100644 (file)
--- a/lib/Catalyst/ActionRole/Scheme.pm
+++ b/lib/Catalyst/ActionRole/Scheme.pm
@@ -82,7 +82,7 @@ Around method modifier that return 1 if the scheme matches
 
 =head2 list_extra_info
 
-Add the scheme info  contenif present to the debug screen.
+Add the scheme declaration if present to the debug screen.
 
 =head1 AUTHORS
 

diff --git a/lib/Catalyst/UTF8.pod b/lib/Catalyst/UTF8.pod
index 9f2ceed..b32bc31 100644 (file)
--- a/lib/Catalyst/UTF8.pod
+++ b/lib/Catalyst/UTF8.pod
@@ -32,7 +32,7 @@ as well as how you construct L<URL> objects to actions with UTF8 paths
 
     package MyApp::Controller::Root;
 
-    use uf8;
+    use utf8;
     use base 'Catalyst::Controller';
 
     sub heart_with_arg :Path('♥') Args(1)  {
@@ -60,7 +60,7 @@ In the example controller above we have constructed two matchable URL routes:
 
 The first one is a classic Path type action and the second uses Chaining, and
 spans three actions in total.  As you can see, you can use unicode characters
-in your Path and PartPart attributes (remember to use the C<utf8> pragma to allow
+in your Path and PathPart attributes (remember to use the C<utf8> pragma to allow
 these multibyte characters in your source).  The two constructed matchable routes
 would match the following incoming URLs:
 
@@ -133,7 +133,7 @@ pragma).
     use utf8;
     my $url = $c->uri_for( $c->controller('Root')->action_for('arg'), ['♥','♥']);
 
-When you stringyfy this object (for use in a template, for example) it will automatically
+When you stringify this object (for use in a template, for example) it will automatically
 do the right thing regarding utf8 encoding and url encoding.
 
     http://localhost/base/%E2%99%A5/%E2%99%A5/%E2%99%A5/%E2%99%A5
@@ -148,9 +148,8 @@ What Catalyst does with UTF8 in your GET and classic HTML Form POST
 
 =head2 UTF8 in URL query and keywords
 
-The same rules that we find in URL paths also cover URL query parts.  That is if
-one types a URL like this into the browser (again assuming a modernish UI that
-allows unicode)
+The same rules that we find in URL paths also cover URL query parts.  That is
+if one types a URL like this into the browser
 
        http://localhost/example?♥=♥♥
 
@@ -186,7 +185,7 @@ strings) in $c->uri_for:
        use utf8;
        my $url = $c->uri_for( $c->controller('Root')->action_for('example'), {'♥' => '♥♥'});
 
-When you stringyfy this object (for use in a template, for example) it will automatically
+When you stringify this object (for use in a template, for example) it will automatically
 do the right thing regarding utf8 encoding and url encoding.
 
        http://localhost/example?%E2%99%A5=%E2%99%A5%E2%99%A5
@@ -355,7 +354,7 @@ B<NOTE> pay attention to the content-type setting in the example.  L<Catalyst> i
 content type carefully to determine if the body needs encoding).
 
 B<NOTE> If you set the character set of the response L<Catalyst> will skip encoding IF the
-character set is set to somethng that doesn't match $c->encoding->mime_name. We will assume
+character set is set to something that doesn't match $c->encoding->mime_name. We will assume
 if you are setting an alternative character set, that means you want to handle the encoding
 yourself.  However it might be easier to set $c->encoding for a given response cycle since
 you can override this for a given response.  For example here's how to override the default
@@ -402,7 +401,7 @@ L<Catalyst> will encode each line in turn as long as the content-type meets the
 requirement and $c->encoding is set (which it is, as long as you did not change it).
 
 B<NOTE> If you try to change the encoding after you start the stream, this will invoke an error
-reponse.  However since you've already started streaming this will not show up as an HTTP error
+response.  However since you've already started streaming this will not show up as an HTTP error
 status code, but rather error information in your body response and an error in your logs.
 
 The second way to stream a response is to get the response writer object and invoke methods
@@ -417,7 +416,7 @@ on that directly:
                $writer->close;
        }
 
-This can be used just like the C<write> method, but typicallty you request this object when
+This can be used just like the C<write> method, but typically you request this object when
 you want to do a nonblocking style response since the writer object can be closed over or
 sent to a model that will invoke it in a non blocking manner.  For more on using the writer
 object for non blocking responses you should review the C<Catalyst> documentation and also
@@ -455,7 +454,7 @@ check the current docs and changelog.  Its possible a future release will requir
 a encoding on the IO layer level so that we can be sure to properly encode at body finalization.
 So this is still an edge case we are writing test examples for.  But for now if you are returning
 a filehandle like response, you are expected to make sure you are following the L<PSGI> specification
-and that unencoded bytes are returned.
+and return raw bytes.
 
 =head2 Override the Encoding on Context
 

diff --git a/t/author/spelling.t b/t/author/spelling.t
index 503cf5a..9ebfaf5 100644 (file)
--- a/t/author/spelling.t
+++ b/t/author/spelling.t
@@ -13,16 +13,16 @@ add_stopwords(qw(
     ctx _application MyApp restarter httponly Utils stash's unescapes
     actionchain dispatchtype dispatchtypes redispatch redispatching
     CaptureArgs ChainedParent PathPart PathPrefix
-    BUILDARGS metaclass namespaces pre ARGV ReverseProxy
+    BUILDARGS metaclass namespaces pre ARGV ReverseProxy TT UI
     filename tempname request's subdirectory ini uninstalled uppercased
     wiki bitmask uri url urls dir hostname proxied http https IP SSL
     inline INLINE plugins cpanfile resized
     FastCGI Stringifies Rethrows DispatchType Wishlist Refactor ROADMAP HTTPS Unescapes Restarter Nginx Refactored
     ActionClass LocalRegex LocalRegexp MyAction metadata cometd io psgix websocket websockets proxying
-    UTF async codebase dev encodable filenames params MyMiddleware Sendfile
-    JSON xml POSTed RESTful performant subref actionrole
+    UTF unicode async codebase dev encodable filenames params MyMiddleware Sendfile
+    JSON xml POSTs POSTed RESTful performant subref actionrole
     chunked chunking codewise distingush equivilent plack Javascript gzipping
-    ConfigLoader getline whitepaper
+    ConfigLoader getline whitepaper matchable
     Andreas
     Ashton
     Axel