Remove .proxy/

Author: anthonydiscord

docs/activities/building-an-activity.mdx

@@ -457,10 +457,6 @@ We can now run our server and client-side apps in separate terminal windows. You
 
 Before we call your backend activity server, we need to be aware of the Discord proxy and understand how to avoid any Content Security Policy (CSP) issues.
 
-:::info
-For this tutorial, we are going to prefix the API call to `/api/token/` with `/.proxy`, but you can also use the SDK's `patchUrlMappings()` method to automatically prefix calls to your external resources for the proxy.
-:::
-
 Learn more about this topic in the guides for [Constructing a Full URL](/docs/activities/development-guides/networking#construct-a-full-url) and [Using External Resources](/docs/activities/development-guides/networking#using-external-resources).
 
 ### Calling your backend server from your client
@@ -513,10 +509,7 @@ async function setupDiscordSdk() {
   });
 
   // Retrieve an access_token from your activity's server
-  // Note: We need to prefix our backend `/api/token` route with `/.proxy` to stay compliant with the CSP.
-  // Read more about constructing a full URL and using external resources at
-  // https://discord.com/developers/docs/activities/development-guides/networking#construct-a-full-url
-  const response = await fetch("/.proxy/api/token", {
+  const response = await fetch("/api/token", {
     method: "POST",
     headers: {
       "Content-Type": "application/json",

docs/activities/development-guides/networking.mdx

@@ -29,8 +29,7 @@ There are scenarios where instead of using a relative url (`/path/to/my/thing`)
 1. The protocol you wish to use
 2. Your application's client id
 3. The discord proxy domain
-4. The `/.proxy` path prefix
-5. Whatever you need to list
+4. Whatever you need to list
 
 Here's an example of how to build a full url, using the URL constructor:
 
@@ -39,13 +38,13 @@ const protocol = `https`;
 const clientId = '<YOUR CLIENT ID>';
 const proxyDomain = 'discordsays.com';
 const resourcePath = '/foo/bar.jpg';
-const url = new URL(`${protocol}://${clientId}.${proxyDomain}/.proxy${resourcePath}`);
+const url = new URL(`${protocol}://${clientId}.${proxyDomain}${resourcePath}`);
 ```
 
 In other words, given an application client id of `12345678`
 | Relative Path | Full Path                                           |
 |---------------|-----------------------------------------------------|
-| /foo/bar.jpg  | https://12345678.discordsays.com/.proxy/foo/bar.jpg |
+| /foo/bar.jpg  | https://12345678.discordsays.com/foo/bar.jpg |
 
 ---
 

docs/activities/how-activities-work.md

@@ -41,7 +41,7 @@ async function setup() {
   });
 
   // Retrieve an access_token from your application's server
-  const response = await fetch('/.proxy/api/token', {
+  const response = await fetch('/api/token', {
     method: 'POST',
     headers: {
       'Content-Type': 'application/json',