summaryrefslogtreecommitdiff
path: root/docs/designdefense.rst
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2013-04-05 23:23:38 -0700
committerMichael Merickel <michael@merickel.org>2013-04-05 23:23:38 -0700
commit55ab183d1184dff75e66a2c80e9cadd4aa7c4b6f (patch)
tree1b850fdb3fd206594a8c0c53c16f7b4b1fc01444 /docs/designdefense.rst
parenta62ebd5725338d753d49ff1b6b8bf0fe95b19c92 (diff)
parent125ea45ae864a5513e6d83fdded6ceea9516b578 (diff)
downloadpyramid-55ab183d1184dff75e66a2c80e9cadd4aa7c4b6f.tar.gz
pyramid-55ab183d1184dff75e66a2c80e9cadd4aa7c4b6f.tar.bz2
pyramid-55ab183d1184dff75e66a2c80e9cadd4aa7c4b6f.zip
Merge pull request #972 from tshepang/diff
fix some cross-references
Diffstat (limited to 'docs/designdefense.rst')
-rw-r--r--docs/designdefense.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/designdefense.rst b/docs/designdefense.rst
index 7bc37ac06..de607fda3 100644
--- a/docs/designdefense.rst
+++ b/docs/designdefense.rst
@@ -514,7 +514,7 @@ the method is called (if possible) with its argument list filled with values
mentioned therein. TurboGears and Pylons 1.X operate similarly.
Out of the box, :app:`Pyramid` is configured to have none of these features.
-By default, :mod:`pyramid` view callables always accept only ``request`` and
+By default, :app:`Pyramid` view callables always accept only ``request`` and
no other arguments. The rationale: this argument specification matching done
aggressively can be costly, and :app:`Pyramid` has performance as one of its
main goals, so we've decided to make people, by default, obtain information
@@ -1678,7 +1678,7 @@ was written to address these issues.
If it's Zope3-the-web-framework, Pyramid is *definitely* not that. Making
use of lots of Zope 3 technologies is territory already staked out by the
:term:`Grok` project. Save for the obvious fact that they're both web
-frameworks, :mod:`Pyramid` is very, very different than Grok. Grok exposes
+frameworks, :app:`Pyramid` is very, very different than Grok. Grok exposes
lots of Zope technologies to end users. On the other hand, if you need to
understand a Zope-only concept while using Pyramid, then we've failed on some
very basic axis.