edgeone 1.1.4 → 1.1.7

package/README.md

@@ -66,9 +66,9 @@ After completing initialization, enter the local development stage:
 edgeone pages dev
 ```
 
-Executing the command will start a service on the local port 8088 by default. The Pages Functions service and the Pages project run on the same port.
+The run command by default creates a service locally on port 8088. Both the Pages Function service and the Pages project service run on the same port, with no need for additional proxying.
 
-Visit the frontend at `http://localhost:8088/`, and call your functions directly using their file paths under `edge-functions` or `node-functions`.
+You can access the front-end page via `http://localhost:8088/`. In the front-end project, use the Fetch API directly, where the access path is the path of function files in folder `edge-functions` or `node-functions`.
 
 ```javascript
 // ./node-functions/api/my-functions.js
@@ -94,7 +94,7 @@ If you need to link a project that does not exist, you can also create a new pro
 
 ### 6. Deploy
 
-If your project is created via "direct upload", you can also deploy it directly to the Pages platform locally by executing the following command:
+Build locally and deploy to EdgeOne Pages. If you need to link an existing project, it must be of the direct upload type.
 
 ```plaintext
 edgeone pages deploy [<directoryOrZip>] [-n <projectName>] [-e <env>]
@@ -107,8 +107,8 @@ edgeone pages deploy [<directoryOrZip>] [-n <projectName>] [-e <env>]
 - `-e, --env`: Environment to deploy to, choices: 'production' or 'preview' (default: 'production')
 
 Note:
-- By default, when executing deploy, the CLI will automatically build and package frontend code, `node-functions`, and `edge-functions` into the `.edgeone` folder and deploy to Pages.
-- If you choose to manually build the project, you need to copy the related folders of Pages Functions and the project's `package.json` file to dist (suppose the output directory is dist) after building, then rerun `edgeone pages deploy ./dist`.
+- When you execute the deploy command, the CLI will automatically build and deploy your project.
+- If you build manually, you need to place the Pages Functions related folders and `package.json` into the output directory (such as `dist`), and then run `edgeone pages deploy ./dist`.
 
 #### Usage Examples
 
@@ -154,8 +154,8 @@ edgeone pages deploy [<directoryOrZip>] -n <projectName> -t <token> [-e <env>]
 - `-t, --token`: API Token for CI/CD pipelines (required for automated deployments)
 
 Note:
-- By default, when executing deploy, the CLI will automatically build and package frontend code, `node-functions`, and `edge-functions` into the `.edgeone` folder and deploy to Pages.
-- If you choose to manually build the project, you need to copy the related folders of Pages Functions and the project's `package.json` file to dist (suppose the output directory is dist) after building, then rerun `edgeone pages deploy ./dist`.
+- By default, when executing deploy, the CLI automatically builds and packages frontend code, `node-functions`, and `edge-functions` into the `.edgeone` folder and deploy to Pages.
+- If you choose to build the project manually, you need to manually copy the Pages Functions related folder and `package.json` to dist (suppose the output directory is dist), then rerun `edgeone pages deploy ./dist`.
 
 #### CI/CD Pipeline Examples
 
@@ -191,4 +191,4 @@ _To access the China site documentation, please click [here](https://edgeone.clo
 
 ## Contact
 
-If you need technical support, please [contact us](https://edgeone.ai/contact?source=edgeone-cli).
+If you need technical support, please [contact us](https://pages.edgeone.ai/contact?source=edgeone-cli).