summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorMin ho Kim <minho42@gmail.com>2019-07-27 01:11:04 +1000
committerMin ho Kim <minho42@gmail.com>2019-07-27 01:11:04 +1000
commita85a83b631ac6ff8653a9c35cd089c7889753ea3 (patch)
tree0321399b4b04efdc1f6031af25d8c056fd4724d9 /docs/designdefense.rst
parentd32e4775e6da03720a9d3b239efeec956101e954 (diff)
downloadpyramid-a85a83b631ac6ff8653a9c35cd089c7889753ea3.tar.gz
pyramid-a85a83b631ac6ff8653a9c35cd089c7889753ea3.tar.bz2
pyramid-a85a83b631ac6ff8653a9c35cd089c7889753ea3.zip
Fix typos
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 566ad1f5e..e02949ce5 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -988,7 +988,7 @@ the following:
traverses by registering one or more adapters. As a result of being able
to either replace the larger component entirely or turn knobs on the
default implementation of the larger component, no one understands when (or
- whether) they should ever override the larger component entrirely. This
+ whether) they should ever override the larger component entirely. This
results, over time, in a rusting together of the larger "replaceable"
component and the framework itself because people come to depend on the
availability of the default component in order just to turn its knobs. The