diff --git a/guides/deployment/microservices.md b/guides/deployment/microservices.md
index eeccfdb83f..df9cfd6e7f 100644
--- a/guides/deployment/microservices.md
+++ b/guides/deployment/microservices.md
@@ -1,6 +1,7 @@
 ---
 synopsis: >
   A guide on deploying SAP Cloud Application Programming Model (CAP) applications as microservices to the SAP BTP Cloud Foundry environment.
+status: released
 ---
 
 # Microservices with CAP
@@ -10,10 +11,10 @@ A comprehensive guide on deploying your CAP application as microservices.
 [[toc]]
 
 
-## Create a Solution Monorepo <UnderConstruction/>
+## Create a Solution Monorepo
 
 Assumed we want to create a composite application consisting of two or more micro services, each living in a separate GitHub repository, for example:
-<!-- Those links aren't working links. Why do we use those? -->
+
 - https://github.com/capire/bookstore
 - https://github.com/capire/reviews
 - https://github.com/capire/orders
@@ -906,12 +907,7 @@ resources:
 
 #### Subsequent updates
 
-- TODO... 
-- Whenever one of the projects has changes affecting the database, that triggers a new deployment of the `shared-db` project
-- `git submodules` gives you control of which versions to pull, for example by `git branches` or `git tags` 
-- Ensure to first deploy `shared-db` before deploying the others
-
-
+Whenever one of the projects has changes affecting the database, the database artifacts need to be deployed prior to the application deployment. With a single `mta.yaml`, this is handled in the scope of the mta deployment. When using multiple deployment units, ensure to first deploy the `shared-db` project before deploying the others.
 
 ## Late-Cut Microservices