removed redundant message (#17012)

cloudflare · Sep 23, 2024 · 0d2d570 · 0d2d570
1 parent e0ed0c3
commit 0d2d570
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/...ation/connector/network-options/application-based-policies/breakout-traffic.mdx b/...ation/connector/network-options/application-based-policies/breakout-traffic.mdx
@@ -10,7 +10,7 @@ import { Render, TabItem, Tabs } from "~/components";
 
 Breakout traffic allows you to define which applications should bypass Cloudflare’s security filtering, and go directly to the Internet. It works via DNS requests inspection. This means that if your network is caching DNS requests, Breakout traffic will only take effect after you cache entries expire and your client issues a new DNS request that the Magic WAN Connector can detect. This can take several minutes.
 
-:::caution[Warning]
+:::caution
 Breakout traffic will not work for applications that use DNS-over-HTTPs.
 :::
 

diff --git a/...on/connector/network-options/application-based-policies/prioritized-traffic.mdx b/...on/connector/network-options/application-based-policies/prioritized-traffic.mdx
@@ -12,7 +12,7 @@ Prioritized traffic allows you to define which applications Magic WAN Connector
 
 Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.
 
-:::caution[Warning]
+:::caution
 Prioritized traffic will not work for applications that use DNS-over-HTTPS.
 :::