From 8bf29a5b90e9ad5e67f04bc50f49ec7c51e6413f Mon Sep 17 00:00:00 2001 From: greenie-msft <56556602+greenie-msft@users.noreply.github.com> Date: Fri, 4 Nov 2022 11:33:11 -0700 Subject: [PATCH] Update daprdocs/content/en/getting-started/quickstarts/resiliency-quickstart.md Signed-off-by: greenie-msft <56556602+greenie-msft@users.noreply.github.com> --- .../en/getting-started/quickstarts/resiliency-quickstart.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/getting-started/quickstarts/resiliency-quickstart.md b/daprdocs/content/en/getting-started/quickstarts/resiliency-quickstart.md index 84c7554eb..0d2764803 100644 --- a/daprdocs/content/en/getting-started/quickstarts/resiliency-quickstart.md +++ b/daprdocs/content/en/getting-started/quickstarts/resiliency-quickstart.md @@ -11,7 +11,7 @@ description: "Get started with Dapr's resiliency capabilities" Resiliency is currently a preview feature. {{% /alert %}} -In this Quickstart, you will observe Dapr resiliency capabilities by introducing toxic behavior to a microservice that continuously perists and retrieves state via Dapr's state management API. +In this Quickstart, you will observe Dapr resiliency capabilities by simulating a system failure. You will execute a microservice application that continuously persists and retrieves state via Dapr's state management API. When operations to the state store begin to fail, Dapr resiliency policies are applied. The resiliency policies used in this example are defined and applied via the [resiliency spec]() located in the components directory.