Skip to content

Conversation

@omer-cloudflare
Copy link
Contributor

Made a substantial update to the "Source country or location" and "Target country or location" sections — adding more details and clarity.

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

Made a substantial update to the "Source country or location" and "Target country or location" sections — adding more details and clarity.
@andre-j3sus
Copy link
Contributor

@omer-cloudflare Instead of using 'country or location'. what do you think about using just the word 'location'?

@omer-cloudflare
Copy link
Contributor Author

In the most recent report that we published (https://blog.cloudflare.com/ddos-threat-report-for-2025-q2/), we refer to it as

  • "Top sources of DDoS attacks"
  • "Top attacked locations"

so perhaps in the section titles we can just use location as you suggested. But in the description, I think that referring to country and location is fine and provides more details/context. WDYT?

@andre-j3sus
Copy link
Contributor

In the most recent report that we published (https://blog.cloudflare.com/ddos-threat-report-for-2025-q2/), we refer to it as

  • "Top sources of DDoS attacks"
  • "Top attacked locations"

so perhaps in the section titles we can just use location as you suggested. But in the description, I think that referring to country and location is fine and provides more details/context. WDYT?

Yes, I agree with changing the titles and keeping the text as is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants