copy reflects client apis have been updated

Author: Andra Mircioiu

content/geoip/release-notes/2025.md

@@ -19,7 +19,7 @@ The IP risk snapshot is based on an analysis of historical risk on the IP addres
 
 minFraud customers may find the IP risk snapshot output useful to determine whether an IP address is risky based on historical activity versus a current, emerging issue. A lower `traits/ip_risk_snapshot` score combined with a higher minFraud `ip_address/risk` score would mean that the IP address is becoming risky in real time based on the traffic on your and other customers' networks. A high score in both `ip_risk_snapshot` and minFraud IP risk score would mean that the IP address has been risky for a longer time.
 
-We plan to update the client APIs soon to reflect this change. 
+Client APIs have been updated to reflect this change. 
 
 {{</ release-note >}}
 
@@ -29,15 +29,15 @@ We have added an [`anonymizer` object](https://dev.maxmind.com/geoip/docs/web-se
 
 Anonymizer data in the `traits` object is being marked as deprecated. However, for backwards compatibility, anonymizer data in the `traits` object will continue to be populated and the functionality remains the same. This will not be a breaking change. 
 
-When the client APIs for the web services are upgraded, we recommend updating your integrations to use the new `anonymizer` object, which contains data points not found in the `traits` object:
+We recommend updating your integrations to use the new `anonymizer` object, which contains data points not found in the `traits` object:
 
 | new data | description |
 | -------------------------------- | -------------------------------- |
 | `anonymizer/confidence`                       | A score ranging from 1 to 99 that represents our percent confidence that the network is currently part of an actively used VPN service.| 
 | `anonymizer/network_last_seen`                | The last day that the network was sighted in our analysis of anonymized networks. This is in the ISO 8601 date format (YYYY-MM-DD). |
 |  `anonymizer/provider_name`                  | The name of the VPN provider (e.g., NordVPN, SurfShark, etc.) associated with the network. |
 
-We plan to update the client APIs soon to reflect this change, which applies to the following web services: 
+Client APIs have been updated to reflect this change, which applies to the following web services: 
 - GeoIP Insights
 - minFraud Insights
 - minFraud Factors 

content/minfraud/release-notes/2025.md

@@ -19,27 +19,25 @@ The IP risk snapshot is based on an analysis of historical risk on the IP addres
 
 minFraud customers may find the IP risk snapshot output useful to determine whether an IP address is risky based on historical activity versus a current, emerging issue. A lower `traits/ip_risk_snapshot` score combined with a higher minFraud `ip_address/risk` score would mean that the IP address is becoming risky in real time based on the traffic on your and other customers' networks. A high score in both `ip_risk_snapshot` and minFraud IP risk score would mean that the IP address has been risky for a longer time.
 
-We plan to update the client APIs soon to reflect this change. 
+Client APIs have been updated to reflect this change. 
 
 {{</ release-note >}}
 
-
-
 {{< release-note date="2025-11-19" title="New anonymizer data added to web services">}}
 
 We have added an [`anonymizer` object](https://dev.maxmind.com/geoip/docs/web-services/responses/#anonymizer) to our web services. This object contains the anonymizer data previously found in the `traits` object together with new outputs.
 
 Anonymizer data in the `traits` object is being marked as deprecated. However, for backwards compatibility, anonymizer data in the `traits` object will continue to be populated and the functionality remains the same. This will not be a breaking change. 
 
-When the client APIs for the web services are upgraded, we recommend updating your integrations to use the new `anonymizer` object, which contains data points not found in the `traits` object:
+We recommend updating your integrations to use the new `anonymizer` object, which contains data points not found in the `traits` object:
 
 | new data | description |
 | -------------------------------- | -------------------------------- |
 | `anonymizer/confidence`                       | A score ranging from 1 to 99 that represents our percent confidence that the network is currently part of an actively used VPN service.| 
 | `anonymizer/network_last_seen`                | The last day that the network was sighted in our analysis of anonymized networks. This is in the ISO 8601 date format (YYYY-MM-DD). |
 |  `anonymizer/provider_name`                  | The name of the VPN provider (e.g., NordVPN, SurfShark, etc.) associated with the network. |
 
-We plan to update the client APIs soon to reflect this change, which applies to the following web services: 
+Client APIs have been updated to reflect this change, which applies to the following web services: 
 
 - minFraud Insights
 - minFraud Factors