diff options
| author | Paul Winkler <slinkp@gmail.com> | 2012-02-24 14:24:50 -0500 |
|---|---|---|
| committer | Paul Winkler <slinkp@gmail.com> | 2012-02-24 14:24:50 -0500 |
| commit | 283494c2338dbd6e89a7da79a05318992ee04cfc (patch) | |
| tree | 708736152f7c25838512de98490bfdd53782b67a /docs/designdefense.rst | |
| parent | 3213d8e0a9f925ab2a6211b1134b087fc5adbad8 (diff) | |
| download | pyramid-283494c2338dbd6e89a7da79a05318992ee04cfc.tar.gz pyramid-283494c2338dbd6e89a7da79a05318992ee04cfc.tar.bz2 pyramid-283494c2338dbd6e89a7da79a05318992ee04cfc.zip | |
More trivial typos
Diffstat (limited to 'docs/designdefense.rst')
| -rw-r--r-- | docs/designdefense.rst | 4 |
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 +++++++++++ |