Clarify that RUM geo.* attributes are derived from client IP, not device GPS (#36213)

* Clarify that RUM geo.* attributes are resolved from client IP, not device GPS

* Update layouts/shortcodes/mdoc/en/sdk/data_collected/android.mdoc.md

Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com>

* Update layouts/shortcodes/mdoc/en/sdk/data_collected/ios.mdoc.md

Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com>

---------

Co-authored-by: Ida Adjivon <65119712+iadjivon@users.noreply.github.com>

Author: yuandesu

layouts/shortcodes/mdoc/en/sdk/data_collected/android.mdoc.md

@@ -87,7 +87,9 @@ The following OS-related attributes are attached automatically to all events col
 
 ### Geolocation
 
-The following attributes are related to the geolocation of IP addresses.
+The following attributes are related to the geolocation of IP addresses. Datadog resolves these attributes server-side from the client IP address on the intake connection. The SDK does not access the device's GPS or OS location.
+
+**Note**: On mobile networks, the IP address resolves to the carrier's gateway rather than the device's physical location.
 
 **Note:** If you want to stop collecting geolocation attributes, change the setting in your [application details][9].
 

layouts/shortcodes/mdoc/en/sdk/data_collected/ios.mdoc.md

@@ -92,7 +92,9 @@ The following OS-related attributes are attached automatically to all events col
 
 ### Geolocation
 
-The following attributes are related to the geolocation of IP addresses.
+The following attributes are related to the geolocation of IP addresses. Datadog resolves these attributes server-side from the client IP address on the intake connection. The SDK does not access the device's GPS or OS location.
+
+**Note**: On mobile networks, the IP address resolves to the carrier's gateway rather than the device's physical location.
 
 **Note:** If you want to stop collecting geolocation attributes, change the setting in your [application details][8].