Apply suggestions from code review

Co-authored-by: Jun Lee <[email protected]>

Author: RebeccaTamachiro

src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx

@@ -14,7 +14,7 @@ import { Render, APIRequest, Details, Example, TabItem, Tabs, GlossaryTooltip }
 
 - You can upgrade individual IPs within a Spectrum prefix to a CDN IP. For example, if you have a Spectrum prefix 203.0.113.0/24, you can upgrade 203.0.113.1 to CDN.
 
-This guide will use the first example, considering a prefix that was onboarded to the CDN and will have a few IPs upgraded to Spectrum.
+This guide will use the first example and consider a prefix that was onboarded to the CDN, with a few IPs upgraded to Spectrum.
 
 ## Before you begin
 

src/content/partials/byoip/service-bindings-create-binding.mdx

@@ -7,7 +7,7 @@ params:
 import { Example, APIRequest } from "~/components";
 
 :::caution[Caution]
-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. Make a `POST` request to the [Create service binding](/api/resources/addressing/subresources/prefixes/subresources/service_bindings/methods/create/) endpoint, indicating the IP address you want to bind to {props.added_product}. Specify the **corresponding network mask** as needed.

src/content/partials/byoip/service-bindings-prereqs.mdx

@@ -6,7 +6,7 @@ params:
 
 import { Details } from "~/components";
 
-Although it is possible to add discrete bindings for non-contiguous CIDR blocks, implementing service bindings through an **aggregated** CIDR block is **strongly** recommended as it is more efficient.
+Cloudflare **strongly** recommends implementing service bindings through an **aggregated** CIDR block, as it is more efficient than adding discrete bindings for non-contiguous CIDR blocks.
 
 <Details header="Example">
 
@@ -27,7 +27,7 @@ Add one discrete {props.added_product} service binding for `203.0.113.16` with a
 
 </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.
 
 :::note
 This guide assumes that the prefix is tied to a single Cloudflare account that has both {props.pre_existing_product} and {props.added_product} properties. If you are using [prefix delegations](/byoip/concepts/prefix-delegations/), the service bindings must be [created](#2-create-service-binding) on the parent account.