Update part-03.md

Fix typo in FOLLOWING

docs/en/tutorials/modular-crm/part-03.md

@@ -387,7 +387,7 @@ Configure<AbpAspNetCoreMvcOptions>(options =>
 {
     options.ConventionalControllers.Create(typeof(ModularCrmApplicationModule).Assembly);
     
-    //ADD THE FOLLOWINGN LINE:
+    //ADD THE FOLLOWING LINE:
     options.ConventionalControllers.Create(typeof(ProductsApplicationModule).Assembly);
 });
 ````
@@ -503,4 +503,4 @@ Some of the projects in the product module's .NET solution (`ModularCrm.Products
 * `ModularCrm.Products.HttpApi`: That project is to define regular HTTP API controllers. If you will always use ABP's [Auto API Controllers](../../framework/api-development/auto-controllers.md) feature (like we did in this tutorial), you can delete that project.
 * `ModularCrm.Products.HttpApi.Client`: That project is generally shared with 3rd-party applications, so they can easily consume your HTTP API endpoints. In a modular monolith application, you typically don't need it.
 * `ModularCrm.Products.HttpApi.Installer`: That project is used to discover and install a multi-projects module (like the product module) when you deploy it to a package management system (like NuGet). If you will use the module with local project references (like we did here), you can delete that project.
-* You can also delete the test projects (there are 4 of them in the solution) if you don't prefer to write unit/integration tests in the module's solution (Legal warning: it is recommended to write tests &#128522;)
+* You can also delete the test projects (there are 4 of them in the solution) if you don't prefer to write unit/integration tests in the module's solution (Legal warning: it is recommended to write tests &#128522;)