From 5af30057aa5528eaa277603ee717b7111c147a51 Mon Sep 17 00:00:00 2001 From: Steve Piercy Date: Sun, 19 Aug 2018 00:36:46 -0700 Subject: Standardize Unix capitalization --- docs/narr/templates.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/narr/templates.rst') diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst index bc3e913ff..1ccab9d3c 100644 --- a/docs/narr/templates.rst +++ b/docs/narr/templates.rst @@ -52,7 +52,7 @@ directory containing the file which defines the view configuration. In this case, this is the directory containing the file that defines the ``sample_view`` function. Although a renderer path is usually just a simple relative pathname, a path named as a renderer can be absolute, starting with a -slash on UNIX or a drive letter prefix on Windows. The path can alternatively +slash on Unix or a drive letter prefix on Windows. The path can alternatively be an :term:`asset specification` in the form ``some.dotted.package_name:relative/path``. This makes it possible to address template assets which live in another package. For example: @@ -317,7 +317,7 @@ Similar renderer configuration can be done imperatively. See See also :ref:`built_in_renderers`. Although a renderer path is usually just a simple relative pathname, a path -named as a renderer can be absolute, starting with a slash on UNIX or a drive +named as a renderer can be absolute, starting with a slash on Unix or a drive letter prefix on Windows. The path can alternatively be an :term:`asset specification` in the form ``some.dotted.package_name:relative/path``, making it possible to address template assets which live in another package. -- cgit v1.2.3