From 18b43b94f5d08ae32f2248b386f6941c7874100a Mon Sep 17 00:00:00 2001
From: Laura Coursen <lecoursen@github.com>
Date: Wed, 27 Mar 2024 14:35:43 -0500
Subject: [PATCH] Fix code examples for callouts in the style guide (#49871)

Co-authored-by: Annie Streater <12902836+streats@users.noreply.github.com>
---
 .../style-guide.md                            | 21 +++++++++++++++----
 1 file changed, 17 insertions(+), 4 deletions(-)

diff --git a/content/contributing/style-guide-and-content-model/style-guide.md b/content/contributing/style-guide-and-content-model/style-guide.md
index da8ecb18cb..03fdf2d8f6 100644
--- a/content/contributing/style-guide-and-content-model/style-guide.md
+++ b/content/contributing/style-guide-and-content-model/style-guide.md
@@ -89,16 +89,29 @@ Danger callouts will generally only be necessary when describing processes that
 
 We use standard formatting and colors for different types of callouts across doc sets.
 
-Callouts are rendered using Markdown. Specify the type of callout (note, warning, or danger) by placing it in brackets, preceded by an exclamation mark.
+Callouts are rendered using Markdown.
+Tip:
+```[!TIP] Here's a suggestion. ```
 
+```markdown
+>[!TIP] Here's a suggestion.```
 Note:
-```[!NOTE] Keep this in mind.```
+
+```markdown
+>[!NOTE] Keep this in mind.
+```
 
 Warning:
-```[!WARNING] Be careful.```
+
+```markdown
+>[!WARNING] Be careful.
+```
 
 Danger:
-```[!DANGER] Be extremely careful.```
+
+```markdown
+>[!DANGER] Be extremely careful.
+```
 
 Liquid syntax for callouts is still supported and may still appear in older articles, but should not be used for new callouts.