Simplify shields.io content into a note on the JSON endpoint

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: zentron

src/pages/docs/projects/badges.md

@@ -65,7 +65,7 @@ GET /api/{spaceId}/projects/{projectSlug}/badge/{environmentSlug}/latest_release
 
 ### JSON endpoint
 
-Returns badge data as JSON, useful for integrations with third-party badge services:
+Returns badge data as JSON. You can use this endpoint to externalize badge rendering through third-party services like [shields.io](https://shields.io), which offloads requests from your Octopus Server.
 
 ```
 GET /api/{spaceId}/projects/{projectSlug}/badge/{environmentSlug}/latest_release.json
@@ -80,21 +80,6 @@ GET /api/{spaceId}/projects/{projectSlug}/badge/{environmentSlug}/latest_release
 | `includeFailed` | `false` | Include failed, canceled, or timed-out releases |
 | `tenantId` | | Filter by a specific tenant for multi-tenant deployments |
 
-## Use badges with shields.io
-
-You can use the JSON endpoint with [shields.io Dynamic JSON Badge](https://shields.io/badges/dynamic-json-badge) to serve badges through shields.io's infrastructure. This offloads requests from your Octopus Server, as shields.io has its own caching layer.
-
-To create a shields.io badge:
-
-1. Open the badge builder and copy the **URL** for the JSON endpoint (ending in `.json`).
-2. URL-encode the endpoint and use it as the `url` parameter for a shields.io dynamic badge.
-
-For example:
-
-```
-https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fyour-octopus.example.com%2Fapi%2FSpaces-1%2Fprojects%2Fmy-project%2Fbadge%2Fproduction%2Flatest_release.json&query=%24.Message&label=Production
-```
-
 ## Caching
 
-Badge responses include HTTP caching headers to reduce load on your Octopus Server. External consumers like shields.io also maintain their own caches. This means badge updates may not appear instantly after a deployment completes.
+Badge responses include HTTP caching headers to reduce load on your Octopus Server. This means badge updates may not appear instantly after a deployment completes.