From 5eee24602a7f43efa8e59542f6c47f54d647de73 Mon Sep 17 00:00:00 2001 From: Artur Souza Date: Tue, 26 Oct 2021 21:15:34 -0700 Subject: [PATCH] Update daprdocs/content/en/operations/components/certification-lifecycle.md Co-authored-by: greenie-msft <56556602+greenie-msft@users.noreply.github.com> --- .../content/en/operations/components/certification-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/components/certification-lifecycle.md b/daprdocs/content/en/operations/components/certification-lifecycle.md index 7e84901bc..1ad8e0fbd 100644 --- a/daprdocs/content/en/operations/components/certification-lifecycle.md +++ b/daprdocs/content/en/operations/components/certification-lifecycle.md @@ -77,7 +77,7 @@ Each stable component in the [components-contrib](https://github.com/dapr/compon Test plan for stable components should include the following scenarios: -- Client reconnection: in case the client library cannot connect to the service for a moment, Dapr sidecar should not require to be restarted once the service is back online. +- Client reconnection: in case the client library cannot connect to the service for a moment, Dapr sidecar should not require a restart once the service is back online. - Authentication options: validate the component can authenticate with all the supported options. - Validate resource provisioning: validate if the component automatically provisions resources on initialization, if applicable. - All scenarios relevant to the corresponding building block and component.