summaryrefslogtreecommitdiff
path: root/docs/reference
diff options
context:
space:
mode:
authorJosh Soref <2119212+jsoref@users.noreply.github.com>2024-09-26 13:32:55 -0400
committerGitHub <noreply@github.com>2024-09-26 17:32:55 +0000
commitca1f749c087bc19f6fbcebcd3ee34307959a95d5 (patch)
treeafa4bc0fca4b27d15b99df6da625090b0ef864f2 /docs/reference
parent3c90878460cecaaa7ac879ba0973f94705b7c062 (diff)
Spelling (#5020)
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Diffstat (limited to 'docs/reference')
-rw-r--r--docs/reference/context.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/reference/context.md b/docs/reference/context.md
index 8c6ee9de..0ea88975 100644
--- a/docs/reference/context.md
+++ b/docs/reference/context.md
@@ -59,11 +59,11 @@ 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 can not only give us access to set rule values. It can also let us know
+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 dependant on section
+heading numbering, the table of contents, or page headers dependent on section
headings.
Some functions like [`counter.get`]($counter.get) implicitly access the current