diff options
| author | Carlos de la Guardia <cguardia@yahoo.com> | 2013-09-15 00:03:23 -0500 |
|---|---|---|
| committer | Carlos de la Guardia <cguardia@yahoo.com> | 2013-09-15 00:03:23 -0500 |
| commit | 4fa49f72be3b61182c76eca353e6f37fdb625227 (patch) | |
| tree | da4bcd579ac85a82c508c0b0c91d742101e70aea | |
| parent | 9d0f887fa913482a2e07df442ed0b02ae7778a89 (diff) | |
| download | pyramid-4fa49f72be3b61182c76eca353e6f37fdb625227.tar.gz pyramid-4fa49f72be3b61182c76eca353e6f37fdb625227.tar.bz2 pyramid-4fa49f72be3b61182c76eca353e6f37fdb625227.zip | |
typo
| -rw-r--r-- | docs/designdefense.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst index e30b847de..02f868e5d 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -810,7 +810,7 @@ won't regularly need to deal wth meaningless textual merge conflicts that trivial changes to upstream packages often entail when it comes time to update the upstream package, because if you extend an application externally, there just is no textual merge done. Your modifications will also, for -whatever its worth, be contained in one, canonical, well-defined place. +whatever it's worth, be contained in one, canonical, well-defined place. Branching an application and continually merging in order to get new features and bugfixes is clearly useful. You can do that with a :app:`Pyramid` |