Update actor state store docs to include strong consistency requirement

Signed-off-by: Jonathan Collinge <[email protected]>

Author: jjcollinge

daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md

@@ -27,7 +27,7 @@ Alternatively, you can use the Dapr SDK in [.NET]({{< ref "dotnet-actors" >}}),
 Actors can save state reliably using state management capability.
 You can interact with Dapr through HTTP/gRPC endpoints for state management.
 
-To use actors, your state store must support multi-item transactions.  This means your state store [component](https://github.com/dapr/components-contrib/tree/master/state) must implement the [TransactionalStore](https://github.com/dapr/components-contrib/blob/master/state/transactional_store.go) interface.  The list of components that support transactions/actors can be found here: [supported state stores]({{< ref supported-state-stores.md >}}). Only a single state store component can be used as the statestore for all actors.
+To use actors, your state store must support multi-item transactions, etags and have strong consistency.  This means your state store [component](https://github.com/dapr/components-contrib/tree/master/state) must implement the [TransactionalStore](https://github.com/dapr/components-contrib/blob/master/state/transactional_store.go) interface.  The list of components that support transactions/actors can be found here: [supported state stores]({{< ref supported-state-stores.md >}}). Only a single state store component can be used as the statestore for all actors.
 
 ## Actor timers and reminders
 

daprdocs/content/en/developing-applications/building-blocks/state-management/state-management-overview.md

@@ -71,7 +71,7 @@ Dapr supports two types of bulk operations - **bulk** or **multi**. You can grou
 Read the [API reference]({{< ref state_api.md >}}) to learn how use bulk and multi options.
 
 ### Actor state
-Transactional state stores can be used to store actor state. To specify which state store to be used for actors, specify value of property `actorStateStore` as `true` in the metadata section of the state store component. Actors state is stored with a specific scheme in transactional state stores, which allows for consistent querying. Only a single state store component can be used as the statestore for all actors. Read the [API reference]({{< ref state_api.md >}}) to learn more about state stores for actors and the [actors API reference]({{< ref actors_api.md >}})
+Transactional state stores can be used to store actor state. The state store must have strong consistency. To specify which state store to be used for actors, specify value of property `actorStateStore` as `true` in the metadata section of the state store component. Actors state is stored with a specific scheme in transactional state stores, which allows for consistent querying. Only a single state store component can be used as the statestore for all actors. Read the [API reference]({{< ref state_api.md >}}) to learn more about state stores for actors and the [actors API reference]({{< ref actors_api.md >}})
 
 ### Query state store directly
 

daprdocs/content/en/reference/components-reference/supported-state-stores/_index.md

@@ -22,7 +22,7 @@ Table captions:
 
 The following stores are supported, at various levels, by the Dapr state management building block:
 
-> State stores can be used for actors if it supports both transactional operations and etag.
+> State stores can be used for actors if it supports, transactional operations, etag and has strong consistency.
 
 ### Generic