From aa3dfd1c20f11d7e032b2b18e0f1136d49907aa0 Mon Sep 17 00:00:00 2001 From: Dominic R Date: Mon, 3 Feb 2025 20:21:44 -0500 Subject: [PATCH] fix anchor --- website/docs/developer-docs/docs/style-guide.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/developer-docs/docs/style-guide.mdx b/website/docs/developer-docs/docs/style-guide.mdx index 8c45c17402e5..0e007d8c59ad 100644 --- a/website/docs/developer-docs/docs/style-guide.mdx +++ b/website/docs/developer-docs/docs/style-guide.mdx @@ -12,8 +12,8 @@ If you notice any inconsistencies, feel free to open an [Issue](https://github.c - [Word Choices](#word-choices) - [Formatting Guidelines](#formatting-guidelines) - [Component-Based Formatting](#component-based-formatting) -- [Error Message Formatting & Troubleshooting](#error-messages) -- [Accessibility Best Practices](#accessibility) +- [Error Message Formatting and Troubleshooting](#error-message-formatting-and-troubleshooting) +- [Accessibility Best Practices](#accessibility-best-practices) - [React Component Imports](#react-component-imports) - [Notes and Warnings](#notes-and-warnings) @@ -162,7 +162,7 @@ Tabs improve readability when presenting different configurations or setup optio When importing React components (e.g.: Tabs), imports must be placed at the top of the file. -## Error Message Formatting & Troubleshooting +## Error Message Formatting and Troubleshooting When documenting error messages: