Fix typo in cqrs-microservice-reads.md (#20627)

zakaria-c · web-flow · commit 9eb447939990 · 2020-09-15T16:29:07.000+05:30
diff --git a/docs/architecture/microservices/microservice-ddd-cqrs-patterns/cqrs-microservice-reads.md b/docs/architecture/microservices/microservice-ddd-cqrs-patterns/cqrs-microservice-reads.md
@@ -167,7 +167,7 @@ public class OrderSummary
 }
 ```
 
-This is another reason why explicit returned types are better than dynamic types, in the long term. When using the `ProducesResponseType` attribute, you can also specify what is the expected outcome in regards possible HTTP errors/codes, like 200, 400, etc.
+This is another reason why explicit returned types are better than dynamic types, in the long term. When using the `ProducesResponseType` attribute, you can also specify what is the expected outcome in regards to possible HTTP errors/codes, like 200, 400, etc.
 
 In the following image, you can see how Swagger UI shows the ResponseType information.
 

Original file line number	Diff line number	Diff line change
`@@ -167,7 +167,7 @@ public class OrderSummary`
`167`	`167`	`}`
`168`	`168`	```
`169`	`169`
`170`		-This is another reason why explicit returned types are better than dynamic types, in the long term. When using the `ProducesResponseType` attribute, you can also specify what is the expected outcome in regards possible HTTP errors/codes, like 200, 400, etc.
	`170`	+This is another reason why explicit returned types are better than dynamic types, in the long term. When using the `ProducesResponseType` attribute, you can also specify what is the expected outcome in regards to possible HTTP errors/codes, like 200, 400, etc.
`171`	`171`
`172`	`172`	`In the following image, you can see how Swagger UI shows the ResponseType information.`
`173`	`173`