[CF One] Rename "WARP ingress IP" heading to "Cloudflare One Client ingress IP" - #32437
[CF One] Rename "WARP ingress IP" heading to "Cloudflare One Client ingress IP"#32437cf-rhett wants to merge 1 commit into
Conversation
github-actions
Bot
assigned
csujedihy,
elithrar,
jiulingz,
lpraneis,
alpdot,
jeffh-cloudflare and
steve-cloudflare
Review
Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. Conventions❌ This review could not complete this run; results may be incomplete. It will retry on the next push. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
|
Skipping SG-170db579f45f. The link at |
|
/rebase |
dd5d452 to
ec18edb
Compare
|
Hey there, we've marked this pull request as stale because there's no recent activity on it. This label helps us identify PRs that might need updates (or to be closed out by our team if no longer relevant). |
|
/rebase |
…ngress IP" The old heading read as though the section covered the consumer WARP client, when it actually documents the ingress IPs and UDP ports used by the Cloudflare One Client. The new wording matches the phrasing already used on the switch organizations page. Keep the #warp-ingress-ip anchor via an explicit heading ID. This section is widely deep-linked from support material, and URL fragments cannot be redirected.
ec18edb to
262838a
Compare
8 participants
Summary
The WARP ingress IP heading on the Cloudflare One Client firewall page reads as though the section covers the consumer WARP client, but it documents the ingress IPs and UDP ports used by the Cloudflare One Client. Renamed it to Cloudflare One Client ingress IP, which also matches the phrasing already used on the switch organizations page.
The
#warp-ingress-ipanchor is deliberately preserved via an explicit heading ID (## Cloudflare One Client ingress IP {/* warp-ingress-ip */}). This is the section customers are pointed at to build firewall allowlists, so it is widely deep-linked from support material and internal runbooks, and URL fragments cannot be redirected. All eight inbound links keep working untouched.Link text was updated in the same pass. On the firewall page itself the surrounding sentence already names the client, so those read just "ingress IPs" rather than repeating the product name; off-page references (a table cell in the diagnostic logs page, a troubleshooting step, and the Cloudflare WAN partial) use the full name since they have no surrounding context.
Documentation checklist