diff --git a/src/pages/docs/runbooks/config-as-code-runbooks.md b/src/pages/docs/runbooks/config-as-code-runbooks.md
index 6436b44fbd..33ce8db3dd 100644
--- a/src/pages/docs/runbooks/config-as-code-runbooks.md
+++ b/src/pages/docs/runbooks/config-as-code-runbooks.md
@@ -82,7 +82,7 @@ The information that was previously found on the **Snapshot** page is still avai
 
 [Runbook triggers](/docs/runbooks/scheduled-runbook-trigger) will always run CaC Runbooks from the latest commit on your default branch, just as non-CaC runbook triggers will only run published runbooks.
 
-:::{.hint}
+:::div{.hint}
 If you have steps that use packages in your runbook process we only support getting latest non-prerelease versions. To use prerelease packages you would need to hard-code the version on individual steps.
 :::
 
diff --git a/src/pages/docs/runbooks/scheduled-runbook-trigger/index.md b/src/pages/docs/runbooks/scheduled-runbook-trigger/index.md
index f9d1d61947..bc9c4f0091 100644
--- a/src/pages/docs/runbooks/scheduled-runbook-trigger/index.md
+++ b/src/pages/docs/runbooks/scheduled-runbook-trigger/index.md
@@ -34,7 +34,7 @@ Scheduled runbook triggers provide a way to configure your runbooks to run on a
 
 If you are using [tenants](/docs/tenants) you can select the tenants that the runbook will run against. For each tenant, the published runbook will run against the tenant's environment. 
 
-:::{.hint}
+:::div{.hint}
 If you have steps that use packages in your runbook process we only support getting latest non-prerelease versions. To use prerelease packages you would need to hard-code the version on individual steps.
 :::