summaryrefslogtreecommitdiff
path: root/docs/reference
diff options
context:
space:
mode:
authorLaurenz <laurmaedje@gmail.com>2024-10-03 15:20:48 +0200
committerGitHub <noreply@github.com>2024-10-03 13:20:48 +0000
commitcbd251f4749241bbf722fe538cb42dd6edef8c1c (patch)
treee58bf85b61ea90fde4b645a4acf93fe7631c9142 /docs/reference
parent0343e038d373b9164679c4d7b2c5345c58c123b7 (diff)
Tweak docs (#5089)
Diffstat (limited to 'docs/reference')
-rw-r--r--docs/reference/context.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/reference/context.md b/docs/reference/context.md
index 0ea88975..bdd520f5 100644
--- a/docs/reference/context.md
+++ b/docs/reference/context.md
@@ -59,12 +59,12 @@ context is known. The body of a context expression may be evaluated zero, one,
or multiple times, depending on how many different places it is put into.
## Location context
-Context cannot only give us access to set rule values. It can also let us know
-_where_ in the document we currently are, relative to other elements, and
-absolutely on the pages. We can use this information to create very flexible
-interactions between different document parts. This underpins features like
-heading numbering, the table of contents, or page headers dependent on section
-headings.
+We've already seen that context gives us access to set rule values. But it can
+do more: It also lets us know _where_ in the document we currently are, relative
+to other elements, and absolutely on the pages. We can use this information to
+create very flexible interactions between different document parts. This
+underpins features like heading numbering, the table of contents, or page
+headers dependent on section headings.
Some functions like [`counter.get`]($counter.get) implicitly access the current
location. In the example below, we want to retrieve the value of the heading