diff --git a/docs/en/modules/gdpr.md b/docs/en/modules/gdpr.md
index 45d380ecd9..76875e0403 100644
--- a/docs/en/modules/gdpr.md
+++ b/docs/en/modules/gdpr.md
@@ -236,9 +236,17 @@ This [Event Transfer Object](../framework/infrastructure/event-bus/distributed#e
 
 Cookie Consent can be used to inform the users of the application, before saving any specific data about the users. 
 
-This feature is enabled by default for the [Application](../solution-templates/layered-web-application) and [Application Single Layer](../solution-templates/single-layer-web-application) Startup Templates.
+This feature is enabled by default for the [Application](../solution-templates/layered-web-application) and [Application Single Layer](../solution-templates/single-layer-web-application) Startup Templates. You can easily enable/disable showing Cookie Consent by configuring the `AbpCookieConsentOptions`
 
-> You can easily enable/disable to show the Cookie Consent by configuring the `AbpCookieConsentOptions`, which explained above.
+If you want to override the texts in the Cookie Consent component, you just need to define the following localization keys in your localization resource files and change text as you wish:
+
+```json
+    "ThisWebsiteUsesCookie": "This website uses cookies to ensure you get the best experience on the website.",
+    "CookieConsentAgreePolicies": "If you continue to browse, then you agree to our {0} and {1}.",
+    "CookieConsentAgreePolicy": "If you continue to browse, then you agree to our {0}.",
+```
+
+> Refer to the [Localization documentation](../framework/fundamentals/localization.md) for more info about defining localization resources and overriding existing localization entries that comes from pre-built modules.
 
 ### Configuring the Cookie Consent
 
diff --git a/docs/en/solution-templates/microservice/how-to-use-with-abp-suite.md b/docs/en/solution-templates/microservice/how-to-use-with-abp-suite.md
index d5ffbf1b2c..8549032089 100644
--- a/docs/en/solution-templates/microservice/how-to-use-with-abp-suite.md
+++ b/docs/en/solution-templates/microservice/how-to-use-with-abp-suite.md
@@ -6,14 +6,54 @@ You can open ABP Suite from ABP Studio by using the **ABP Suite** -> **Open** to
 
 ![abp-suite-context-menu](images/abp-suite-context-menu.png)
 
-It opens the ABP Suite in a built-in browser window. You can also access the suite by visiting `http://localhost:3000` through your browser. From there, you can visually design your solution and generate code. In this example, we create a **Product** entity.
+It opens the ABP Suite in a built-in browser window. You can also access the suite by visiting `http://localhost:3000` through your browser. From there, you can visually design your solution and generate code. 
+
+In the following example, we've defined the entity name as **Product** and provide other metadata for the related entity:
 
 ![abp-suite-product-entity](images/abp-suite-product-entity.png)
 
 After clicking **Save and generate** for the entity in ABP Suite, use **Run** -> **Build & Restart** in the [Solution Runner](../../studio/running-applications.md#start) to apply the changes.
 
-To confirm, visit the Swagger UI to verify that the necessary API endpoints and services have been created.
+> ABP Suite requires you to stop all running instances in the related solution/project to be able to generate codes properly. Otherwise, it might not work effectively.
+
+Then, to confirm, you can visit the Swagger UI to verify that the necessary API endpoints and services have been created.
 
 ![abp-suite-product-services](images/abp-suite-product-services.png)
 
-> Currently, you can't generate UI code with ABP Suite for microservice solutions. This feature will be added in future releases.
\ No newline at end of file
+If you selected the *Create user interface* option for the entity, the related UI components (pages, styles, scripts etc.) will also be created. To be able to see the related pages in your host application/UI you should apply the following steps:
+
+1. Generate [*client-proxies*](../../framework/api-development/static-csharp-clients.md) with the following command:
+
+```bash
+abp generate-proxy -t csharp -url http://localhost:{your-service-port}/ -m {remote-service-name} --without-contracts
+```
+
+* You should run this command in the directory of your host application, and your microservices should be up and running.
+* The command will generate proxy classes for your microservice in the host application, which you can see under the **ClientProxies** folder.
+
+> **Note:** After each entity generation/modification in your services, then you should run this command to update client-proxies.
+
+2. Configure the application for the static client proxy:
+
+```csharp
+public class MyClientAppModule : AbpModule
+{
+    public override void ConfigureServices(ServiceConfigurationContext context)
+    {
+        // Prepare for static client proxy generation
+        context.Services.AddStaticHttpClientProxies(
+            typeof(MyServiceApplicationContractsModule).Assembly
+        );
+
+        // Include the generated app-generate-proxy.json in the virtual file system
+        Configure<AbpVirtualFileSystemOptions>(options =>
+        {
+            options.FileSets.AddEmbedded<MyClientAppModule>();
+        });
+    }
+}
+```
+
+After you apply these steps, you're ready to go to run your microservices and see the generated CRUD pages:
+
+![abp-suite-product-pages](images/abp-suite-products-pages.png)
diff --git a/docs/en/solution-templates/microservice/images/abp-suite-products-pages.png b/docs/en/solution-templates/microservice/images/abp-suite-products-pages.png
new file mode 100644
index 0000000000..01bee7ed5e
Binary files /dev/null and b/docs/en/solution-templates/microservice/images/abp-suite-products-pages.png differ