diff --git a/docs/en/tutorials/microservice/images/abp-studio-run-build-start.png b/docs/en/tutorials/microservice/images/abp-studio-run-build-start.png
new file mode 100644
index 0000000000..39e006e2e9
Binary files /dev/null and b/docs/en/tutorials/microservice/images/abp-studio-run-build-start.png differ
diff --git a/docs/en/tutorials/microservice/images/web-orders-page.png b/docs/en/tutorials/microservice/images/web-orders-page.png
new file mode 100644
index 0000000000..92fd1040fc
Binary files /dev/null and b/docs/en/tutorials/microservice/images/web-orders-page.png differ
diff --git a/docs/en/tutorials/microservice/part-05.md b/docs/en/tutorials/microservice/part-05.md
index 3b1a3185aa..0ad81547f3 100644
--- a/docs/en/tutorials/microservice/part-05.md
+++ b/docs/en/tutorials/microservice/part-05.md
@@ -8,7 +8,7 @@
     "Path": "tutorials/microservice/part-04"
   },
   "Next": {
-    "Name": "Integrating the modules: Implementing Integration Services",
+    "Name": "Integrating the services: HTTP API Calls",
     "Path": "tutorials/microservice/part-06"
   }
 }
@@ -410,3 +410,23 @@ private static async Task ConfigureMainMenuAsync(MenuConfigurationContext contex
         );
 }
 ```
+
+## Building and Running the Application
+
+Now, we can build and run the application to see the changes. Please stop the applications if they are running. Then open the *Solution Runner* panel, right-click the `CloudCrm` root item, and select the *Run* -> *Build & Start* command.
+
+![abp-studio-run-build-start](images/abp-studio-run-build-start.png)
+
+After the applications start, you can *Browse* and navigate to the `Orders` page to see the list of orders:
+
+![web-orders-page](images/web-orders-page.png)
+
+Great! We have successfully implemented the Ordering module. However, there is a problme:
+
+- We see Product's GUID ID instead of its name. This is because the *Ordering* microservice has no integration with the *Catalog* microservice and doesn't have access to Product microservice's database to perform a JOIN query.
+
+We will solve this problem in the next part by implementing an integration service between the *Ordering* and *Catalog* microservices.
+
+## Summary
+
+In this part, we implemented the Ordering module manually. We created the `Order` entity, the `OrderState` enum, the `OrderAppService` application service, and the user interface for the `Orders` page. We also added a menu item to the sidebar to navigate to the `Orders` page.
\ No newline at end of file
diff --git a/docs/en/tutorials/microservice/part-06.md b/docs/en/tutorials/microservice/part-06.md
new file mode 100644
index 0000000000..476d2e6a9e
--- /dev/null
+++ b/docs/en/tutorials/microservice/part-06.md
@@ -0,0 +1,16 @@
+# Microservice Tutorial Part 06: Integrating the services: HTTP API Calls
+
+````json
+//[doc-nav]
+{
+  "Previous": {
+    "Name": "Building the Ordering module",
+    "Path": "tutorials/microservice/part-05"
+  },
+  "Next": {
+    "Name": "Integrating the services: Using Distributed Events",
+    "Path": "tutorials/microservice/part-07"
+  }
+}
+````
+