diff --git a/mkdocs.yml b/mkdocs.yml
index 37f4d00b0a..e26c0ff90f 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -12,6 +12,8 @@ plugins:
   - awesome-pages
   - macros:
       include_dir: examples
+markdown_extensions:
+  - admonition
 nav:
   - Introduction: index.md
   - Concepts:
diff --git a/site-src/v1alpha2/references/cross-namespace-references.md b/site-src/v1alpha2/references/cross-namespace-references.md
index 4d599d24f2..a0302d9de2 100644
--- a/site-src/v1alpha2/references/cross-namespace-references.md
+++ b/site-src/v1alpha2/references/cross-namespace-references.md
@@ -10,10 +10,9 @@ In the past, we've seen that forwarding traffic across namespace boundaries is a
 desired feature, but a safeguard like ReferencePolicy,
 [vulnerabilities](https://github.com/kubernetes/kubernetes/issues/103675) can emerge.
 
-!!!note
-
+!!! note
     When discussing the process of creating cross-namespace object references, this
-    document and the documentation on the API itself refers to the object being
+    document and the documentation on the API itself refer to the object being
     referred to as "the referent object", using the
     [meaning](https://dictionary.cambridge.org/dictionary/english/referent)
     of "referent" to be "the person, thing, or idea that a word, phrase, or object