From 828943156ab5619f54be629dcee7c0ffc74a22be Mon Sep 17 00:00:00 2001
From: Theo Lemay <16546293+theol0403@users.noreply.github.com>
Date: Mon, 18 Mar 2024 18:34:45 -0400
Subject: [PATCH] fix(docs): Fix hold-tap info callout (#2211)

The hold-while-undecided callout does not properly render in the docs. This fixes it.
---
 docs/docs/behaviors/hold-tap.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/behaviors/hold-tap.mdx b/docs/docs/behaviors/hold-tap.mdx
index 191e820dd43..5217cf79e29 100644
--- a/docs/docs/behaviors/hold-tap.mdx
+++ b/docs/docs/behaviors/hold-tap.mdx
@@ -87,7 +87,7 @@ For example, if you press `&mt LEFT_SHIFT A` and then release it without pressin
 
 If enabled, the hold behavior will immediately be held on hold-tap press, and will release before the behavior is sent in the event the hold-tap resolves into a tap. With most modifiers this will not affect typing, and is useful for using modifiers with the mouse.
 
-:::note Alt/Win/Cmd behavior
+:::info[Alt/Win/Cmd behavior]
 In some applications/desktop environments, pressing Alt keycodes by itself will have its own behavior like activate a menu and Gui keycodes will bring up the start menu or an application launcher.
 :::