From 11c99ab946feb1cb96e244814717de6f2fa109ba Mon Sep 17 00:00:00 2001 From: Artur Souza Date: Fri, 29 Oct 2021 14:04:07 -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 3ad61ab4b..7f0abdeb3 100644 --- a/daprdocs/content/en/operations/components/certification-lifecycle.md +++ b/daprdocs/content/en/operations/components/certification-lifecycle.md @@ -99,7 +99,7 @@ For a component to be certified tests are run in an environment maintained by th For a new component requiring a certification change from Alpha to Beta, a request for component certification follows these steps: - Requestor creates an issue in `components-contrib` repository for certification of the component with the current and the new certification levels - Requestor submits a PR for integrating the component to run with the defined conformance test suite, if not included already - - The user details the environment setup in the issue created, so that a Dapr maintainer can setup the service in a managed environment + - The user details the environment setup in the issue created, so a Dapr maintainer can setup the service in a managed environment - After the environment setup is complete, Dapr maintainers review the PR and if approved merges that PR - Requestor submits a PR in `docs` repository, updating the component's certification level