From 72bd20a986b813c9351c6b78dd7d0fed4889fa47 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Halil=20=C4=B0brahim=20Kalkan?= <hi_kalkan@yahoo.com>
Date: Mon, 23 Sep 2024 14:02:15 +0300
Subject: [PATCH] Grammer fixes

---
 docs/en/tutorials/modular-crm/part-02.md | 26 ++++++++++++------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/docs/en/tutorials/modular-crm/part-02.md b/docs/en/tutorials/modular-crm/part-02.md
index edc6f6bb38..14560b3766 100644
--- a/docs/en/tutorials/modular-crm/part-02.md
+++ b/docs/en/tutorials/modular-crm/part-02.md
@@ -14,11 +14,11 @@
 }
 ````
 
-In this part, you will build a new module for product management and install it to the main CRM application.
+In this part, you will build a new product management module and install it in the main CRM application.
 
 ## Creating Solution Folders
 
-You can create solution folders and sub-folders in *Solution Explorer* to better organize your solution components. Right-click to the solution root on the *Solution Explorer* panel, and select *Add* -> *New Folder* command:
+You can create solution folders and sub-folders in *Solution Explorer* to organize your solution components better. Right-click to the solution root on the *Solution Explorer* panel, and select *Add* -> *New Folder* command:
 
 ![abp-studio-add-new-folder-command](images/abp-studio-add-new-folder-command.png)
 
@@ -26,7 +26,7 @@ That command opens a dialog where you can set the folder name:
 
 ![abp-studio-new-folder-dialog](images/abp-studio-new-folder-dialog.png)
 
-Create `main` and `modules` folder using the *New Folder* command, then move the `ModularCrm` module into the `main` folder (simply by drag & drop). The *Solution Explorer* panel should look like the following figure now:
+Create a `main` and a `modules` folder using the *New Folder* command, then move the `ModularCrm` module into the `main` folder (simply by drag & drop). The *Solution Explorer* panel should look like the following figure now:
 
 ![abp-studio-solution-explorer-with-folders](images/abp-studio-solution-explorer-with-folders.png)
 
@@ -35,15 +35,15 @@ Create `main` and `modules` folder using the *New Folder* command, then move the
 There are two module templates provided by ABP Studio:
 
 * **Empty Module**: You can use that module template to build your module structure from scratch.
-* **DDD Module**: A Domain-Driven Design based layered module structure.
+* **DDD Module**: A Domain Driven Design based layered module structure.
 
-We will use the *DDD Module* template for the Product module. We will use the *Empty Module* template later in this tutorial.
+We will use the *DDD Module* template for the Product module and the *Empty Module* template later in this tutorial.
 
 Right-click the `modules` folder on the *Solution Explorer* panel, and select the *Add* -> *New Module* -> *DDD Module* command:
 
 ![abp-studio-add-new-dd-module](images/abp-studio-add-new-dd-module.png)
 
-This command opens a new dialog to define properties of the new module. You can use the following values to create a new module named `ModularCrm.Products`:
+This command opens a new dialog to define the properties of the new module. You can use the following values to create a new module named `ModularCrm.Products`:
 
 ![abp-studio-create-new-module-dialog](images/abp-studio-create-new-module-dialog.png)
 
@@ -58,7 +58,7 @@ Here, you can select the UI type you want to support in your module:
 A module;
 
 * May not contain a UI and leaves the UI development to the final application.
-* May contain a single UI implementation that is typically in the same technology with the main application.
+* May contain a single UI implementation that is typically in the same technology as the main application.
 * May contain more than one UI implementation if you want to create a reusable application module and you want to make that module usable by different applications with different UI technologies. For example, all of [pre-built ABP modules](https://abp.io/modules) support multiple UI options.
 
 In this tutorial, we are selecting the MVC UI since we are building that module only for our `ModularCrm` solution and we are using the MVC UI in our application. So, select the MVC UI and click the *Next* button.
@@ -93,11 +93,11 @@ As seen in the preceding figure, the `ModularCrm.Products` solution consists of
 
 ### Installing the Product Module to the Main Application
 
-A module does not contain an executable application inside. The `Modular.Products.Web` project is just a class library project, not an executable web application. A module should be installed to an executable application in order to run it.
+A module does not contain an executable application inside. The `Modular.Products.Web` project is just a class library project, not an executable web application. A module should be installed in an executable application to run it.
 
 > **Ensure that the web application is not running in [Solution Runner](../../studio/running-applications.md) or in your IDE. Installing a module to a running application will produce errors.**
 
-The product module has no relation to the main application yet. Right-click to the `ModularCrm` module (inside the `main` folder) and select the *Import Module* command:
+The product module has yet to be related to the main application. Right-click on the `ModularCrm` module (inside the `main` folder) and select the *Import Module* command:
 
 ![abp-studio-import-module](images/abp-studio-import-module.png)
 
@@ -105,7 +105,7 @@ The *Import Module* command opens a dialog as shown below:
 
 ![abp-studio-import-module-dialog](images/abp-studio-import-module-dialog.png)
 
-Select the `ModularCrm.Products` module and check the *Install this module* option. If you don't check that option, it only imports the module but doesn't setup project dependencies. Importing a module without installation can be used to manually setup your project dependencies. Here, we want to make it automatically, so checking the *Install this module* option.
+Select the `ModularCrm.Products` module and check the *Install this module* option. If you don't check that option, it only imports the module but doesn't set project dependencies. Importing a module without installation can be used to set up your project dependencies manually. We want to make it automatically, so check the *Install this module* option.
 
 When you click the *OK* button, ABP Studio opens the *Install Module* dialog:
 
@@ -117,13 +117,13 @@ The default package match is good for this tutorial, so you can click the *OK* b
 
 ### Building the Main Application
 
-After the installation, build the entire solution by right-clicking to the `ModularCrm` module (under the `main` folder) and select the *Dotnet CLI* -> *Graph Build* command:
+After the installation, build the entire solution by right-clicking on the `ModularCrm` module (under the `main` folder) and selecting the *Dotnet CLI* -> *Graph Build* command:
 
 ![abp-studio-graph-build](images/abp-studio-graph-build.png)
 
-Graph Build is a dotnet CLI command that recursively build all the referenced dotnet projects even if they are not a part of the root solution.
+Graph Build is a dotnet CLI command that recursively builds all the referenced dotnet projects, even if they are not part of the root solution.
 
-> While developing multi-module solutions with ABP Studio, you may need to perform *Graph Build* on the root/main module if you made changes in the depending modules.
+> While developing multi-module solutions with ABP Studio, you may need to perform *Graph Build* on the root/main module if you change the depending modules.
 
 ### Run the Main Application