diff --git a/pages/pipelines/_build_states.md b/pages/pipelines/_build_states.md
index 30a78cdd2c..91caa0154d 100644
--- a/pages/pipelines/_build_states.md
+++ b/pages/pipelines/_build_states.md
@@ -1,8 +1,7 @@
 Build state can be one of `creating`, `scheduled`, `running`, `passed`, `failing`, `failed`, `blocked`, `canceling`, `canceled`, `skipped`, `not_run`.
 You can query for `finished` builds to return builds in any of the following states: `passed`, `failed`, `blocked`, or `canceled`.
 
->🚧
-> When a <a href="/docs/pipelines/trigger-step">triggered build</a> fails, the step that triggered it will be stuck in the <code>running</code> state forever.
-
->📘
+> 🚧
+> When a [triggered build](/docs/pipelines/trigger-step) fails, the step that triggered it will be stuck in the `running` state forever.
 > When all the steps in a build are skipped (either by using skip attribute or by using `if` condition), the build state will be marked as `not_run`.
+> By default, all steps depend on the step that uploads them, and they will not run until that one is finished.
diff --git a/styleguides/markdown-syntax-style.md b/styleguides/markdown-syntax-style.md
index 2609e59269..15c965ee5b 100644
--- a/styleguides/markdown-syntax-style.md
+++ b/styleguides/markdown-syntax-style.md
@@ -211,7 +211,7 @@ A regular info callout ("purple"):
 
 ```
 > 📘 An info callout title
-> Callout content can have <code>code</code> or _emphasis_ and other inline elements in it, <a href="#">including links</a>.
+> Callout content can have `code` or _emphasis_ and other inline elements in it, including [internal](/docs/) or <a href="#">external</a> links.
 > Every line break after the first becomes a new paragraph inside the callout.
 ```
 
@@ -220,7 +220,7 @@ This will be rendered as the following HTML in the site:
 ```
 <section class="callout callout--info">
   <p class="callout__title" id="a-callout-title"📘 An info callout title</p>
-  <p>Callout content can have <code>code</code> or <em>emphasis</em> and other inline elements in it, <a href="#">including links</a></p>
+  <p>Callout content can have <code>code</code> or <em>emphasis</em> and other inline elements in it, including <a href="/docs/">internal</a> or <a href="#">external</a> links.</p>
   <p>Every line break after the first becomes a new paragraph inside the callout.</p>
 </section>
 ```
@@ -233,7 +233,7 @@ For troubleshooting callouts ("orange"), use the 🚧 emoji:
 
 ```
 > 🚧 A troubleshooting callout title
-> Callout content can have <code>code</code> or <em>emphasis</em> and other inline elements in it, <a href="#">including links</a>.
+> Callout content can have `code` or _emphasis_ and other inline elements in it, including [internal](/docs/) or <a href="#">external</a> links.
 > Every line break after the first becomes a new paragraph inside the callout.
 ```
 
@@ -241,7 +241,7 @@ While no longer used in the Buildkite Docs, Work-in-progress (WIP) or Experiment
 
 ```
 > 🛠 This marks it as WIP
-> Callout content can have <code>code</code> or <em>emphasis</em> and other inline elements in it, <a href="#">including links</a>.
+> Callout content can have `code` or _emphasis_ and other inline elements in it, including [internal](/docs/) or <a href="#">external</a> links.
 > Every line break after the first becomes a new paragraph inside the callout.
 ```