From 5962195498f53a349b101c9c8ca19daa9c1c9972 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Wed, 7 Sep 2011 14:41:10 -0400 Subject: wording --- docs/narr/introduction.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs') diff --git a/docs/narr/introduction.rst b/docs/narr/introduction.rst index 6e28500d1..b7721f186 100644 --- a/docs/narr/introduction.rst +++ b/docs/narr/introduction.rst @@ -94,12 +94,12 @@ typically sacrifice "big app" features, and vice versa. We don't think it's a universally reasonable suggestion to write "small apps" in a "small framework" and "big apps" in a "big framework". You can't really -know what size every application will eventually grow to. We don't really +know to what size every application will eventually grow. We don't really want to have to rewrite a previously small application in another framework when it gets "too big". We believe the current binary distinction between -"small" and "large" frameworks is just false; a well-designed framework -should be able to be good at both. Pyramid strives to be that kind of -framework. +frameworks for small and large applications is just false; a well-designed +framework should be able to be good at both. Pyramid strives to be that kind +of framework. To this end, Pyramid provides a set of features, that, combined, are unique amongst Python web frameworks. Lots of other frameworks contain some -- cgit v1.2.3