From b12b3c7467b76a2a3136520b4177096517fe64d2 Mon Sep 17 00:00:00 2001 From: Drew Powers Date: Thu, 24 Oct 2024 17:00:25 -0600 Subject: [PATCH] Fix design token heading levels (#254) --- technical-reports/format/design-token.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/technical-reports/format/design-token.md b/technical-reports/format/design-token.md index 00cebdb..c9eb376 100644 --- a/technical-reports/format/design-token.md +++ b/technical-reports/format/design-token.md @@ -84,7 +84,7 @@ Furthermore, due to the syntax used for [token aliases](#aliases-references) the While `$value` is the only required property for a token, a number of additional properties MAY be added: -## Description +### Description A plain text description explaining the token's purpose can be provided via the optional `$description` property. Tools MAY use the description in various ways. @@ -111,7 +111,7 @@ The value of the `$description` property MUST be a plain JSON string, for exampl -## Type +### Type Design tokens always have an unambiguous type, so that tools can reliably interpret their value. @@ -145,7 +145,7 @@ For example: -## Extensions +### Extensions The optional **`$extensions`** property is an object where tools MAY add proprietary, user-, team- or vendor-specific data to a design token. When doing so, each tool MUST use a vendor-specific key whose value MAY be any valid JSON data. @@ -178,5 +178,3 @@ Tool vendors are encouraged to publicly share specifications of their extension

The extensions section is not limited to vendors. All token users can add additional data in this section for their own purposes.

- -## More token properties TBC