Permalink
Browse files

apply grammer fixes from hanekomu

  • Loading branch information...
miyagawa committed Sep 7, 2009
1 parent 13f2832 commit 65afea5dfa45405d85b5273939879e29ee791ffc
Showing with 24 additions and 23 deletions.
  1. +24 −23 PSGI.pod
View
@@ -11,11 +11,12 @@ framework developers.
Keep in mind that PSGI is not Yet Another web application
framework. PSGI is a specification to decouple web server environments
-from web application framework code. PSGI is not also the web
+from web application framework code. PSGI is also not the web
application API. Web application developers (end users) are not
-supposed to run their web applications directly using PSGI interface,
-but instead are encouraged to use frameworks that supports PSGI, or
-use the helper implementations like Plack (more on that later).
+supposed to run their web applications directly using the PSGI
+interface, but instead are encouraged to use frameworks that
+support PSGI, or use the helper implementations like Plack (more on
+that later).
=head1 SPECIFICATION
@@ -53,16 +54,16 @@ required.
C<SCRIPT_NAME>: The initial portion of the request URL's I<path> that
corresponds to the application, so that the application knows its
-virtual "location". This may be an empty string, if the application
+virtual "location". This may be an empty string if the application
corresponds to the "root" of the server.
=item *
C<PATH_INFO>: The remainder of the request URL's "path", designating
the virtual "location" of the request's target within the
-application. This may be an empty string, if the request URL targets
+application. This may be an empty string if the request URL targets
the application root and does not have a trailing slash. This value
-may be percent-encoded when I originating from a URL.
+may be percent-encoded when it originates from a URL.
=item *
@@ -90,7 +91,7 @@ treat any HTTP request headers.
C<HTTP_> Variables: Variables corresponding to the client-supplied
HTTP request headers (i.e., variables whose names begin with
C<HTTP_>). The presence or absence of these variables should
-correspond with the presence or absence of the appropriate HTTP header
+correspond to the presence or absence of the appropriate HTTP header
in the request.
=back
@@ -110,7 +111,7 @@ C<psgi.url_scheme>: A string C<http> or C<https>, depending on the request URL.
=item *
-C<psgi.input>: the input stream. See blow.
+C<psgi.input>: the input stream. See below.
=item *
@@ -136,7 +137,7 @@ asynchronous event loop. See L<PSGI Async extension|PSGI::Async>.
=back
-The server or the application can store their own data in the
+The server or the application can store its own data in the
environment, too. The keys MUST contain at least one dot, and should
be prefixed uniquely. The prefix C<psgi.> is reserved for use with the
PSGI core implementation and other accepted extensions and MUST NOT be
@@ -154,7 +155,7 @@ C<psgi.version> MUST be an array of integers.
=item *
-C<psgi.url_scheme> MUST either be a scalar variable containing a
+C<psgi.url_scheme> MUST be a scalar variable containing either the
string C<http> or C<https>.
=item *
@@ -184,8 +185,8 @@ The C<CONTENT_LENGTH>, if given, MUST consist of digits only.
=item *
One of C<SCRIPT_NAME> or C<PATH_INFO> MUST be set. C<PATH_INFO> should
-be / if C<SCRIPT_NAME> is empty. C<SCRIPT_NAME> never should be /, but
-instead be empty.
+be C</> if C<SCRIPT_NAME> is empty. C<SCRIPT_NAME> should never be C</>,
+but should instead be empty.
=back
@@ -202,9 +203,9 @@ class of the stream, but instead just call C<read> to duck type.
Application developers SHOULD NOT use the built-in C<read> function to
read from the input stream, because C<read> function only works with
-the real IO object (glob ref based file handle or PerlIO) and makes
-the duck typing difficult. Web application framework developers, if
-they know the input stream will be called built-in read() in the
+the real IO object (a glob ref based file handle or PerlIO) and makes
+duck typing difficult. Web application framework developers, if
+they know the input stream will be used with the built-in read() in any
upstream code they can't touch, SHOULD use PerlIO or tie handle to
work around with this problem.
@@ -245,12 +246,12 @@ HTTP status code, is an integer and MUST be greater than or equal to 100.
=head4 Headers
-The header must be an array reference containing a pair of key and
-value. Its number of elements MUST be even. The header MUST NOT
-contain a C<Status> key, contain keys with C<:> or newlines in their
-name, contain keys that end in C<-> or C<_> but only contain keys that
+The headers must be an array reference containing key and value pairs.
+Its number of elements MUST be even. The header MUST NOT contain a
+C<Status> key, contain keys with C<:> or newlines in their name,
+contain keys that end in C<-> or C<_> but only contain keys that
consist of letters, digits, C<_> or C<-> and start with a letter. The
-value of the header must be a scalar value that contains strings. The
+value of the header must be a scalar value that contain a string. The
value string MUST NOT contain characters below chr(37).
If the same key name appears multiple times in an array ref, those
@@ -287,8 +288,8 @@ An IO::Handle-like object or a built-in filehandle.
open my $body, "</path/to/file";
my $body = IO::File->new("/path/to/file");
-Implementors SHOULD NOT check if the type or class of body but instead
-just call C<getline> to iterate the body and call C<close> when done.
+Implementors SHOULD NOT check the type or class of the body but instead
+just call C<getline> to iterate over the body and call C<close> when done.
=back

0 comments on commit 65afea5

Please sign in to comment.