Added link and minor copy edits

Author: patriciasantaana

src/content/changelog/api-shield/2025-03-18-api-posture-management.mdx

@@ -16,15 +16,15 @@ View these risks in [Endpoint Management](https://developers.cloudflare.com/api-
 
 API Shield will scan for risks on your API inventory daily. Here are the new risks we're scanning for and automatically labelling:
 
-- **cf-risk-sensitive**: applied if the customer is subscribed to the sensitive data detection ruleset and the WAF detects sensitive data returned on an endpoint in the last 7 days.
+- **cf-risk-sensitive**: applied if the customer is subscribed to the [sensitive data detection ruleset](/waf/managed-rules/reference/sensitive-data-detection/) and the WAF detects sensitive data returned on an endpoint in the last seven days.
 - **cf-risk-missing-auth**: applied if the customer has configured a session ID and no successful requests to the endpoint contain the session ID. 
 - **cf-risk-mixed-auth**: applied if the customer has configured a session ID and some successful requests to the endpoint contain the session ID while some lack the session ID.
 - **cf-risk-missing-schema**: added when a learned schema is available for an endpoint that has no active schema.
 - **cf-risk-error-anomaly**: added when an endpoint experiences a recent increase in response errors over the last 24 hours.
 - **cf-risk-latency-anomaly**: added when an endpoint experiences a recent increase in response latency over the last 24 hours.
 - **cf-risk-size-anomaly**: added when an endpoint experiences a spike in response body size over the last 24 hours.
 
-In addition, API Shield has two new 'beta' scans for **Broken Object Level Authorization (BOLA) attacks**. If you're in the beta, you'll see the following two labels when API Shield suspects an endpoint is suffering from a BOLA vulnerability:
+In addition, API Shield has two new 'beta' scans for **Broken Object Level Authorization (BOLA) attacks**. If you're in the beta, you will see the following two labels when API Shield suspects an endpoint is suffering from a BOLA vulnerability:
 
  - **cf-risk-bola-enumeration**: added when an endpoint experiences successful responses with drastic differences in the number of unique elements requested by different user sessions.
  - **cf-risk-bola-pollution**: added when an endpoint experiences successful responses where parameters are found in multiple places in the request.