diff options
| author | Steve Piercy <web@stevepiercy.com> | 2016-07-02 01:55:29 -0700 |
|---|---|---|
| committer | Steve Piercy <web@stevepiercy.com> | 2016-07-02 01:55:29 -0700 |
| commit | fa257dd74588c9cc80cc3a6b4158ff2c627eacd5 (patch) | |
| tree | dc30e24dff01a46fac7bcce84d7524bb8a8028fa | |
| parent | 446065219c5e43a8116f5b06142de0c75c779618 (diff) | |
| download | pyramid-fa257dd74588c9cc80cc3a6b4158ff2c627eacd5.tar.gz pyramid-fa257dd74588c9cc80cc3a6b4158ff2c627eacd5.tar.bz2 pyramid-fa257dd74588c9cc80cc3a6b4158ff2c627eacd5.zip | |
fix overly aggressive refactor
| -rw-r--r-- | docs/narr/project.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/narr/project.rst b/docs/narr/project.rst index 812404b76..71bd176f6 100644 --- a/docs/narr/project.rst +++ b/docs/narr/project.rst @@ -266,7 +266,7 @@ path to the module on which we want to run tests and coverage. Running the Project Application ------------------------------- -.. seealso:: See also the output of :ref:`pserve --help <pserve_scriptc:\>`. +.. seealso:: See also the output of :ref:`pserve --help <pserve_script>`. Once a project is installed for development, you can run the application it represents using the ``pserve`` command against the generated configuration |