Fix review comments

Author: amisstea

README.md

@@ -16,10 +16,10 @@ documentation instead.
 
 ### Operator CI Pipeline
 
-The Operator CI pipeline is a Tekton pipeline that can be triggered by a partner on on-premise
-infrastructure. The pipeline validates an Operator Bundle, builds it and install it to an OpenShift
-environment. After installation pre-flight tests are executed which validate that the Operator meets
-minimum requirements for Red Hat OpenShift Certification. If all preceding tasks pass the CI pipeline
+The Operator CI pipeline is a Tekton pipeline that can be triggered by a partner using on-premise
+infrastructure. The pipeline validates an Operator Bundle, builds it and installs it to an OpenShift
+environment. After installation, pre-flight tests are executed which validate that the Operator meets
+minimum requirements for Red Hat OpenShift Certification. If all preceding tasks pass, the CI pipeline
 optionally uploads results and submits a pull request to trigger the next stages of the operator
 certification workflow.
 

docs/ci-cd.md

@@ -4,7 +4,7 @@ This project uses GitHub actions for CI (tests, linters) and CD (deployment).
 
 ## Secrets
 
-Both deployment and E2E tests needs GitHub secrets to work properly.
+Both deployment and E2E tests need GitHub secrets to work properly.
 The following secrets should be kept in the repository:
 
 | Secret name | Secret value | Purpose |

docs/developer-guide.md

@@ -202,8 +202,8 @@ git push origin <insert-branch-name>
 
 #### Create an API Key
 
-Contact a Pyxis admin to assist with this request. It must correspond to the
-`org_id` for the certification project under test.
+[File a ticket](https://url.corp.redhat.com/86973d1) with Pyxis admins to assist with this request.
+It must correspond to the `org_id` for the certification project under test.
 
 ## Making Changes to the Pipelines
 
@@ -247,7 +247,7 @@ pip install ".[dev]"
 
 ### Tips
 
-- If adding a new script - don't forget to add the entrypoint to setup.py
+- If adding a new script in the pipeline image - don't forget to add the entrypoint to setup.py
 
 ### Run Unit Tests, Code Style Checkers, etc.
 

docs/pipeline-env-setup.md

@@ -132,7 +132,7 @@ oc create secret generic github-bot-token --from-literal github_bot_token=< BOT
 
 ### Prow-kubeconfig
 Hosted preflight tests are run on the separate cluster. To provision a cluster destined for the tests,
-the pipeline uses a Prowjob. Thus, to start the preflight test, there is needs to be a prow-specific
+the pipeline uses a Prowjob. Thus, to start the preflight test, there needs to be a prow-specific
 kubeconfig.
 - [ProwJob](https://github.com/kubernetes/test-infra/tree/master/prow)
 - [OperatorCI](https://docs.ci.openshift.org/docs/architecture/ci-operator/)

docs/rhc4tp-cluster.md

@@ -12,7 +12,7 @@ to prepare the RHC4TP clusters for use by the pipeline.
     oc create sa operator-pipelines -n default
     ```
 
-1. Create a Kubeconfig for the service account. It should be stored in the repository Ansible Vault.
+1. Create a kubeconfig for the service account. It should be stored in the repository Ansible Vault.
 
     ```bash
     clusterName=dev

scripts/copy-bundle.sh

@@ -7,7 +7,7 @@ usage() {
   [ -i BUNDLE_IMAGE a pull spec to a bundle image to copy ]
   [ -n PKG_NAME the new operator package name ]
   [ -v BUNDLE_VERSION the new operator version ]
-  [ -r OCP_RANGE the new supported OpenShift version range ]
+  [ -r OCP_RANGE the new supported OpenShift version range (see: https://url.corp.redhat.com/6e0ad44) ]
   [ -o OUTPUT_PATH a directory for the generated structure ]
   [ -h show this usage ]" 1>&2
 }