refactor: rename proxy cli to tunnel

Author: charIeszhao

docs/docs/references/using-cli/custom-ui-local-proxy.mdx renamed to docs/docs/references/using-cli/tunnel.mdx

@@ -4,7 +4,7 @@ import Tabs from '@theme/Tabs';
 
 # Set up a local tunnel for custom UI development
 
-<Availability cloud oss={{ major: 1, minor: 19 }} />
+<Availability cloud oss={{ major: 1, minor: 20 }} />
 
 For Logto Cloud users, We've made it easy to let you "Bring your own UI" to Logto. Cloud users can now upload a zip file containing the custom UI assets in Logto Console -> Sign-in experience -> Custom UI. (Check out the [Bring your UI](/docs/recipes/customize-sie/bring-your-ui) page for more details.)
 
@@ -34,19 +34,19 @@ sequenceDiagram
 ```
 
 But now since you are developing your own custom sign-in UI, you need a way to navigate to the custom sign-in UI pages running on your local machine instead.
-This requires a local proxy to intercept the outgoing requests from your application and redirect them to your custom sign-in UI pages.
+This requires a local tunnel service to intercept the outgoing requests from your application and redirect them to your custom sign-in UI pages.
 
 Additionally, you need to interact with Logto's experience API to authenticate users and manage sessions.
-This proxy will also help forward these experience API requests to Logto Cloud in order to avoid CORS issues.
+This service will also help forward these experience API requests to Logto Cloud in order to avoid CORS issues.
 
-The sequence diagram below illustrates how a successful "sign-in" flow works with your custom UI and the proxy in place:
+The sequence diagram below illustrates how a successful "sign-in" flow works with your custom UI and the tunnel service in place:
 
 ```mermaid
 sequenceDiagram
     box Local machine
     participant A as Your application
     participant B as Your custom sign-in UI
-    participant C as proxy
+    participant C as Tunnel
     end
     box Logto Cloud
     participant D as Logto Cloud auth endpoint
@@ -63,7 +63,7 @@ sequenceDiagram
     A --> A: Handle the sign-in callback and<br/>the user is now authenticated
 ```
 
-With the proxy in place, you can now develop and test your custom sign-in UI locally, without needing to upload the assets to Logto Cloud every time you make a change.
+With the tunnel service in place, you can now develop and test your custom sign-in UI locally, without needing to upload the assets to Logto Cloud every time you make a change.
 
 ## Instructions
 
@@ -78,14 +78,14 @@ Then you can execute the command this way:
   <TabItem value="cli" label="CLI">
 
 ```bash
-logto proxy -p 9000 --experience-uri http://localhost:4000/ --endpoint https://foobar.logto.app/
+logto tunnel -p 9000 --experience-uri http://localhost:4000/ --endpoint https://foobar.logto.app/
 ```
 
   </TabItem>
   <TabItem value="npx" label="npx">
 
 ```bash
-npx @logto/cli proxy -p 9000 --experience-uri http://localhost:4000/ --endpoint https://foobar.logto.app/
+npx @logto/cli tunnel -p 9000 --experience-uri http://localhost:4000/ --endpoint https://foobar.logto.app/
 ```
 
   </TabItem>
@@ -99,14 +99,14 @@ It also works if you have custom domain configured in Logto:
   <TabItem value="cli" label="CLI">
 
 ```bash
-logto proxy -p 9000 --experience-uri http://localhost:4000/ --endpoint https://your.custom.domain/
+logto tunnel -p 9000 --experience-uri http://localhost:4000/ --endpoint https://your.custom.domain/
 ```
 
   </TabItem>
   <TabItem value="npx" label="npx">
 
 ```bash
-npx @logto/cli proxy -p 9000 --experience-uri http://localhost:4000/ --endpoint https://your.custom.domain/
+npx @logto/cli tunnel -p 9000 --experience-uri http://localhost:4000/ --endpoint https://your.custom.domain/
 ```
 
   </TabItem>
@@ -120,14 +120,14 @@ Alternatively, the command also supports static html assets without needing to r
   <TabItem value="cli" label="CLI">
 
 ```bash
-logto proxy -p 9000 --experience-path /path/to/your/static/files --endpoint https://foobar.logto.app/
+logto tunnel -p 9000 --experience-path /path/to/your/static/files --endpoint https://foobar.logto.app/
 ```
 
   </TabItem>
   <TabItem value="npx" label="npx">
 
 ```bash
-npx @logto/cli proxy -p 9000 --experience-path /path/to/your/static/files --endpoint https://foobar.logto.app/
+npx @logto/cli tunnel -p 9000 --experience-path /path/to/your/static/files --endpoint https://foobar.logto.app/
 ```
 
   </TabItem>
@@ -136,7 +136,7 @@ npx @logto/cli proxy -p 9000 --experience-path /path/to/your/static/files --endp
 
 ### Step 2: Update endpoint URI in your application
 
-Finally, run your application and set its Logto endpoint to the proxy address `http://localhost:9000/` instead.
+Finally, run your application and set its Logto endpoint to the tunnel service address `http://localhost:9000/` instead.
 
 Let's take a React application as an example:
 
@@ -145,7 +145,7 @@ import { LogtoProvider, LogtoConfig } from '@logto/react';
 
 const config: LogtoConfig = {
   // endpoint: 'https://foobar.logto.app/', // original Logto Cloud endpoint
-  endpoint: 'http://localhost:9000/', // proxy address
+  endpoint: 'http://localhost:9000/', // tunnel service address
   appId: '<your-application-id>',
 };