summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDanny Navarro <j@dannynavarro.net>2010-12-25 12:37:32 +0100
committerDanny Navarro <j@dannynavarro.net>2010-12-25 12:37:32 +0100
commitea32d63773bec2493326c04c896f224e25c532c4 (patch)
tree8f1ec52247a12f5fe22045e12b3ec9598fd29c13 /docs
parent291bcc034c59a17afa46443499ae6a670718055d (diff)
downloadpyramid-ea32d63773bec2493326c04c896f224e25c532c4.tar.gz
pyramid-ea32d63773bec2493326c04c896f224e25c532c4.tar.bz2
pyramid-ea32d63773bec2493326c04c896f224e25c532c4.zip
typo
Diffstat (limited to 'docs')
-rw-r--r--docs/designdefense.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 1b8aa1512..db399fffa 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -260,7 +260,7 @@ ZCA registry gives us, and we have long-ago borne the weight of understanding
what it does and how it works. The authors of :app:`Pyramid` understand the
ZCA deeply and can read code that uses it as easily as any other code.
-But we recognize that developers who my want to extend the framework are not
+But we recognize that developers who might want to extend the framework are not
as comfortable with the ZCA registry API as the original developers are with
it. So, for the purposes of being kind to third-party :app:`Pyramid`
framework developers in, we've drawn some lines in the sand.