diff options
| author | Tshepang Lekhonkhobe <tshepang@gmail.com> | 2013-01-11 19:02:30 +0200 |
|---|---|---|
| committer | Tshepang Lekhonkhobe <tshepang@gmail.com> | 2013-01-11 19:02:30 +0200 |
| commit | 2e54b81ff69fc39d42783fffe98a4bb81d28ac97 (patch) | |
| tree | 3cbcc6726f66038ef0fe7075cf5f216b57fd40e4 | |
| parent | 09f43d3ba25ba2189a1b9abf6978e14690034d16 (diff) | |
| download | pyramid-2e54b81ff69fc39d42783fffe98a4bb81d28ac97.tar.gz pyramid-2e54b81ff69fc39d42783fffe98a4bb81d28ac97.tar.bz2 pyramid-2e54b81ff69fc39d42783fffe98a4bb81d28ac97.zip | |
add missing commas
| -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 96e1001e6..6ff686a95 100644 --- a/docs/designdefense.rst +++ b/docs/designdefense.rst @@ -38,7 +38,7 @@ forking is also a Zope derivative. Implementations of these features were *required* to allow the :app:`Pyramid` authors to build the bread-and-butter CMS-type systems for customers in the -way they were accustomed to building them. No other system save Zope itself +way they were accustomed to building them. No other system, save for Zope itself, had such features. And Zope itself was beginning to show signs of its age. We were becoming hampered by consequences of its early design mistakes. Zope's lack of documentation was also difficult to work around: it was hard @@ -55,7 +55,7 @@ existing frameworks had good, and sometimes very compelling ideas. In particular, :term:`URL dispatch` is a more direct mechanism to map URLs to code. -So although we couldn't find a framework save for Zope that fit our needs, +So, although we couldn't find a framework, save for Zope, that fit our needs, and while we incorporated a lot of Zope ideas into BFG, we also emulated the features we found compelling in other frameworks (such as :term:`url dispatch`). After the initial public release of BFG, as time went on, |