diff --git a/modules/configuring-firewall.adoc b/modules/configuring-firewall.adoc
index e3236c5aa709..b5760b5ae1dd 100644
--- a/modules/configuring-firewall.adoc
+++ b/modules/configuring-firewall.adoc
@@ -83,7 +83,7 @@ If your environment has a dedicated load balancer in front of your {product-titl
 |The `https://console.redhat.com` site uses authentication from `sso.redhat.com`
 |===
 +
-* You can use the wildcards `\*.quay.io` and `*.openshiftapps.com` instead of `cdn.quay.io` and `cdn0[1-6].quay.io` in your allowlist.
+* You can use the wildcard `*.quay.io` instead of `cdn.quay.io` and `cdn0[1-6].quay.io` in your allowlist.
 * You can use the wildcard `*.access.redhat.com` to simplify the configuration and ensure that all subdomains, including `registry.access.redhat.com`, are allowed.
 * When you add a site, such as `quay.io`, to your allowlist, do not add a wildcard entry, such as `*.quay.io`, to your denylist. In most cases, image registries use a content delivery network (CDN) to serve images. If a firewall blocks access, image downloads are denied when the initial download request redirects to a hostname such as `cdn01.quay.io`.