[en] update skoala release notes and DME term (#5666)

docs/en/docs/skoala/intro/advantages.md

@@ -21,7 +21,7 @@ Microservice Engline has the following advantages over its counterparts:
 
 - Easy Transition
 
-    Microservice Engline can manage both traditional and cloud native microservices. You can integrate traditional registries (Zookeeper, Eureka, Nacos, Consul) and cloud native registries (Kubernetes, Service Mesh) into DME. You can also create a Nacos registry in Microservice Engline and enable Mesh plugin to change traditional microservices to cloud native ones, no need to change service codes.
+    Microservice Engline can manage both traditional and cloud native microservices. You can integrate traditional registries (Zookeeper, Eureka, Nacos, Consul) and cloud native registries (Kubernetes, Service Mesh) into Microservice Engine. You can also create a Nacos registry in Microservice Engline and enable Mesh plugin to change traditional microservices to cloud native ones, no need to change service codes.
 
 - Open and Compatible
 

docs/en/docs/skoala/intro/release-notes.md

@@ -9,6 +9,14 @@ This page lists the release notes of Microservices to help you learn its feature
 
 *[skoala]: Internal development codename for DaoCloud Microservice Engine
 
+## 2024-09-02
+
+### v0.40.1
+
+#### Fixes
+
+- **Fixed** an issue where the gateway could not be used when sharing LB VIP
+
 ## 2024-08-26
 
 ### v0.40.0

docs/en/docs/skoala/intro/scenarios.md

@@ -7,18 +7,18 @@ hide:
 
 # Use Cases
 
-DaoCloud Microservice Engine (DME) is a one-stop management platform for common microservice frameworks. It mainly consists of two parts: service governance and cloud native gateway, providing service registration and discovery, configuration management, east-west traffic governance, service monitoring, south-north traffic management, API management, domain name management, etc, covering most user cases throughout the lifecycle of microservice management.
+DaoCloud Microservice Engine is a one-stop management platform for common microservice frameworks. It mainly consists of two parts: service governance and cloud native gateway, providing service registration and discovery, configuration management, east-west traffic governance, service monitoring, south-north traffic management, API management, domain name management, etc, covering most user cases throughout the lifecycle of microservice management.
 
-Based on the [features list](./features.md), DME can be used for registration and discovery of microservice, configuration management, traffic governance, and gateway management. Here are some typical use cases:
+Based on the [features list](./features.md), Microservice Engine can be used for registration and discovery of microservice, configuration management, traffic governance, and gateway management. Here are some typical use cases:
 
 ## One-stop management of heterogeneous microservices
 
-Microservices in the same system may use different architectures. Some use traditional SpringCloud or Dubbo framework, and some may take a more cloud native way with Kubernetes or Service Mesh. As the number of microservices grows quickly, the whole system is susceptible to avalanche caused by cascade effect resulted from complicated invocation relationship between microservices. This will add difficulty and cost of operation and maintenance of microservice system. Therefore, a **one-stop platform** that can manage both traditional and cloud native microservices is in highly demand. This is why DME came into being. It can monitor service information, trace invocations, manage microservice configuration, and govern north-south traffic for the two kind of microservices.
+Microservices in the same system may use different architectures. Some use traditional SpringCloud or Dubbo framework, and some may take a more cloud native way with Kubernetes or Service Mesh. As the number of microservices grows quickly, the whole system is susceptible to avalanche caused by cascade effect resulted from complicated invocation relationship between microservices. This will add difficulty and cost of operation and maintenance of microservice system. Therefore, a **one-stop platform** that can manage both traditional and cloud native microservices is in highly demand. This is why Microservice Engine came into being. It can monitor service information, trace invocations, manage microservice configuration, and govern north-south traffic for the two kind of microservices.
 
 ## Transition from traditional to cloud native microservices
 
-Cloud native has significant advantages in scalability, isolation of bottom differences, troubleshooting and other aspects. Under the influence of the cloud native hit, some enterprises may want to steadily and gradually shift from the traditional microservice architecture to the cloud native architecture, and some enterprises may hope to finish the transition with one step. DME can meet both requirements, because it supports unified management of traditional and cloud native microservices, and supports traffic governance by Sentinel and Service Mesh.
+Cloud native has significant advantages in scalability, isolation of bottom differences, troubleshooting and other aspects. Under the influence of the cloud native hit, some enterprises may want to steadily and gradually shift from the traditional microservice architecture to the cloud native architecture, and some enterprises may hope to finish the transition with one step. Microservice Engine can meet both requirements, because it supports unified management of traditional and cloud native microservices, and supports traffic governance by Sentinel and Service Mesh.
 
 ## Efficient visualized microservice gateway
 
-Many open-source gateway projects only support command line operation, which is not user-friendly. In some cases, several microservices share the same gateway, which costs a lot of resources and may gradually become the resource bottleneck of the whole system. Based on Contour, DME offers an GUI interface to operate gateways and further enriches some key features, such as API management, domain name, and service integrate. It allows multi-gateway management and easy creation of multiple gateway instances in different clusters and namespaces. These gateway instances are isolated from each other, securing higher availability and stability. In addition, the cascade feature of gateway routes can also be used to realize blue and green deployment of microservices.
+Many open-source gateway projects only support command line operation, which is not user-friendly. In some cases, several microservices share the same gateway, which costs a lot of resources and may gradually become the resource bottleneck of the whole system. Based on Contour, Microservice Engine offers an GUI interface to operate gateways and further enriches some key features, such as API management, domain name, and service integrate. It allows multi-gateway management and easy creation of multiple gateway instances in different clusters and namespaces. These gateway instances are isolated from each other, securing higher availability and stability. In addition, the cascade feature of gateway routes can also be used to realize blue and green deployment of microservices.

docs/en/docs/skoala/quickstart/select-workspace.md

@@ -5,7 +5,7 @@ hide:
 
 # Select Workspace
 
-When entering the DaoCloud Microservice Engine (DME) for the first time, you must select a
+When entering the DaoCloud Microservice Engine for the first time, you must select a
 [workspace](../../ghippo/user-guide/workspace/workspace.md) before any other actions.
 
 ![select a workspace](https://docs.daocloud.io/daocloud-docs-images/docs/en/docs/skoala/images/select-ws01.png)