[Docs] Update geolocation references (cloudflare#22548)

Author: pedrosousa

src/content/docs/client-ip-geolocation/about/index.mdx

@@ -38,7 +38,7 @@ Because our cell list includes Designated Market Areas in the United States, you
 
 ## Example scenario
 
-Jane is a Cloudflare WARP user in Glendive, Montana, USA. She is interested in the privacy benefits of using a VPN. Her client IP address is `108.59.112.0`, which is owned by [Mid-Rivers Telephone Cooperative](https://bgp.he.net/AS11961) and geolocates to 47.0984,-104.7275 (with a location accuracy of 50km using MaxMind’s GeoIP service).
+Jane is a Cloudflare WARP user in Glendive, Montana, USA. She is interested in the privacy benefits of using a VPN. Her client IP address is `108.59.112.0`, which is owned by [Mid-Rivers Telephone Cooperative](https://bgp.he.net/AS11961) and geolocates to 47.0984,-104.7275, approximately.
 
 ![Diagram of how Cloudflare reports accurate location information over VPN](~/assets/images/client-ip-geolocation/client-ip-geolocation-example.png)
 

src/content/docs/cloudflare-one/insights/dex/tests/traceroute.mdx

@@ -53,7 +53,7 @@ A traceroute test measures the following data:
 | Number of hops  | Number of routers encountered between the device and the target.                                                                                                                                                                                                                                                                                                                                                                                                                                       |
 | Packet loss     | Percentage of IP packets that failed to receive a response.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
 | Availability    | Percentage of tests where at least one packet reached the destination.                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| Last seen ISP   | The Internet Service Provider that is managing the connection from the device to Cloudflare. (Only available on macOS and Windows.) <br/> <br/> DEX looks up the IP address of the ISP in the [MaxMind GeoIP2 database](https://www.maxmind.com/en/geoip2-services-and-databases) and returns the corresponding [ASO and ASN](https://www.cloudflare.com/learning/network-layer/what-is-an-autonomous-system/). If the ASO and ASN are `Unknown`, it means this information is unavailable in MaxMind. |
+| Last seen ISP   | The Internet Service Provider that is managing the connection from the device to Cloudflare. (Only available on macOS and Windows.) <br/> <br/> DEX looks up the IP address of the ISP in a geolocation database and returns the corresponding [ASO and ASN](https://www.cloudflare.com/learning/network-layer/what-is-an-autonomous-system/). If the ASO and ASN are `Unknown`, it means this information is unavailable in the geolocation data provider. |
 
 ## Related resources
 

src/content/docs/load-balancing/understand-basics/traffic-steering/steering-policies/index.mdx

@@ -21,7 +21,7 @@ import { DirectoryListing, GlossaryTooltip, Render } from "~/components"
 
 Customers can configure their load balancer using the `location_strategy` parameter, which includes the properties `prefer_ecs` and `mode`.
 
-`prefer_ecs` determines whether the ECS GeoIP should be preferred as the authoritative location.
+`prefer_ecs` determines whether the ECS geolocation should be preferred as the authoritative location.
 
 | Type          | Description                                                                             |
 | ------------- | --------------------------------------------------------------------------------------- |
@@ -30,17 +30,15 @@ Customers can configure their load balancer using the `location_strategy` parame
 | `"proximity"` | Prefers ECS only when `steering_policy="proximity"`.                                    |
 | `"geo"`       | Prefers ECS only when `steering_policy="geo"` and only supports country-level steering. |
 
-`mode` determines the authoritative location when ECS is not preferred, does not exist in the request, or its GeoIP lookup is unsuccessful.
+`mode` determines the authoritative location when ECS is not preferred, does not exist in the request, or its geolocation lookup is unsuccessful.
 
-| Type            | Description                                                                                                     |
-| --------------- | --------------------------------------------------------------------------------------------------------------- |
-| `"pop"`         | Uses the Cloudflare PoP location.                                                                               |
-| `"resolver_ip"` | Uses the DNS resolver GeoIP location. If the GeoIP lookup is unsuccessful, it uses the Cloudflare PoP location. |
+| Type            | Description                                                                                                             |
+| --------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `"pop"`         | Uses the Cloudflare PoP location.                                                                                       |
+| `"resolver_ip"` | Uses the DNS resolver geolocation data. If the geolocation lookup is unsuccessful, it uses the Cloudflare PoP location. |
 
 :::note
 
-
 ECS support applies to DNS-only load balancers.
 
-
 :::

src/content/docs/magic-firewall/best-practices/minimal-ruleset.mdx

@@ -70,6 +70,6 @@ The list below is a common list of traffic types you should also consider blocki
 * HTTP and HTTPS
   * If you only have servers on your Magic Transit prefixes, consider blocking ingress traffic on TCP source ports 80 and 443 from outside. If you have endpoints on your Magic Transit prefixes, you can allow traffic on the source ports but consider creating a disabled rule you can activate to respond to reflection attacks as needed.
 
-If relevant to your environment, consider blocking based on GeoIP, which blocks traffic based on the country or user when an end user's IP address is registered in the GeoIP database.
+If relevant to your environment, consider blocking based on geolocation data, which blocks traffic based on the country or user when an end user's IP address is registered in the geolocation database.
 
 If you are interested in participating in the beta for [Session Initiation Protocol (SIP) Validation](https://blog.cloudflare.com/programmable-packet-filtering-with-magic-firewall/), contact your Implementation Manager.

src/content/docs/magic-firewall/how-to/add-rules.mdx

@@ -100,7 +100,7 @@ curl https://api.cloudflare.com/client/v4/accounts/{account_id}/rulesets \
   "rules": [
     {
       "action": "block",
-      "expression": "ip.geoip.country == \"BR\"",
+      "expression": "ip.src.country == \"BR\"",
       "description": "Block traffic from Brazil"
     }
   ]

src/content/docs/network/ip-geolocation.mdx

@@ -8,7 +8,7 @@ import { FeatureTable, TabItem, Tabs } from "~/components";
 
 IP geolocation adds the [`CF-IPCountry` header](/fundamentals/reference/http-headers/#cf-ipcountry) to all requests to your origin server.
 
-Cloudflare automatically updates its IP geolocation database using MaxMind and other data sources, typically twice a week.
+Cloudflare automatically updates its IP geolocation database from several data sources, typically twice a week.
 
 ## Availability
 
@@ -25,8 +25,8 @@ If you only want the request header for the visitor's country, you can enable **
 To enable **IP Geolocation** in the dashboard:
 
 1. Log in to your [Cloudflare account](https://dash.cloudflare.com) and go to a specific domain.
-2. Go to **Network**.
-3. For **IP Geolocation**, switch the toggle to **On**.
+2. Go to **Network**.
+3. For **IP Geolocation**, switch the toggle to **On**.
 
 </TabItem> <TabItem label="API">
 
@@ -46,5 +46,5 @@ In order to use this data, you will need to then retrieve it from the [`CF-IPCou
 
 If you find an incorrect IP location, consider the following:
 
-- If the IP is part of the [current Cloudflare IP ranges](https://www.cloudflare.com/ips/), report to `geoip@cloudflare.com`.
+- If the IP is part of the [current Cloudflare IP ranges](https://www.cloudflare.com/ips/), report to `ip-corrections@cloudflare.com`.
 - If the IP is **not** listed within the [current Cloudflare IP ranges](https://www.cloudflare.com/ips/), [report to MaxMind](https://www.maxmind.com/en/geoip-data-correction-request).

src/content/docs/radar/investigate/url-scanner.mdx

@@ -106,7 +106,7 @@ Some examples of more specific properties include:
 * `meta.processors.radarRank` - [Cloudflare Radar Rank](http://blog.cloudflare.com/radar-domain-rankings/) of the main hostname contacted.
 * `meta.processors.wappa` - The kind of technologies detected as being in use by the website, with the help of [Wappalyzer](https://github.com/Lissy93/wapalyzer).
 * `page.url` - URL of the primary request, after all HTTP redirects.
-* `page.country` - GeoIP country name of the main IP address contacted.
+* `page.country` - Country name from geolocation data associated with the main IP address contacted.
 * `page.history` - Main page history, including any HTTP redirects.
 * `page.screenshot` - Various hashes of the main screenshot. Can be used to search for sites with similar screenshots.
 * `page.domStructHash` - HTML structure hash. Use it to search for sites with similar structure.

src/content/docs/reference-architecture/architectures/load-balancing.mdx

@@ -315,7 +315,7 @@ Proximity steering is a traffic steering algorithm available to enterprise plan
 Cloudflare determines the requester’s physical location using the following methods, in this order:
 
 1. [EDNS Client Subnet](https://developers.google.com/speed/public-dns/docs/ecs) information, if provided in the DNS request
-2. GeoIP information of the resolver used to reach Cloudflare
+2. Geolocation information of the resolver used to reach Cloudflare
 3. GPS location of the Cloudflare data center handling the request
 
 Proximity steering requires providing GPS coordinates for all endpoint pools, allowing Cloudflare to calculate the closest endpoint pool based on the requesting IP, DNS resolver, or Cloudflare data center.