diff --git a/website/content/docs/agent/limits/index.mdx b/website/content/docs/agent/limits/index.mdx
index 9a522dc3313a..ff6f2213c812 100644
--- a/website/content/docs/agent/limits/index.mdx
+++ b/website/content/docs/agent/limits/index.mdx
@@ -31,6 +31,10 @@ Setting limits per source IP requires Consul Enterprise.
 
 You can define request rate limits in the agent configuration and in the control plane request limit configuration entry. The configuration entry also supports rate limit configurations for Consul resources. Consul perfroms the following order of operations when determing request rate limits:
 
+![Diagram showing the order of operations for determining request rate limits.](/img/agent-rate-limiting-ops-order.jpg#light-theme-only)
+![Diagram showing the order of operations for determining request rate limits.](/img/agent-rate-limiting-ops-order-dark.jpg#dark-theme-only)
+
+<!--
 1. Parse request.
 1. Does the request reach a global server limit?
    - No: Proceed to the next stage.
@@ -50,6 +54,7 @@ You can define request rate limits in the agent configuration and in the control
    - No: Proceed to the next stage.
    - Yes: Return an error that the requested resource has been exhausted.
 1. Handle the request.
+-->
 
 ## Kubernetes
 
diff --git a/website/public/img/agent-rate-limiting-ops-order-dark.jpg b/website/public/img/agent-rate-limiting-ops-order-dark.jpg
new file mode 100644
index 000000000000..c78c279973ae
Binary files /dev/null and b/website/public/img/agent-rate-limiting-ops-order-dark.jpg differ
diff --git a/website/public/img/agent-rate-limiting-ops-order.jpg b/website/public/img/agent-rate-limiting-ops-order.jpg
new file mode 100644
index 000000000000..8f5105aa061e
Binary files /dev/null and b/website/public/img/agent-rate-limiting-ops-order.jpg differ