Update src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx

Author: kodster28

src/content/changelog/gateway/2025-04-28-FDQN-Filtering-Egress-Policies.mdx

@@ -12,6 +12,6 @@ Cloudflare One administrators can now control which egress IP is used based on a
 - During the beta period, you can use these selectors with traffic on-ramped to Gateway with the WARP client, proxy endpoints (commonly deployed with PAC files), or Cloudflare Browser Isolation.
   - For WARP client support, additional configuration is required. For more information, refer to the [WARP client configuration documentation](/cloudflare-one/policies/gateway/egress-policies/#limitations).
 
-![egress by FQDN and Hostname](~/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview.png)
+![Egress by FQDN and Hostname](~/assets/images/gateway/Gateway-Egress-FQDN-Policy-preview.png)
 
 This will help apply egress IPs to your users' traffic when an upstream application or network requires it, while the rest of their traffic can take the most performant egress path.