From f34563d5620ba21248cea2e5991dc2e77bc64641 Mon Sep 17 00:00:00 2001 From: Dipika Bhattacharya Date: Wed, 21 Jan 2026 08:52:56 -0500 Subject: [PATCH] Update macro guidance for fit-conetnt() --- .../en-us/mdn/writing_guidelines/page_structures/links/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/mdn/writing_guidelines/page_structures/links/index.md b/files/en-us/mdn/writing_guidelines/page_structures/links/index.md index 11dc03fd492f098..07b940092a4e60c 100644 --- a/files/en-us/mdn/writing_guidelines/page_structures/links/index.md +++ b/files/en-us/mdn/writing_guidelines/page_structures/links/index.md @@ -93,7 +93,7 @@ A few other behaviors of the `CSSxRef` macro worth noting include: - `fit-content()` function (`Web/CSS/Reference/Values/fit-content_function`) vs. `fit-content` keyword (`Web/CSS/Reference/Values/fit-content`) - **Macro**: `\{{CSSxRef("fit-content_function", "fit-content()")}}` vs. `\{{CSSxRef("fit-content")}}` (this is currently an exception where you need to provide the second parameter to get the correct link text for the function.) + **Macro**: `\{{CSSxRef("fit-content()")}}` vs. `\{{CSSxRef("fit-content")}}` - `flex` property (`Web/CSS/Reference/Properties/flex`) vs. `` data type (`Web/CSS/Reference/Values/flex_value`)