Clarifying CIDR block usage for Address Maps in MT w/ L7 guide

Author: erfianugrah

src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx

@@ -11,32 +11,32 @@ import { Details, Example, TabItem, Tabs, GlossaryTooltip } from "~/components";
 
 [Magic Transit](/magic-transit/) customers using BYOIP can also benefit from the performance, reliability, and security that Cloudflare offers for HTTP-based applications.
 
-This documentation covers using the Cloudflare API to configure [service bindings](/byoip/service-bindings/) within Cloudflare's IP Address Management framework. Service bindings allow BYOIP customers to selectively route traffic on a per-IP address basis to the CDN pipeline (which includes [Cache](/cache/), [Web Application Firewal (WAF)](/waf/), and more).
+This documentation covers using the Cloudflare API to configure [service bindings](/byoip/service-bindings/) within Cloudflare's IP Address Management framework. Service bindings allow BYOIP customers to selectively route traffic on a per-IP address basis to the CDN pipeline (which includes [Cache](/cache/), [Web Application Firewall (WAF)](/waf/), and more).
 
 It is also possible to define service bindings to route traffic to the Spectrum pipeline selectively. However, this is not in the scope of this guide.
 
 It is important to note that traffic routed to the CDN pipeline is protected at Layers 3 and 4 by the inherent DDoS protection capabilities native to the CDN pipeline.
 
 ## Before you begin
 
-Efficiency is paramount when planning how you will implement service bindings. Implementing service bindings through an aggregated CIDR block is strongly recommended.
+Even though it is possible to add discrete bindings for non-contiguous CIDR blocks (having to use different prefixes might necessitate this), implementing service bindings through an **aggregated** CIDR block is **strongly** recommended.
 
   <Details header="Example" >
 
   **Magic Transit protected prefix:** `203.0.113.100/24`
 
   **IPs to upgrade to the CDN:**
 
-  `203.0.113.16`
-  `203.0.113.17`
-  `203.0.113.18`
-  `203.0.113.19`
-  `203.0.113.20`
-  `203.0.113.21`
-  `203.0.113.22`
+  `203.0.113.16`<br />
+  `203.0.113.17`<br />
+  `203.0.113.18`<br />
+  `203.0.113.19`<br />
+  `203.0.113.20`<br />
+  `203.0.113.21`<br />
+  `203.0.113.22`<br />
   `203.0.113.23`
 
-  **Best practice:** Add one discrete CDN service binding for `203.0.113.16` with a `/29` netmask.
+	Add one discrete CDN service binding for `203.0.113.16` with a `/29` netmask.
 
   </Details>