- The ``alchemy`` scaffold has been removed.

- The ``routesalchemy`` scaffold has been renamed ``alchemy``.

1 files changed, 3 insertions, 3 deletions

diff --git a/docs/tutorials/wiki2/basiclayout.rst b/docs/tutorials/wiki2/basiclayout.rst
index acd2f04f3..db8ab1fbe 100644
--- a/docs/tutorials/wiki2/basiclayout.rst
+++ b/docs/tutorials/wiki2/basiclayout.rst
@@ -2,7 +2,7 @@
 Basic Layout
 ============
 
-The starter files generated by the ``routesalchemy`` scaffold are
+The starter files generated by the ``alchemy`` scaffold are
 basic, but they provide a good orientation for the high-level patterns common
 to most :term:`url dispatch` -based :app:`Pyramid` projects.
 
@@ -98,7 +98,7 @@ register views for the routes, mapping your patterns to code:
 
 The first positional ``add_view`` argument ``tutorial.views.my_view`` is the
 dotted name to a *function* we write (generated by the
-``routesalchemy`` scaffold) that is given a ``request`` object and
+``alchemy`` scaffold) that is given a ``request`` object and
 which returns a response or a dictionary.  This view also names a
 ``renderer``, which is a template which lives in the ``templates``
 subdirectory of the package.  When the ``tutorial.views.my_view`` view
@@ -124,7 +124,7 @@ Content Models with ``models.py``
 In a SQLAlchemy-based application, a *model* object is an object
 composed by querying the SQL database which backs an application.
 SQLAlchemy is an "object relational mapper" (an ORM).  The
-``models.py`` file is where the ``routesalchemy`` scaffold
+``models.py`` file is where the ``alchemy`` scaffold
 put the classes that implement our models.
 
 Let's take a look. First, we need some imports to support later code.