summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarlos de la Guardia <cguardia@yahoo.com>2013-09-15 00:08:43 -0500
committerCarlos de la Guardia <cguardia@yahoo.com>2013-09-15 00:08:43 -0500
commit63e18d797b4f10f6d06ec7ad25d3dadc85147ae2 (patch)
tree0b1f82ab1cdeb0efa25db3eaa2b3c9087d4a6fc7
parent2d2b438f2d3c44dc5a7c49a64d71e8653c0eac60 (diff)
downloadpyramid-63e18d797b4f10f6d06ec7ad25d3dadc85147ae2.tar.gz
pyramid-63e18d797b4f10f6d06ec7ad25d3dadc85147ae2.tar.bz2
pyramid-63e18d797b4f10f6d06ec7ad25d3dadc85147ae2.zip
Double 'instead' removed.
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index a8f1c409a..bbce3e29c 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -842,7 +842,7 @@ applications by :app:`Pyramid` are good or bad is mostly pointless. You
needn't take advantage of the extensibility features provided by a particular
:app:`Pyramid` application in order to affect a modification for a particular
set of its deployments. You can ignore the application's extensibility
-plugpoints entirely, and instead use version control branching and merging to
+plugpoints entirely, and use version control branching and merging to
manage application deployment modifications instead, as if you were deploying
an application written using any other web framework.