Update changelog

Author: anthonydiscord

docs/change-log/2024-07-17-activities-proxy-csp-update.md

@@ -2,6 +2,9 @@
 title: "Activities Proxy CSP Update"
 date: "2024-07-17"
 breaking: true
+topics:
+- "Activities"
+- "Embedded App SDK"
 ---
 
 :::warn

docs/change-log/2025-07-30-remove-proxy-from-discord-activity-proxy-path.md

@@ -6,46 +6,40 @@ topics:
 - "Embedded App SDK"
 ---
 
-## Overview
-
 We've updated the Content Security Policy (CSP) for Discord Activities to remove the `.proxy/` path requirement when making requests through the discordsays.com proxy. This change simplifies the developer experience while maintaining full backwards compatibility. This was made possible by resolving the underlying privacy considerations that originally required the `.proxy/` path restriction.
 
-## What Changed
-
-### Before
+#### Before
 
 Activities were required to make proxy requests through paths prefixed with `/.proxy/`:
 
 ```
 https://<app_id>.discordsays.com/.proxy/api/endpoint
 ```
 
-### After
+#### After
 
-Activities can now make proxy requests directly without the `.proxy/` prefix:
+Activities can now make proxy requests directly without the `/.proxy/` prefix:
 
 ```
 https://<app_id>.discordsays.com/api/endpoint
 ```
 
-## Technical Details
+#### Technical Details
 
 - **CSP Update**: The Content Security Policy now allows requests to `https://<app_id>.discordsays.com/*` instead of the more restrictive `https://<app_id>.discordsays.com/.proxy/*`
 - **Proxy Behavior**: Both URL patterns work identically - your existing proxy mappings (e.g., `/api -> example.com`) will function the same way regardless of whether you use `/.proxy/api` or `/api`
 - **Performance**: No performance differences between the two approaches
 
-## Developer Tooling Updates
+#### Developer Tooling Updates
 
 The `patchUrlMappings` utility will be updated in an upcoming Embedded App SDK release to generate the simplified URLs by default, though it will continue to support the `.proxy/` format for backward compatibility.
 
-## Backward Compatibility
+#### Backward Compatibility
 
-**All existing code will continue to work without changes.** The `.proxy/` path prefix is still fully supported and will be maintained indefinitely. You can:
+**All existing code will continue to work without changes.** The `/.proxy/` path prefix is still fully supported and will be maintained indefinitely. You can:
 
-- Continue using existing `.proxy/` URLs
+- Continue using existing `/.proxy/` URLs
 - Switch to the new, simplified URLs
 - Use both patterns simultaneously in the same application
 
-## Migration
-
 **No migration is required.** This is a purely additive change that expands what's possible rather than breaking existing functionality.