summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-12-26 17:50:33 -0500
committerChris McDonough <chrism@plope.com>2010-12-26 17:50:33 -0500
commit4062f104319f471952657947c8eaa29e0622d1e3 (patch)
tree223cee3d479de2344eef9290969157f35625c6cd /docs
parentcccde7d6fa003b621383286931540203b66f01f7 (diff)
downloadpyramid-4062f104319f471952657947c8eaa29e0622d1e3.tar.gz
pyramid-4062f104319f471952657947c8eaa29e0622d1e3.tar.bz2
pyramid-4062f104319f471952657947c8eaa29e0622d1e3.zip
wording
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/assets.rst12
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/narr/assets.rst b/docs/narr/assets.rst
index be3325a11..50879ef22 100644
--- a/docs/narr/assets.rst
+++ b/docs/narr/assets.rst
@@ -75,11 +75,13 @@ template file.
There is a second form of asset specification: a *relative* asset
specification. Instead of using an "absolute" asset specification which
includes the package name, in certain circumstances you can omit the package
-name. For example, you might be able to use ``templates/mytemplate.pt``
-instead of ``myapp:templates/some_template.pt``. Such asset specifications
-are usually relative to a "current package." The "current package" is
-usually the package which contains the code that *uses* the asset
-specification.
+name from the specification. For example, you might be able to use
+``templates/mytemplate.pt`` instead of ``myapp:templates/some_template.pt``.
+Such asset specifications are usually relative to a "current package." The
+"current package" is usually the package which contains the code that *uses*
+the asset specification. :app:`Pyramid` APIs which accept relative asset
+specifications typically describe what the asset is relative to in their
+individual documentation.
.. index::
single: add_static_view