From 142c879f9866bee47a05b0545152c82b1ee9663d Mon Sep 17 00:00:00 2001 From: Hannah Hunter Date: Wed, 19 Jul 2023 09:13:34 -0400 Subject: [PATCH] yep another link Signed-off-by: Hannah Hunter --- .../building-blocks/actors/howto-actors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md b/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md index 36e3933b9aa..e94f95d1d81 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md +++ b/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. This means your state store [component](https://github.com/dapr/components-contrib/tree/master/state) must implement the `TransactionalStore` 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