Fixed #31062 -- Doc'd asgi.py in tutorials and project templates.

docs/intro/reusable-apps.txt

@@ -61,6 +61,7 @@ After the previous tutorials, our project should look like this::
             __init__.py
             settings.py
             urls.py
+            asgi.py
             wsgi.py
         polls/
             __init__.py

docs/intro/tutorial01.txt

@@ -86,6 +86,7 @@ Let's look at what :djadmin:`startproject` created::
             __init__.py
             settings.py
             urls.py
+            asgi.py
             wsgi.py
 
 These files are:
@@ -113,6 +114,9 @@ These files are:
   "table of contents" of your Django-powered site. You can read more about
   URLs in :doc:`/topics/http/urls`.
 
+* :file:`mysite/asgi.py`: An entry-point for ASGI-compatible web servers to
+  serve your project. See :doc:`/howto/deployment/asgi/index` for more details.
+
 * :file:`mysite/wsgi.py`: An entry-point for WSGI-compatible web servers to
   serve your project. See :doc:`/howto/deployment/wsgi/index` for more details.
 

docs/ref/applications.txt

@@ -22,9 +22,9 @@ The term **project** describes a Django web application. The project Python
 package is defined primarily by a settings module, but it usually contains
 other things. For example, when you run  ``django-admin startproject mysite``
 you'll get a ``mysite`` project directory that contains a ``mysite`` Python
-package with ``settings.py``, ``urls.py``, and ``wsgi.py``. The project package
-is often extended to include things like fixtures, CSS, and templates which
-aren't tied to a particular application.
+package with ``settings.py``, ``urls.py``, ``asgi.py`` and ``wsgi.py``. The
+project package is often extended to include things like fixtures, CSS, and
+templates which aren't tied to a particular application.
 
 A **project's root directory** (the one that contains ``manage.py``) is usually
 the container for all of a project's applications which aren't installed