diff --git a/daprdocs/content/en/operations/components/component-scopes.md b/daprdocs/content/en/operations/components/component-scopes.md
index 14af6701a..b28f92007 100644
--- a/daprdocs/content/en/operations/components/component-scopes.md
+++ b/daprdocs/content/en/operations/components/component-scopes.md
@@ -79,7 +79,7 @@ See [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-name
 {{% /alert %}}
 
 ## Application access to components with scopes
-Developers and operators might want to limit access for one database to a certain application, or a specific set of applications.
+Developers and operators might want to limit access to one database from a certain application, or a specific set of applications.
 To achieve this, Dapr allows you to specify `scopes` on the component YAML. Application scopes added to a component limit only the applications with specific IDs to be able to use the component.
 
 The following example shows how to give access to two Dapr enabled apps, with the app IDs of `app1` and `app2` to the Redis component named `statestore` which itself is in the `production` namespace