fix RST line too long

docs/deploying/cgi.rst

@@ -46,9 +46,9 @@ In Apache for example you can put something like this into the config:
     ScriptAlias /app /path/to/the/application.cgi
 
 On shared webhosting, though, you might not have access to your Apache config.
-In this case, a file called ``.htaccess``, sitting in the public directory you want
-your app to be available, works too but the ``ScriptAlias`` directive won't
-work in that case:
+In this case, a file called ``.htaccess``, sitting in the public directory
+you want your app to be available, works too but the ``ScriptAlias`` directive
+won't work in that case:
 
 .. sourcecode:: apache
 

docs/deploying/fastcgi.rst

@@ -4,10 +4,10 @@ FastCGI
 =======
 
 FastCGI is a deployment option on servers like `nginx`_, `lighttpd`_, and
-`cherokee`_; see :doc:`uwsgi` and :doc:`wsgi-standalone` for other options. To
-use your WSGI application with any of them you will need a FastCGI server first.
-The most popular one is `flup`_ which we will use for this guide. Make sure to
-have it installed to follow along.
+`cherokee`_; see :doc:`uwsgi` and :doc:`wsgi-standalone` for other options.
+To use your WSGI application with any of them you will need a FastCGI
+server first. The most popular one is `flup`_ which we will use for
+this guide. Make sure to have it installed to follow along.
 
 .. admonition:: Watch Out
 

docs/deploying/mod_wsgi.rst

@@ -52,10 +52,10 @@ reload you can safely ignore them.  Just restart the server.
 Creating a `.wsgi` file
 -----------------------
 
-To run your application you need a :file:`yourapplication.wsgi` file.  This file
-contains the code `mod_wsgi` is executing on startup to get the application
-object.  The object called `application` in that file is then used as
-application.
+To run your application you need a :file:`yourapplication.wsgi` file.
+This file contains the code `mod_wsgi` is executing on startup
+to get the application object.  The object called `application`
+in that file is then used as application.
 
 For most applications the following file should be sufficient::
 
@@ -108,16 +108,17 @@ refuse to run with the above configuration. On a Windows system, eliminate those
 
 .. sourcecode:: apache
 
-	<VirtualHost *>
-		ServerName example.com
-		WSGIScriptAlias / C:\yourdir\yourapp.wsgi
-		<Directory C:\yourdir>
-			Order deny,allow
-			Allow from all
-		</Directory>
-	</VirtualHost>
+    <VirtualHost *>
+        ServerName example.com
+        WSGIScriptAlias / C:\yourdir\yourapp.wsgi
+        <Directory C:\yourdir>
+            Order deny,allow
+            Allow from all
+        </Directory>
+    </VirtualHost>
 
-Note: There have been some changes in access control configuration for `Apache 2.4`_.
+Note: There have been some changes in access control configuration
+for `Apache 2.4`_.
 
 .. _Apache 2.4: https://httpd.apache.org/docs/trunk/upgrading.html
 

docs/deploying/uwsgi.rst

@@ -31,10 +31,11 @@ Given a flask application in myapp.py, use the following command:
 
     $ uwsgi -s /tmp/yourapplication.sock --manage-script-name --mount /yourapplication=myapp:app
 
-The ``--manage-script-name`` will move the handling of ``SCRIPT_NAME`` to uwsgi,
-since it is smarter about that. It is used together with the ``--mount``
-directive which will make requests to ``/yourapplication`` be directed to
-``myapp:app``. If your application is accessible at root level, you can use a
+The ``--manage-script-name`` will move the handling of ``SCRIPT_NAME``
+to uwsgi, since it is smarter about that.
+It is used together with the ``--mount`` directive which will make
+requests to ``/yourapplication`` be directed to ``myapp:app``.
+If your application is accessible at root level, you can use a
 single ``/`` instead of ``/yourapplication``. ``myapp`` refers to the name of
 the file of your flask application (without extension) or the module which
 provides ``app``. ``app`` is the callable inside of your application (usually