summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorPaul Everitt <paul@agendaless.com>2009-07-20 13:17:50 +0000
committerPaul Everitt <paul@agendaless.com>2009-07-20 13:17:50 +0000
commit7f05986f5040fc8581f0653ec3073052acae3e38 (patch)
treebaf7ebb46c4c2634b7caa614aa05ec4c93d2b98d /docs
parentfdaa89727d8fdba4ad6e9b6c54c5fca82ebc1a6a (diff)
downloadpyramid-7f05986f5040fc8581f0653ec3073052acae3e38.tar.gz
pyramid-7f05986f5040fc8581f0653ec3073052acae3e38.tar.bz2
pyramid-7f05986f5040fc8581f0653ec3073052acae3e38.zip
Small wording change courtesy of Russ Ferriday
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/introduction.rst9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst
index b277d8666..2af6cadc2 100644
--- a/docs/narr/introduction.rst
+++ b/docs/narr/introduction.rst
@@ -109,11 +109,10 @@ which persistence mechanisms you should use to build an application.
Zope applications are typically reliant on :term:`ZODB`;
:mod:`repoze.bfg` allows you to build :term:`ZODB` applications, but
it has no reliance on the ZODB package. Likewise, :term:`Django`
-tends to make the assumption that you're going to want to store your
-application's data in a relational database. :mod:`repoze.bfg` makes
-no such assumption; it allows you to use a relational database but
-doesn't encourage or discourage an application developer about such a
-decision.
+tends to assume that you want to store your application's data in a
+relational database. :mod:`repoze.bfg` makes no such assumption; it
+allows you to use a relational database but doesn't encourage or
+discourage an application developer about such a decision.
Why?
----