summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMax <me@mkor.je>2024-11-12 12:54:25 +0000
committerGitHub <noreply@github.com>2024-11-12 12:54:25 +0000
commit8d4f01d2847e116c2156f02a869b526859364953 (patch)
treea8b76afbcb2c162437c8f2f053cca0ac2466d9f1 /docs
parentdadc2176e2a71740f0f8afb252229144cc661652 (diff)
Add support for page references through new `ref.form` property (#4729)
Diffstat (limited to 'docs')
-rw-r--r--docs/guides/page-setup.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/guides/page-setup.md b/docs/guides/page-setup.md
index d4a1e62c..c93a778e 100644
--- a/docs/guides/page-setup.md
+++ b/docs/guides/page-setup.md
@@ -433,7 +433,7 @@ frequently used for [figures]($figure.placement).
### Use columns anywhere in your document { #columns-anywhere }
To create columns within a nested layout, e.g. within a rectangle, you can use
the [`columns` function]($columns) directly. However, it really should only be
-used within nested layouts. At the page-level, the page set rule is preferrable
+used within nested layouts. At the page-level, the page set rule is preferable
because it has better interactions with things like page-level floats,
footnotes, and line numbers.