From 216d9802f5eaedcf1d5ae947d6fa0f9bd761a216 Mon Sep 17 00:00:00 2001
From: Bernd Verst <4535280+berndverst@users.noreply.github.com>
Date: Tue, 27 Dec 2022 15:52:55 -0800
Subject: [PATCH] Update tests/conformance/README.md

Signed-off-by: Bernd Verst <4535280+berndverst@users.noreply.github.com>
---
 tests/conformance/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/conformance/README.md b/tests/conformance/README.md
index 689721ff7..ffed4f0bc 100644
--- a/tests/conformance/README.md
+++ b/tests/conformance/README.md
@@ -181,7 +181,7 @@ terraform framework we have in place. To enable your component test to use terra
 
 ## Adding new AWS component in github actions
 
-1. For tests involving aws components we use a service account to provision the resources needed. If you are contributing a brand new component you will need to make sure our account has sufficient permissions to provision resources and use handle component. A Dapr STC/Maintainer will have to update the service account so contact them for assistance.
+1. For tests involving aws components we use a service account to provision the resources needed. If you are contributing a brand new component you will need to make sure our account has sufficient permissions to provision resources and use handle component. A Dapr STC member will have to update the service account so contact them for assistance.
 
 2. In your component yaml for your tests you should set the component metadata properties `accesskey` and `secretkey` to the values of `${{AWS_ACCESS_KEY_ID}}` and `${{AWS_SECRET_ACCESS_KEY}}`. These env values will contain the credentials for the testing service account.