docs: adapt cqrs

patterns/command-query-responsibility-segregation.md

@@ -7,15 +7,15 @@ description: Separation between commands and queries
 
 In its most basic form, it's just a separation (segregation) between requests that change data (commands) and requests that query data. For example application 1 handles all the commands and application 2 handles all the queries. Usually because each form has separate performance requirements such as throughput, latency, security, etc.
 
-Because read and write happens in different places, one of the drawbacks is having consistency between queries and commands as they lag behind.
+Because read and write happens in different places, one of the drawbacks is having consistency between queries and commands as they lag behind, also called [eventual consistency](./glossary.md#).
 
 Application in charge of processing commands:
 ```json
 {
   "asyncapi": "3.0.0",
   "info": {
     "title": "Command application",
-	  "description": "The application in charge of processing commands",
+    "description": "The application in charge of processing commands",
     "version": "1.0.0"
   },
   "channels": {
@@ -94,7 +94,7 @@ Application in charge of processing queries:
   "asyncapi": "3.0.0",
   "info": {
     "title": "Query application",
-	  "description": "The application in charge of processing queries",
+    "description": "The application in charge of processing queries",
     "version": "1.0.0"
   },
   "channels": {