Overall review and touchups

Author: RebeccaTamachiro

src/content/docs/byoip/service-bindings/index.mdx

@@ -9,20 +9,20 @@ sidebar:
 description: In IP address management, service binding refers to the association of IPs to specific Cloudflare services. Review the available options and the API endpoints to set up service bindings.
 ---
 
-Service Bindings are mappings that control whether traffic destined for a given IP address is routed to Magic Transit, the CDN pipeline (Layer 7 HTTP-based), or Spectrum pipeline (Layer 4 or Layer 7 HTTP with custom ports).
+Service bindings are mappings that control whether traffic destined for a given IP address is routed to [Magic Transit](/magic-transit/), the CDN pipeline [^1], or the Spectrum pipeline [^2].
 
 :::note
 Service binding operations are currently only available via API. You can find all endpoints and their specifications in the [Cloudflare API documentation](/api/operations/ip-address-management-service-bindings-list-service-bindings).
 :::
 
 ## Scope
 
-Customers using BYOIP with Magic Transit can leverage the [service binding API endpoints](/api/operations/ip-address-management-service-bindings-list-service-bindings) to selectively route traffic through the CDN (Layer 7 HTTP-based) or Spectrum (Layer 4 and Layer 7 HTTP with custom ports) pipelines on a per-IP address basis.
+Customers using BYOIP with Magic Transit can leverage the [service binding API endpoints](/api/operations/ip-address-management-service-bindings-list-service-bindings) to selectively route traffic through the CDN [^1] or Spectrum [^2] pipelines on a per-IP address basis.
 
 You can upgrade individual IPs within a Magic Transit prefix to either a CDN IP or a Spectrum IP. For example, if you have `203.0.113.0/24`, you can upgrade `203.0.113.1` to CDN and `203.0.113.2` to Spectrum.
 
 :::caution
-Magic Transit customers must ensure that their contract allows them to use CDN and/or Spectrum services to the desired extent.
+Magic Transit customers must ensure that their contract includes CDN and/or Spectrum according to their needs.
 :::
 
 ### CDN (Cache)
@@ -39,4 +39,7 @@ When a service binding of type `Spectrum` is applied, once the change has propag
 
 - You must keep Magic Transit as a common base service, spanning all addresses in your prefix.
 - When adding a service binding for a given IP address, it must be either a CDN service binding or a Spectrum service binding. It is not possible (or necessary) to bind both services.
--  Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's Global Network. Services for the IP addresses in scope will likely be disrupted during this window.
+-  Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
+
+[^1]: Layer 7 HTTP-based
+[^2]: Layer 4 or Layer 7 HTTP with custom ports

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

@@ -9,9 +9,9 @@ sidebar:
 
 import { Details, Example, TabItem, Tabs, GlossaryTooltip } from "~/components";
 
-[Magic Transit](/magic-transit/) customers using [BYOIP](/byoip/) can also benefit from the performance, reliability, and security that Cloudflare offers for HTTP-based applications.
+[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 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/), [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 Firewal (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.
 
@@ -40,7 +40,7 @@ Efficiency is paramount when planning how you will implement service bindings. I
 
   </Details>
 
-Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global  network. Services for the IP addresses in scope will likely be disrupted during this window.
+Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
 
 
 ## 1. Get account information
@@ -51,7 +51,7 @@ Once a service binding is created (or deleted), it will take four to six hours t
 
 <Example>
 
-At this point, continuing the example mentioned above, you should have a mapping similar to the following:
+At this point, continuing the [example](#before-you-begin), you should have a mapping similar to the following:
 
 | Variables  | Description                                        |
 |-------------------------------|----------------------------------------------------|
@@ -77,7 +77,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/addressing/prefi
 Once a service binding is created (or deleted), it will take four to six hours to propagate across Cloudflare's global network. Services for the IP addresses in scope will likely be disrupted during this window.
 :::
 
-1. Make a `POST` request to the [Create service binding](/api/operations/ip-address-management-service-bindings-create-service-binding/) endpoint, indicating the IP address you want to bind to the CDN. Specify the **corresponding network mask** as needed.
+1. Make a `POST` request to the [Create service binding](/api/operations/ip-address-management-service-bindings-create-service-binding) endpoint, indicating the IP address you want to bind to the CDN. Specify the **corresponding network mask** as needed.
 
 <Example>