Refs #36485 -- Rewrapped docs to 79 columns line length.

Lines in the docs files were manually adjusted to conform to the
79 columns limit per line (plus newline), improving readability and
consistency across the content.

4 files changed, 12 insertions, 11 deletions

diff --git a/docs/howto/deployment/asgi/uvicorn.txt b/docs/howto/deployment/asgi/uvicorn.txt
index cd7cacd72f..b02d6c20ee 100644
--- a/docs/howto/deployment/asgi/uvicorn.txt
+++ b/docs/howto/deployment/asgi/uvicorn.txt
@@ -40,8 +40,9 @@ For more advanced usage, please read the `Uvicorn documentation <Uvicorn_>`_.
 Deploying Django using Uvicorn and Gunicorn
 ===========================================
 
-Gunicorn_ is a robust web server that implements process monitoring and automatic
-restarts. This can be useful when running Uvicorn in a production environment.
+Gunicorn_ is a robust web server that implements process monitoring and
+automatic restarts. This can be useful when running Uvicorn in a production
+environment.
 
 To install Uvicorn and Gunicorn, use the following:
 
diff --git a/docs/howto/deployment/wsgi/apache-auth.txt b/docs/howto/deployment/wsgi/apache-auth.txt
index 0629b785c5..454abf232c 100644
--- a/docs/howto/deployment/wsgi/apache-auth.txt
+++ b/docs/howto/deployment/wsgi/apache-auth.txt
@@ -2,10 +2,10 @@
 How to authenticate against Django's user database from Apache
 ==============================================================
 
-Since keeping multiple authentication databases in sync is a common problem when
-dealing with Apache, you can configure Apache to authenticate against Django's
-:doc:`authentication system </topics/auth/index>` directly. This requires Apache
-version >= 2.2 and mod_wsgi >= 2.0. For example, you could:
+Since keeping multiple authentication databases in sync is a common problem
+when dealing with Apache, you can configure Apache to authenticate against
+Django's :doc:`authentication system </topics/auth/index>` directly. This
+requires Apache version >= 2.2 and mod_wsgi >= 2.0. For example, you could:
 
 * Serve static/media files directly from Apache only to authenticated users.
 
diff --git a/docs/howto/deployment/wsgi/index.txt b/docs/howto/deployment/wsgi/index.txt
index 502a253866..0d3b0cd220 100644
--- a/docs/howto/deployment/wsgi/index.txt
+++ b/docs/howto/deployment/wsgi/index.txt
@@ -37,9 +37,9 @@ deployments.
 
 WSGI servers obtain the path to the ``application`` callable from their
 configuration. Django's built-in server, namely the :djadmin:`runserver`
-command, reads it from the :setting:`WSGI_APPLICATION` setting. By default, it's
-set to ``<project_name>.wsgi.application``, which points to the ``application``
-callable in :file:`<project_name>/wsgi.py`.
+command, reads it from the :setting:`WSGI_APPLICATION` setting. By default,
+it's set to ``<project_name>.wsgi.application``, which points to the
+``application`` callable in :file:`<project_name>/wsgi.py`.
 
 Configuring the settings module
 ===============================
diff --git a/docs/howto/deployment/wsgi/modwsgi.txt b/docs/howto/deployment/wsgi/modwsgi.txt
index c81b3df48a..a5699002ec 100644
--- a/docs/howto/deployment/wsgi/modwsgi.txt
+++ b/docs/howto/deployment/wsgi/modwsgi.txt
@@ -124,8 +124,8 @@ use ``WSGIPythonPath``; instead you should use the ``python-path`` option to
     WSGIProcessGroup example.com
 
 If you want to serve your project in a subdirectory
-(``https://example.com/mysite`` in this example), you can add ``WSGIScriptAlias``
-to the configuration above:
+(``https://example.com/mysite`` in this example), you can add
+``WSGIScriptAlias`` to the configuration above:
 
 .. code-block:: apache