docs(templates): the scope-fallback hazard headline was backwards

It read "an inner key silently loses to an outer key of the SAME NAME" --
false: the document's own num entry, two paragraphs below, shows the
opposite (inside {{#weeks}}, a bare {{num}} is the week's own number,
correctly, because the inner scope wins). The real hazard, matching the
body text and the name example that were already correct: a DOTTED path
that resolves only part way inward (the day's own name object exists but
lacks the key the path needs) falls back WHOLESALE to an outer scope of
the same name, not a bare key losing outright. Corrected the headline
only; re-linted clean with groff -man -Tutf8 -ww -z.

1 files changed, 8 insertions, 2 deletions

diff --git a/man/colitur-templates.5 b/man/colitur-templates.5
index a7e4992..2f42d68 100644
--- a/man/colitur-templates.5
+++ b/man/colitur-templates.5
@@ -131,8 +131,14 @@ could never reach
 .BR {{year}} ,
 which lives only on the outermost object.
 .PP
-.B The hazard: an inner key silently loses to an outer key of the SAME NAME.
-Falling back outward means a name that exists at
+.B The hazard: a DOTTED PATH that resolves only PART WAY inward falls back
+.B WHOLESALE to an outer scope of the SAME NAME.
+A bare key inside the immediately enclosing section is not at risk this way
+\(em it either resolves right there or fails outright (see
+.B num
+below); it is specifically a dotted path, one step of which is missing from
+the inner object, that abandons the whole path and restarts the lookup one
+level out. Falling back outward means a name that exists at
 .I both
 levels never fails and never warns \(em it just silently resolves to the
 .I outer