From cb91e06bf1a7a8e942f6ab7689e30c6541cf75ed Mon Sep 17 00:00:00 2001 From: Engincan VESKE Date: Tue, 22 Oct 2024 14:30:12 +0300 Subject: [PATCH] Update part-04.md --- docs/en/tutorials/modular-crm/part-04.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/tutorials/modular-crm/part-04.md b/docs/en/tutorials/modular-crm/part-04.md index 6c435e6a79..1674ced6c6 100644 --- a/docs/en/tutorials/modular-crm/part-04.md +++ b/docs/en/tutorials/modular-crm/part-04.md @@ -48,7 +48,7 @@ Since we've created a standard module, it doesn't have multiple layers like the ![file-system-odering-module-initial-folder](images/file-system-ordering-module-initial-folder.png) -Because only a single UI package can be chosen, the UI type doesn’t matter. This is why the package name is changed to *ModuleCrm.Ordering.UI*. Additionally, there are no *Domain*, *EntityFrameworkCore*, or *Http* layers like in the DDD module. We're going to use the `ModularCrm.Ordering` package for the domain business logic. You can open `ModularCrm.Ordering.sln` in your favorite IDE (e.g. Visual Studio): +Because only a single UI package can be chosen, the UI type doesn’t matter. This is why the package name is changed to *ModularCrm.Ordering.UI*. Additionally, there are no *Domain*, *EntityFrameworkCore*, or *Http* layers like in the DDD module. We're going to use the `ModularCrm.Ordering` package for the domain business logic. You can open `ModularCrm.Ordering.sln` in your favorite IDE (e.g. Visual Studio): ![ordering-module-visual-studio](images/ordering-module-visual-studio.png)