[MWAN] Added warning box (#16627)

* added warning box

* added note and warning about dns

* Update src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/prioritized-traffic.mdx

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>

Author: marciocloudflare

src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/breakout-traffic.mdx

@@ -4,14 +4,17 @@ title: Breakout traffic
 head: []
 description: Breakout traffic allows you to define which applications should
   bypass Cloudflare’s security filtering.
-
 ---
 
-import { Render } from "~/components"
+import { Render } 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]
 Breakout traffic will not work for applications that use DNS-over-HTTPs.
+:::
+
+<br />
 
 ```mermaid
 flowchart LR
@@ -36,7 +39,10 @@ Refer to [Traffic steering](/magic-wan/reference/traffic-steering/) to learn how
 
 You need to configure Breakout traffic for each of your existing sites, as it is a per-site configuration.
 
-<Render file="connector/app-aware-policies/add-app" params={{ one: "Breakout traffic" }} />
+<Render
+	file="connector/app-aware-policies/add-app"
+	params={{ one: "Breakout traffic" }}
+/>
 
 6. Select one or more applications that should bypass Cloudflare filtering from the list. You can also use the search box.
 7. Select **Add applications**.
@@ -45,4 +51,7 @@ The traffic for that application will now go directly to the Internet and bypass
 
 ## Delete an application
 
-<Render file="connector/app-aware-policies/delete-app" params={{ one: "Breakout traffic" }} />
+<Render
+	file="connector/app-aware-policies/delete-app"
+	params={{ one: "Breakout traffic" }}
+/>

src/content/docs/magic-wan/configuration/connector/network-options/application-based-policies/prioritized-traffic.mdx

@@ -4,18 +4,26 @@ title: Prioritized traffic
 head: []
 description: Prioritized traffic allows you to define which applications are
   processed first by Magic WAN Connector.
-
 ---
 
-import { Render } from "~/components"
+import { Render } from "~/components";
 
 Prioritized traffic allows you to define which applications Magic WAN Connector should process first. Applications not in the list will be queued behind prioritized traffic.
 
+Similarly to breakout traffic, prioritized traffic also works via DNS requests inspection.
+
+:::caution[Warning]
+Prioritized traffic will not work for applications that use DNS-over-HTTPS.
+:::
+
 ## Add an application
 
 You need to configure Prioritized traffic for each of your existing sites, as it is a per-site configuration.
 
-<Render file="connector/app-aware-policies/add-app" params={{ one: "Prioritized traffic" }} />
+<Render
+	file="connector/app-aware-policies/add-app"
+	params={{ one: "Prioritized traffic" }}
+/>
 
 6. Select one or more applications that should take precedence over other traffic. You can also use the search box.
 7. Select **Add applications**.
@@ -24,4 +32,7 @@ The traffic for the applications you chose are now processed first by Connector.
 
 ## Delete an application
 
-<Render file="connector/app-aware-policies/delete-app" params={{ one: "Prioritized traffic" }} />
+<Render
+	file="connector/app-aware-policies/delete-app"
+	params={{ one: "Prioritized traffic" }}
+/>