Overall text review and add info on checking IPs via dash

Author: RebeccaTamachiro

src/content/docs/smart-shield/configuration/dedicated-egress-ips/about.mdx

@@ -21,7 +21,7 @@ flowchart LR
 
 ## Egress IPs
 
-Zooming in to what happens as a request routes through Cloudflare, you can consider two parts of the process: ingress and egress.
+Zooming into what happens as a request routes through Cloudflare, you can consider two parts of the process: ingress and egress.
 
 ```mermaid
 flowchart LR
@@ -34,9 +34,19 @@ Ingress refers to the data center where the client request lands on, based on In
 
 Traditionally, Cloudflare maintains a very large pool of egress IPs that are used by all Cloudflare customers and are [publicly documented](https://www.cloudflare.com/ips/). With Dedicated CDN Egress IPs, Cloudflare connects to your origin using IPs that are reserved for you.
 
-:::note
+### BYOIP or Cloudflare-leased
+
 Each dedicated CDN egress IP pool can consist of either IPs from a [BYOIP prefix](/byoip/) or Cloudflare-leased IPs. A single dedicated CDN egress IP pool cannot contain both BYOIPs and leased IPs.
-:::
+
+<Render
+  file="check-leased-ips"
+	product="byoip"
+	params={{
+		product: "dedicated IPs for CDN egress"
+	}}
+/>
+
+If you are using BYOIP, refer to [**IP addresses** > **BYOIP prefixes**](https://dash.cloudflare.com/?to=/:account/ip-addresses/ip-prefixes) instead.
 
 ## IPs allocation
 
@@ -56,7 +66,7 @@ Refer to [connection forwarding](#connection-forwarding) to understand how reque
 
 <Render file="concurrent-connections-explainer" product="aegis" />
 
-Dedicated CDN Egress IPs also benefit from [connection reuse and connection coalescing](/smart-shield/concepts/connection-reuse/).
+Dedicated CDN Egress IPs also benefit from [connection reuse and coalescing](/smart-shield/concepts/connection-reuse/).
 
 GraphQL Analytics API allows you to get visibility over [IPs utilization](/smart-shield/configuration/dedicated-egress-ips/ips-utilization/).
 

src/content/docs/smart-shield/configuration/dedicated-egress-ips/index.mdx

@@ -17,10 +17,10 @@ If you are interested in using Smart Shield Advanced with Dedicated CDN Egress I
 
 ## Benefits
 
-With dedicated egress IPs, you can:
+With Dedicated CDN Egress IPs, you can:
 
-* Lock down your network firewall to only allow traffic from the your dedicated CDN egress IPs.
-* Use [Cloudflare Access](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
+* Lock down your network firewall to only allow traffic from your dedicated IPs.
+* Use [Cloudflare Access and CNI](/smart-shield/configuration/dedicated-egress-ips/other-products/#access-and-cni) to secure your applications without installing software or customizing code on your server.
 * Ensure only authorized [Workers](/smart-shield/configuration/dedicated-egress-ips/other-products/#workers) can access your origin services.
 
 ## Scope

src/content/docs/smart-shield/configuration/dedicated-egress-ips/other-products.mdx

@@ -12,14 +12,10 @@ Use Dedicated CDN Egress IPs in combination with different Cloudflare products.
 
 You can use Dedicated CDN Egress IPs combined with [Cloudflare Network Interconnect (CNI)](/network-interconnect/) to secure your applications with [Cloudflare Access](/cloudflare-one/access-controls/policies/) without installing software or customizing code on your server.
 
-While Access allows you to enforce policies at the hostname level, other solutions are usually necessary to protect against origin IP bypass — when an attacker knows your origin server IP and uses it to directly interact with the target application.
-
-With Dedicated CDN Egress IPs, you only allow a small number of IPs (that are not publicly listed) through your network firewall. And with Cloudflare Network Interconnect, you can use a completely private path between Cloudflare and your application server, without exposure to the public Internet.
+While Access allows you to enforce policies at the hostname level, other solutions are usually necessary to protect against origin IP bypass [^1]. With Dedicated CDN Egress IPs, you only allow a small number of IPs (that are not publicly listed) through your network firewall and, with Cloudflare Network Interconnect, you can use a completely private path between Cloudflare and your application server, without exposure to the public Internet. For details and background, refer to the [Cloudflare blog](https://blog.cloudflare.com/access-aegis-cni).
 
 Dedicated CDN Egress IPs are included within [BGP advertisement over CNI](/network-interconnect/).
 
-For details and background, refer to the [Cloudflare blog](https://blog.cloudflare.com/access-aegis-cni).
-
 ## Data Localization Suite
 
 [Data Localization Suite (DLS)](/data-localization/) is an enterprise add-on that enables you to choose the location where Cloudflare encrypts, decrypts, and stores data.
@@ -58,4 +54,6 @@ Workers subrequests — requests from one Worker to another — are expected to
 
 ### `connect`
 
-For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Dedicated CDN Egress IPs are **not** used.
+For [`connect()` requests](/workers/runtime-apis/tcp-sockets/) - which create outbound TCP connections from Workers - Dedicated CDN Egress IPs are **not** used.
+
+[^1]: When an attacker knows your origin server IP and uses it to directly interact with the target application.