Clarify pull request usage in README

Signed-off-by: Rodrigo Tavares <[email protected]> Update README.md Thanks @dhaiducek Co-authored-by: Dale Haiducek <[email protected]> Signed-off-by: Rodrigo Tavares <[email protected]>
open-cluster-management-io · Jul 18, 2024 · 2b06406 · 2b06406
1 parent a4c5a11
commit 2b06406
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -28,11 +28,11 @@ This is known as `PolicySets` and these contributions are made in directories or
 
 ## Using GitOps to deploy policies to a cluster
 
-Fork this repository and use the forked version as the target to run the sync against. This is to
-avoid unintended changes to be applied to your cluster automatically. To get latest policies from
-the `policy-collection` repository, you can pull the latest changes from `policy-collection` to your
-own repository through a pull request. Any further changes to your repository are automatically be
-applied to your cluster.
+Fork this repository and use the forked version as the target to run the sync. This avoids
+unintended changes to your cluster. To get the latest policies from the `policy-collection`
+repository, pull the latest changes from `policy-collection` and then create a pull request to merge
+these changes into your forked repository. Any further changes to your repository will be applied to
+your cluster automatically.
 
 Make sure you have [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) installed and
 that you are logged into your hub cluster in terminal.