diff --git a/daprdocs/content/en/concepts/service-mesh.md b/daprdocs/content/en/concepts/service-mesh.md
index cba402532..67902e48d 100644
--- a/daprdocs/content/en/concepts/service-mesh.md
+++ b/daprdocs/content/en/concepts/service-mesh.md
@@ -7,7 +7,7 @@ description: >
   How Dapr compares to, and works with service meshes
 ---
 
-Dapr uses the sidecar architecture, running as a separate process alongside the application and includes features such as network security and distributed tracing. This often raises the question - how does Dapr compares to service mesh solutions such as Linkerd and Istio?
+Dapr uses the sidecar architecture, running as a separate process alongside the application and includes features such as network security and distributed tracing. This often raises the question - how does Dapr compare to service mesh solutions such as Linkerd and Istio?
 
 ## How Dapr and service meshes compare
 While Dapr and service meshes do offer some overlapping capabilities, **Dapr is not a service mesh**. Unlike a service mesh which is focused on networking concerns, Dapr is focused on providing building blocks that make it easier for developers to build microservices. Dapr is developer-centric versus service meshes being infrastructure-centric.