quick_tour - Configuration with ``.ini`` files section cookiecutter updates

- reorder numbered list to align with configuration order, this time for sure!

1 files changed, 5 insertions, 5 deletions

diff --git a/docs/quick_tour.rst b/docs/quick_tour.rst
index a48ac4137..ab25f68dc 100644
--- a/docs/quick_tour.rst
+++ b/docs/quick_tour.rst
@@ -603,16 +603,16 @@ We have a few decisions made for us in this configuration:
    ``use = egg:hello_world`` in the app section tells the configuration what
    application to load.
 
-#. *Choice of web server:* ``use = egg:waitress#main`` tells ``pserve`` to
-   use the ``waitress`` server.
-
-#. *Interfaces:* ``listen = 127.0.0.1:6543 [::1]:6543`` tells ``waitress`` to listen on all interfaces on port 6543 for both IPv4 and IPv6.
-
 #. *Easier development by automatic template reloading:* In development mode,
    you shouldn't have to restart the server when editing a Jinja2 template.
    ``pyramid.reload_templates = true`` sets this policy, which might be
    different in production.
 
+#. *Choice of web server:* ``use = egg:waitress#main`` tells ``pserve`` to
+   use the ``waitress`` server.
+
+#. *Interfaces:* ``listen = 127.0.0.1:6543 [::1]:6543`` tells ``waitress`` to listen on all interfaces on port 6543 for both IPv4 and IPv6.
+
 Additionally the ``development.ini`` generated by this scaffold wired up
 Python's standard logging. We'll now see in the console, for example, a log on
 every request that comes in, as well as traceback information.