clean up whitespace

diff --git a/lib/Catalyst/Manual/Deployment.pod b/lib/Catalyst/Manual/Deployment.pod
index fd1aed7..ac6eb3b 100644 (file)
--- a/lib/Catalyst/Manual/Deployment.pod
+++ b/lib/Catalyst/Manual/Deployment.pod
@@ -4,27 +4,29 @@ Catalyst::Manual::Deployment - Deploying Catalyst
 
 =head1 DEPLOYMENT OPTIONS
 
-Catalyst applications most often deployed as a FastCGI or mod_perl application, however
-as Catalyst is based on the L<PSGI> specification, any web handler implementing that specification
-can be used to run Catalyst applications.
+Catalyst applications most often deployed as a FastCGI or mod_perl application,
+however as Catalyst is based on the L<PSGI> specification, any web handler
+implementing that specification can be used to run Catalyst applications.
 
-This documentation most thoroughly covers the normal and traditional deployment options, but
-will mention alternate methods of deployment, and we welcome additional documentation from
-people deploying Catalyst in non-standard environments.
+This documentation most thoroughly covers the normal and traditional deployment
+options, but will mention alternate methods of deployment, and we welcome
+additional documentation from people deploying Catalyst in non-standard
+environments.
 
 =head2 Deployment for shared hosting
 
-Almost all shared hosting environments involve deploying Catalyst as a FastCGI on Apache.
+Almost all shared hosting environments involve deploying Catalyst as a FastCGI
+on Apache.
 
-You will usually want to have a set of libraries specific to your application installed on
-your shared host, and there are instructions about
-this in L<Catalyst::Manual::Deployment::SharedHosting>.
+You will usually want to have a set of libraries specific to your application
+installed on your shared host, and there are instructions about this in
+L<Catalyst::Manual::Deployment::SharedHosting>.
 
 =head2 FastCGI
 
-FastCGI is the most common Catalyst deployment option, it is documented generally in
-L<Catalyst::Manual::Deployment::FastCGI>, and there are specific instructions for common
-web servers linked below:
+FastCGI is the most common Catalyst deployment option, it is documented
+generally in L<Catalyst::Manual::Deployment::FastCGI>, and there are specific
+instructions for common web servers linked below:
 
 =head3 Apache
 
@@ -44,35 +46,39 @@ L<Catalyst::Manual::Deployment::IIS::FastCGI>
 
 =head2 mod_perl
 
-Traditionally a common deployment option for dedicated applications, with some advantages and
-disadvantages over FastCGI. This is documented in L<Catalyst::Manual::Deployment::Apache::mod_perl>.
+Traditionally a common deployment option for dedicated applications, with some
+advantages and disadvantages over FastCGI. This is documented in
+L<Catalyst::Manual::Deployment::Apache::mod_perl>.
 
 =head2 Development Server
 
-It is possible to deploy the Catalyst development server behind a reverse proxy. This may work
-well for small scale applications which are in an early development phase, but you want to be
-able to show to people. See: L<Catalyst::Manual::Deployment::DevelopmentServer>.
+It is possible to deploy the Catalyst development server behind a reverse
+proxy. This may work well for small scale applications which are in an early
+development phase, but you want to be able to show to people. See:
+L<Catalyst::Manual::Deployment::DevelopmentServer>.
 
 =head2 PSGI
 
-Catalyst can be deployed with any PSGI compliant handler. See L<Catalyst::PSGI> for more information,
-and a list of possible deployment servers are shown below:
+Catalyst can be deployed with any PSGI compliant handler. See L<Catalyst::PSGI>
+for more information, and a list of possible deployment servers are shown
+below:
 
 =head3 Starman
 
-L<Starman> is a high performance perl server implementation, which is designed to be used
-directly (rather than behind a reverse proxy). It includes HTTP/1.1 support,
-chunked requests and responses, keep-alive xxand pipeline requests.
+L<Starman> is a high performance perl server implementation, which is designed
+to be used directly (rather than behind a reverse proxy). It includes HTTP/1.1
+support, chunked requests and responses, keep-alive xxand pipeline requests.
 
 =head3 Starlet.
 
