From dd84e53aac0c370fc34c0b3f6ba80280d98a6093 Mon Sep 17 00:00:00 2001 From: Artur Souza Date: Fri, 29 Oct 2021 14:10:26 -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 ed088498f..4fcef667d 100644 --- a/daprdocs/content/en/operations/components/certification-lifecycle.md +++ b/daprdocs/content/en/operations/components/certification-lifecycle.md @@ -97,7 +97,7 @@ In order for a component to be certified, tests are run in an environment mainta ### New component certification: Alpha->Beta 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 creates an issue in the `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 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