From f868a98cdc4bec0ce10d18b66af1687f3e3a1bbb Mon Sep 17 00:00:00 2001 From: Steve Piercy Date: Sun, 7 Oct 2018 02:40:23 -0700 Subject: Use proper case for Setuptools as a library name. Change Setuptools to a glossary term where useful. --- docs/narr/scaffolding.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/narr/scaffolding.rst') diff --git a/docs/narr/scaffolding.rst b/docs/narr/scaffolding.rst index 083d831cc..47eb2c658 100644 --- a/docs/narr/scaffolding.rst +++ b/docs/narr/scaffolding.rst @@ -21,11 +21,11 @@ Basics A scaffold template is just a bunch of source files and directories on disk. A small definition class points at this directory. It is in turn pointed at by a -:term:`setuptools` "entry point" which registers the scaffold so it can be +:term:`Setuptools` "entry point" which registers the scaffold so it can be found by the ``pcreate`` command. To create a scaffold template, create a Python :term:`distribution` to house -the scaffold which includes a ``setup.py`` that relies on the ``setuptools`` +the scaffold which includes a ``setup.py`` that relies on the :term:`Setuptools` package. See `Packaging and Distributing Projects `_ for more information about how to do this. For example, we'll pretend the distribution you create -- cgit v1.2.3