[Catalyst-commits] r12394 - trunk/examples/CatalystAdvent/root/2009/pen

[hobbs at dev.catalyst.perl.org]

Author: hobbs
Date: 2009-12-16 00:13:22 +0000 (Wed, 16 Dec 2009)
New Revision: 12394

Modified:
   trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod
Log:
Spelling and grammar nits


Modified: trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod	2009-12-15 23:54:48 UTC (rev 12393)
+++ trunk/examples/CatalystAdvent/root/2009/pen/media_delivery.pod	2009-12-16 00:13:22 UTC (rev 12394)
@@ -32,11 +32,11 @@
 to go any further...
 
 However, if you're serving large files and likely to have an appreciable number of users,
-then sending bytes in perl just won't scale..
+then sending bytes in perl just won't scale.
 
-=head2 Scaleing
+=head2 Scaling
 
-The key to scaleing is to do things using the minimum resources possible. Sending bytes across
+The key to scaling is to do things using the minimum resources possible. Sending bytes across
 the internet is something that web servers are very good at scaling to do.
 
 So the planned architecture will be something like:
@@ -45,7 +45,7 @@
 
 =item *
 
-Request comes into your web server
+Request comes into your web server.
 
 =item *
 
@@ -63,12 +63,12 @@
 
 =back
 
-So the key is this <X-Accel-Redirect> or C<X-Sendfile> thing - these are just
-a header that you get your application to send in the response (which one you
+So the key is this C<X-Accel-Redirect> or C<X-Sendfile> thing - these are just
+headers that you get your application to send in the response (which one you
 use depends which web server you're running).
 
-After sending this (headers only) response, your application server is freed
-up and able to get on with handling the next request.
+After sending this response (headers only, no content), your application server
+is freed up and able to get on with handling the next request.
 
 =head3 A note on web servers
 
@@ -96,18 +96,18 @@
 it internally redirects the request to another path known by the web server,
 bypassing ACL checking.
 
-This means that the correct header to send is web server configuration
-dependent, which is a disadvantage, but as nginx can act as a proxy as well as
-a web server, this can also be more powerful, as nginx can proxy for a backend
-content server.
+This means that the correct header to send depends on your web server
+configuration, which is a disadvantage, but as nginx can act as a proxy as well
+as a web server, this can also be more powerful, as nginx can proxy for a
+backend content server.
 
 =head4 perlbal
 
 Perl based load balancer which supports an C<X-REPROXY-URL> header to allow
 you to reproxy content to a backend content server.
 
-Not covered in this article as I don't have any experience with it myself, and
-you still need a web server to serve your main application.
+C<X-REPROXY-URL> is not covered in this article as I don't have any experience
+with it myself, and you still need a web server to serve your main application.
 
 =head2 Examples
 
@@ -117,7 +117,7 @@
 =head3 nginx config
 
     http {
-        include       /etc/nginx/mime.types;
+        include     /etc/nginx/mime.types;
         access_log  /var/log/nginx/access.log;
 
         sendfile           on;