diff --git a/docs/architecture/microservices/multi-container-microservice-net-applications/data-driven-crud-microservice.md b/docs/architecture/microservices/multi-container-microservice-net-applications/data-driven-crud-microservice.md
index 3210160044ce1..3eb7c0a6447c9 100644
--- a/docs/architecture/microservices/multi-container-microservice-net-applications/data-driven-crud-microservice.md
+++ b/docs/architecture/microservices/multi-container-microservice-net-applications/data-driven-crud-microservice.md
@@ -283,7 +283,7 @@ Versioning enables a Web API to indicate the features and resources that it expo
 
 - Header versioning
 
-Query string and URI versioning are the simplest to implement. Header versioning is a good approach. However, header versioning not as explicit and straightforward as URI versioning. Because URL versioning is the simplest and most explicit, the eShopOnContainers sample application uses URI versioning.
+Query string and URI versioning are the simplest to implement. Header versioning is a good approach. However, header versioning is not as explicit and straightforward as URI versioning. Because URL versioning is the simplest and most explicit, the eShopOnContainers sample application uses URI versioning.
 
 With URI versioning, as in the eShopOnContainers sample application, each time you modify the Web API or change the schema of resources, you add a version number to the URI for each resource. Existing URIs should continue to operate as before, returning resources that conform to the schema that matches the requested version.