docs: update

Author: Angular2Guy

README.md

@@ -12,9 +12,9 @@ Technologies: Angular, Angular-Cli, Angular-Material, Typescript, Spring Boot, N
 ## Mission Statement
 The project shows howto build a collection of Microservices with their own Angular Microfrontends. The Microfrontends are the integrated in the shell application to give the user the impression of a single frontend. That enables the independend development of the Microservices by different teams with a user friendly modular integrated frontend -> no frontend monolith. 
 
-To project has three Microserives that enable the user to book a flight, to book a hotel and pay for the bookings. The payment microservice integrates the hotel booking and flight booking Microservices. 
+To project has three Microserives that enable the user to book a flight, to book a hotel and pay for the bookings at the checkout. The payment microservice integrates the hotel booking and flight booking Microservices. 
 
-The microservices are build according to the [Self Containted Systems](https://scs-architecture.org/) architecture. This architecture uses the bounded contexts of DDD to create services with distinct functionality. Each service has its own frontend, backend and database. The services should communicate only asynchronous with messaging by the backend. In the SCS architecture the focus of the Microservices is not so much on the size of each service then on the independence of the services. That enables an independent development of the Microservices and could keep the other Microservices working if one fails. The independent Microservices enable a the use of different software stacks for each one. That is used in the project to show NestJs with Typescript, Spring Boot with Java and Spring Boot with Kotlin.
+The microservices are build according to the [Self Containted Systems](https://scs-architecture.org/) architecture. This architecture uses the bounded contexts of DDD to create services with distinct functionality. Each service has its own frontend, backend and database. The services should communicate only asynchronous with messaging by the backend. In the SCS architecture the focus of the Microservices is not so much on the size of each service then on the independence of the services. That enables an independent development of the Microservices and could keep the other Microservices working if one fails. The independent Microservices enable a the use of different software stacks for each one. That is used in the project to show 3 microservices: NestJs with Typescript, Spring Boot with Java and Spring Boot with Kotlin. Each microservice has an Angular frontend.
 
 ## C4 Architecture Diagrams
 The [System Context Diagram](structurizr/diagrams/SystemContext.svg), the [Container Diagram](structurizr/diagrams/Containers.svg) and the [Component Diagram](structurizr/diagrams/Components.svg). The Diagrams have been created with Structurizr. The file runStructurizr.sh contains the commands to use Structurizr and the directory structurizr contains the dsl file.
@@ -35,7 +35,7 @@ The Payment Microservice integrates the Hotel Selection and Flight Selection fro
 For development was the Eclipse ide used.
 
 ## Microservice architecture
-All Microservices use the Clean Architecture with the Rings Adapter, Usecase, Domain to structure the code. The Dtos for the Rest controllers and the Mqtt clients are decoupled by Mappers to be able to change interfaces and database tables independently. The dependency management is done by injection.
+All Microservices use the Clean Architecture with the Rings Adapter, Usecase, Domain to structure the code. The Dtos for the Rest controllers and the Mqtt clients are decoupled by Mappers to be able to change interfaces and database tables independently. The dependency management is done by injection. The communication between microservices is done with MQTT and Apache Artemis.
 
 ## Run the System
 - Build the system with: