Review

Author: Yiyun333

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/creating-your-first-script.md

@@ -45,15 +45,15 @@ After setting up all the prerequisites, you can start writing a first script tha
     main().catch(console.error);
     ```
 
-Don't forget to [set up your personal access token](/apidocs-mxsdk/mxsdk/set-up-your-pat/) before executing the script.
+Do not forget to [set up your personal access token](/apidocs-mxsdk/mxsdk/set-up-your-pat/) before executing the script.
 
 {{% alert color="warning" %}}
 Working copy creation is a resource-intensive process. Consider reusing previously-created ones by invoking `app.getOnlineWorkingCopy(workingCopyId)`. All working copies are automatically deleted after 24 hours.
 {{% /alert %}}
 
 ### Code Explanation
 
-Here are some explanations about the script:
+Here are some explanations about the script.
 
 ```ts
 const client = new MendixPlatformClient();
@@ -92,15 +92,15 @@ Once you are done with the model changes, you can flush the changes to make sure
 
 ## Compiling and Running the Script
 
-1. Add the following section to `package.json` 
+1. Add the following section to `package.json`:
 
     ```json
     "scripts": {
         "start": "tsc && node script.js"
     }
     ```
 
-    This command will first compile your TypeScript code into JavaScript using the TypeScript compiler. After compilation, a file named `script.js` will be generated. The script will then be executed using Node.js.
+    This command first compiles your TypeScript code into JavaScript using the TypeScript compiler. After the compilation, a file named `script.js` is generated. The script will then be executed using Node.js.
 
 2. Run the script to see the results:
 
@@ -114,7 +114,7 @@ Once you are done with the model changes, you can flush the changes to make sure
     Successfully committed the working copy with id 'c70b078e-a323-42a7-b95d-7407a0e611d3' to branch 'main'
     ```
 
-Note that the steps for app creation and committing to the Team Server can take some time, so please be patient.
+The steps for app creation and committing to the Team Server can take some time. Please be patient.
 
 ## Next Step
 

content/en/docs/apidocs-mxsdk/mxsdk/sdk-howtos/setting-up-your-development-environment.md

@@ -22,13 +22,14 @@ $ npm init --yes
 $ npm install mendixmodelsdk mendixplatformsdk --save
 $ npm install typescript@~4.6.2 @types/node@^22 --save-dev
 ```
