[API Shield] Hyperlint Automation: Broken Link Fixes (#20085)

* Fix issue: WorkspaceTaskSubType.BROKEN_LINK
* Add period

---------

Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com>
Co-authored-by: Pedro Sousa <[email protected]>

Author: hyperlint-ai[bot]

src/content/docs/api-shield/security/volumetric-abuse-detection.mdx

@@ -27,9 +27,9 @@ Volumetric Abuse Detection rate limits are a way to prevent blatant volumetric a
 
 Volumetric Abuse Detection analyzes your API’s individual session traffic statistics to recommend per-endpoint, per-session rate limits.
 
-Volumetric Abuse Detection currently requires a <GlossaryTooltip term="session identifier" link="/api-shield/get-started/#set-up-session-identifiers">session identifier</GlossaryTooltip>, like an authorization token available as a request header or cookie.
+Volumetric Abuse Detection currently requires a <GlossaryTooltip term="session identifier" link="/api-shield/get-started/#to-set-up-session-identifiers">session identifier</GlossaryTooltip>, like an authorization token available as a request header or cookie.
 
-After adding a session identifier, allow 24 hours for rate limit recommendations to appear on endpoints in **Security** > **API Shield** > **Endpoint Management** on the Cloudflare dashboard. Recommendations will continue to update if your traffic pattern changes
+After adding a session identifier, allow 24 hours for rate limit recommendations to appear on endpoints in **Security** > **API Shield** > **Endpoint Management** on the Cloudflare dashboard. Recommendations will continue to update if your traffic pattern changes.
 
 ### Observe rate limits