From 0bb42a7195b025652a76b2d69f2658fe8e8ed32f Mon Sep 17 00:00:00 2001 From: Donovan Brown Date: Sun, 6 Dec 2020 17:55:14 -0600 Subject: [PATCH] Added missing word I changed "such querying states" to "such as querying states" by adding the word 'as'. --- .../state-management/query-state-store/query-redis-store.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md b/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md index ab7632e09..42e4eee16 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md +++ b/daprdocs/content/en/developing-applications/building-blocks/state-management/query-state-store/query-redis-store.md @@ -6,7 +6,7 @@ weight: 2000 description: "Use Redis as a backend state store" --- -Dapr doesn't transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec]({{}}). You can directly interact with the underlying store to manipulate the state data, such querying states, creating aggregated views and making backups. +Dapr doesn't transform state values while saving and retrieving states. Dapr requires all state store implementations to abide by a certain key format scheme (see [Dapr state management spec]({{}}). You can directly interact with the underlying store to manipulate the state data, such as querying states, creating aggregated views and making backups. >**NOTE:** The following examples uses Redis CLI against a Redis store using the default Dapr state store implementation.