-You can now proceed directly to step 6 in the detailed instructions to configure TypeScript.
+
+You can now proceed directly to step 6 in the [Setting Up a Working Directory for Your Script](#setting-working-directory) section to configure TypeScript.
 
 ## Setting Up Your Development Tools {#setting}
 
 To set up your development tools, follow these steps:
 
-1. Install the latest LTS version of [Node.js](https://nodejs.org/). If you need to download it, you can find it on [this page](https://nodejs.org/en/download/releases/).
+1. Download and install the latest LTS version of [Node.js](https://nodejs.org/en/download).
 
 2. Open a terminal (on Windows, [Command Prompt](https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands)) and run the following command:
 
@@ -37,14 +38,13 @@ To set up your development tools, follow these steps:
     v22.15.0
     ```
 
-    For Debian-based Linux distributions such as Ubuntu, please refer to [NodeSource Node.js Binary Distributions](https://github.com/nodesource/distributions#user-content-installation-instructions) to properly set up your apt-get sources.
-
-    In the rest of the how-tos, in blocks such as the above, lines starting with a `$` represent commands to type into a terminal. Sometimes a line follows without a $, represents output of the command.
+    For Debian-based Linux distributions such as Ubuntu, refer to [NodeSource Node.js Binary Distributions](https://github.com/nodesource/distributions#user-content-installation-instructions) to properly set up your apt-get sources.
 
-3. Install [Visual Studio Code](https://code.visualstudio.com/) (not to be confused with Visual Studio), a text editor/IDE with good support for [TypeScript](https://www.typescriptlang.org/). Make sure you have a recent version (v1.11.0+); check the version you are using through Help > About when you have Code opened.
+    In the rest of the how-tos, in code blocks such as the above, lines starting with a `$` represent the commands you should type into a terminal. Lines without `$` immediately following a command represent the output produced by that command.
 
+3. Install [Visual Studio Code](https://code.visualstudio.com/) (VS Code: not to be confused with Visual Studio), a text editor/IDE with good support for [TypeScript](https://www.typescriptlang.org/). Make sure you have a recent version (v1.11.0+). Check the version you are using through **Help > About** when you have VS Code opened.
 
-## Setting Up a Working Directory for Your Script
+## Setting Up a Working Directory for Your Script {#setting-working-directory}
 
 To set up a working directory for your script, follow these steps:
 
@@ -58,13 +58,13 @@ To set up a working directory for your script, follow these steps:
 
     Visual Studio Code, other than Visual Studio, works with directories instead of project files.
 
-2. Start **Visual Studio Code** and open the directory you just created. You can open a new instance of Code from the command line with the directory you want to open as first argument. For example, if your current working directory in your terminal is the directory in which all your project files live, use the following command to open Code:
+2. Start Visual Studio Code and open the directory you just created. You can open a new instance of VS Code from the command line with the directory you want to open as first argument. For example, if your current working directory in your terminal is the directory in which all your project files live, use the following command to open VS Code:
 
     ```bash
     $ code .
     ```
 
-3. Add `mendixmodelsdk`, and `mendixplatformsdk` as dependencies. 
+3. Add `mendixmodelsdk` and `mendixplatformsdk` as dependencies. 
     Dependencies are stored in the `node_modules` directory (which will be automatically created by `npm` if necessary). Open the *package.json* you just created. Add a [`dependencies` block](https://docs.npmjs.com/files/package.json#dependencies) that looks like this:
 
     ```json
@@ -74,10 +74,10 @@ To set up a working directory for your script, follow these steps:
     }
     ```
 
-    When a new major version of the Mendix SDK is released (as in, 1.0.0 to 2.0.0) and you run `npm update` in your project folder, the `^` in front of the version number makes sure that the installed version of the SDK will not be upgraded automatically. Only minor and patch releases (as in, 1.1.1) of the SDK will be automatically upgraded; otherwise, your script could inadvertently be broken. You may, of course, edit the dependency by hand yourself.
+    When a new major version of the Mendix SDK is released (as in, 1.0.0 to 2.0.0) and you run `npm update` in your project folder, the `^` in front of the version number makes sure that the installed version of the SDK will not be upgraded automatically. Only minor and patch releases (as in, 1.1.1) of the SDK will be automatically upgraded; otherwise, your script could inadvertently be broken. You may, of course, edit the dependency yourself.
 
-4. Add `typescript`, and `@types/node` as dev dependencies. 
-    Packages like TypeScript, testing libraries, linters, and type definitions (@types/...) are not required for your app to run in production—they're only needed while writing and testing code.
+4. Add `typescript` and `@types/node` as dev dependencies. 
+    Packages like TypeScript, testing libraries, linters, and type definitions (@types/...) are not required for your app to run in production—they are only needed while writing and testing code.
 
     ```json
     "devDependencies": {
@@ -86,15 +86,15 @@ To set up a working directory for your script, follow these steps:
     }
     ```
 
-5. Save your changes and then execute the following to install the dependencies:
+5. Save your changes and then run the following command to install the dependencies:
 
     ```bash
     $ npm install
     ```
 
     If you are using version control, make sure to ignore the `node_modules` directory, otherwise you end up committing dependencies.
 
-6. In Code, create a [tsconfig.json](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) file next to your *package.json*. The *tsconfig.json* file is used by the TypeScript compiler to compile your code in the proper manner to a JS file. Create it with the following contents. 
+6. In VS Code, create a [tsconfig.json](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html) file in the same directory of *package.json*. The *tsconfig.json* file is used by the TypeScript compiler to compile your code in a proper manner to a JavaScript file. Add the following contents to the *tsconfig.json* file:
 
     ```json
     {
@@ -112,7 +112,7 @@ To set up a working directory for your script, follow these steps:
 
     The compiler options should be left as-is. The `files` directive is an array of strings with path names of all TypeScript files that make up your Node.js script or app. You can change it so that the compiler uses the right files.
 
-    Create new files in your app directory with Visual Studio Code by hovering over the name of the working directory in the left-side pane. When the **New file** icon appears, click it to create a new file. For more information on basic editing with VSC, see [Basic Editing](https://code.visualstudio.com/Docs/editor/codebasics).
+    Create new files in your app directory with VS Code by hovering over the name of the working directory in the left-side pane. When the **New file** icon appears, click it to create a new file. For more information on basic editing with VS Code, see [Basic Editing](https://code.visualstudio.com/Docs/editor/codebasics).
 
 ## Next Step