summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2012-02-24 11:46:52 -0800
committerChris McDonough <chrism@plope.com>2012-02-24 11:46:52 -0800
commit33f922bb012481424bdcd0b5d063ebf22f20d273 (patch)
tree708736152f7c25838512de98490bfdd53782b67a /docs/designdefense.rst
parentf2f67edd97b9525ae6c6a20a09a9afa9189c018e (diff)
parent283494c2338dbd6e89a7da79a05318992ee04cfc (diff)
downloadpyramid-33f922bb012481424bdcd0b5d063ebf22f20d273.tar.gz
pyramid-33f922bb012481424bdcd0b5d063ebf22f20d273.tar.bz2
pyramid-33f922bb012481424bdcd0b5d063ebf22f20d273.zip
Merge pull request #445 from slinkp/master
Trivial doc typos
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 84b6be907..bbcf9c2ec 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -1386,7 +1386,7 @@ predictability.
actually the best-case circumstance for double-imports; if a module only
mutates itself and its contents at import time, if it is imported twice,
that's OK, because each decorator invocation will always be mutating an
- independent copy of the object its attached to, not a shared resource like
+ independent copy of the object it's attached to, not a shared resource like
a registry in another module. This has the effect that
double-registrations will never be performed.
@@ -1727,7 +1727,7 @@ reads something like this:
(Paraphrased from a real email, actually.)
-Let's take this criticism point-by point.
+Let's take this criticism point-by-point.
Too Complex
+++++++++++