-Starlet is a standalone HTTP/1.0 server with keep‐alive support which is suitable for running
-HTTP application servers behind a reverse proxy.
+Starlet is a standalone HTTP/1.0 server with keep‐alive support which is
+suitable for running HTTP application servers behind a reverse proxy.
 
 =head3 Twiggy
 
-L<Twiggy> is a high-performance asynchronous web server. It can be used in conjunction with Catalyst,
-but with a number of caveats which mean that it is not suitable for most deployments.
+L<Twiggy> is a high-performance asynchronous web server. It can be used in
+conjunction with Catalyst, but with a number of caveats which mean that it is
+not suitable for most deployments.
 
 =head1 AUTHORS
 

diff --git a/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod b/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
index bb537f2..4822fe8 100644 (file)
--- a/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
+++ b/lib/Catalyst/Manual/Deployment/DevelopmentServer.pod
@@ -46,8 +46,8 @@ different apps served on the same host.
 
 =head2 Other web servers
 
-The proxy configuration above can also be replicated with a different front end server
-or proxy such as varnish, nginx or lighttpd.
+The proxy configuration above can also be replicated with a different front end
+server or proxy such as varnish, nginx or lighttpd.
 
 =head1 AUTHORS
 
@@ -58,4 +58,4 @@ Catalyst Contributors, see Catalyst.pm
 This library is free software. You can redistribute it and/or modify it under
 the same terms as Perl itself.
 
-=cut
\ No newline at end of file
+=cut

diff --git a/lib/Catalyst/Manual/Deployment/FastCGI.pod b/lib/Catalyst/Manual/Deployment/FastCGI.pod
index e568198..3d749e6 100644 (file)
--- a/lib/Catalyst/Manual/Deployment/FastCGI.pod
+++ b/lib/Catalyst/Manual/Deployment/FastCGI.pod
@@ -4,9 +4,9 @@ Catalyst::Manual::Deployment::FastCGI - Deploying Catalyst with FastCGI
 
 =head1 FastCGI Deployment
 
-FastCGI is a high-performance extension to CGI. It is suitable
-for production environments, and is the standard method for deploying Catalyst
-in shared hosting environments.
+FastCGI is a high-performance extension to CGI. It is suitable for production
+environments, and is the standard method for deploying Catalyst in shared
+hosting environments.
 
 =head2 Pros
 
@@ -81,9 +81,9 @@ server.
 
 =head1 WEB SERVERS
 
-Any web server which supports FastCGI should work with Catalyst. Configuration recipies for
-well-known web servers are linked below, and we would welcome contributions from people
-deploying Catalyst against other web servers.
+Any web server which supports FastCGI should work with Catalyst. Configuration
+recipies for well-known web servers are linked below, and we would welcome
+contributions from people deploying Catalyst against other web servers.
 
 =head2 Apache
 

diff --git a/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod b/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod
index 39f71b7..ecf4c41 100644 (file)
--- a/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod
+++ b/lib/Catalyst/Manual/Deployment/IIS/FastCGI.pod
@@ -88,22 +88,22 @@ system c:\windows\syswow64\inetsrv\fcgiext.ini):
 
 =head2 Setup IIS 7.0 (Windows 2008 and Vista)
 
-Microsoft IIS 7.0 has built-in support for FastCGI so you do not have to install
-any addons.
+Microsoft IIS 7.0 has built-in support for FastCGI so you do not have to
+install any addons.
 
 =over
 
 =item Necessary steps during IIS7 installation
 
-During IIS7 installation after you have added role "Web Server (IIS)"
-you need to check to install role feature "CGI" (do not be nervous that it is
-not FastCGI). If you already have IIS7 installed you can add "CGI" role feature
+During IIS7 installation after you have added role "Web Server (IIS)" you need
+to check to install role feature "CGI" (do not be nervous that it is not
+FastCGI). If you already have IIS7 installed you can add "CGI" role feature
 through "Control panel" > "Programs and Features".
 
 =item Create a new website
 
-Open "Control Panel" > "Administrative Tools" > "Internet Information Services Manager"
-> "Add Web Site".
+Open "Control Panel" > "Administrative Tools" > "Internet Information Services
+Manager" > "Add Web Site".
 
     site name: "CatalystSite"
     content directory: "d:\WWW\WebApp\root"