From 4062f104319f471952657947c8eaa29e0622d1e3 Mon Sep 17 00:00:00 2001 From: Chris McDonough Date: Sun, 26 Dec 2010 17:50:33 -0500 Subject: wording --- docs/narr/assets.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) (limited to 'docs') 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 -- cgit v1.2.3