From 7a552b05daa5ee3c6109d94e9ee42faf4b48a6cd Mon Sep 17 00:00:00 2001 From: Joseph Nix Date: Thu, 12 Apr 2018 15:10:12 -0500 Subject: [PATCH] [master] Minor rewording of process-template-context content. --- .../api/plugins/events/process-template-context/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/api/plugins/events/process-template-context/contents.lr b/content/docs/api/plugins/events/process-template-context/contents.lr index 9518769d..c6a144ed 100644 --- a/content/docs/api/plugins/events/process-template-context/contents.lr +++ b/content/docs/api/plugins/events/process-template-context/contents.lr @@ -12,8 +12,8 @@ This event is emitted right before a template is rendered and can be used to inject values directly into the template context. The context is always provided and is a dictionary that can be modified. -What's important to know that this is not the only way to modify the template -context. Another one is to modify the underlying [Jinja Environment +It's important to know that this is not the only way to modify the template +context. Another method is to modify the underlying [Jinja Environment :ref](../../../environment/jinja-env/) on the environment directly. The difference is that the globals from the `jinja_env` are available in *all* templates whereas the modified template context is only available in the