review fixes

docs/book/src/developer/testing.md

@@ -55,7 +55,7 @@ See [e2e development] for more information on developing e2e tests for CAPI and
 
 ## Running the end-to-end tests locally
 
-Usually, the e2e tests are executed by Prow either pre-submit (on PRs) or periodically on certain branches
+Usually the e2e tests are executed by Prow, either pre-submit (on PRs) or periodically on certain branches
 (e.g. the default branch). Those jobs are defined in the kubernetes/test-infra repository in [config/jobs/kubernetes-sigs/cluster-api](https://github.com/kubernetes/test-infra/tree/master/config/jobs/kubernetes-sigs/cluster-api).
 For development and debugging those tests can also be executed locally.
 
@@ -65,7 +65,7 @@ For development and debugging those tests can also be executed locally.
 
 ### Test execution via ci-e2e.sh
 
-To run the tests locally via command line we can just take a look at the Job configuration and execute the same locally.
+To run a test locally via the command line, you should look at the Prow Job configuration for the test you want to run and then execute the same commands locally.
 For example to run [pull-cluster-api-e2e-main](https://github.com/kubernetes/test-infra/blob/49ab08a6a2a17377d52a11212e6f1104c3e87bfc/config/jobs/kubernetes-sigs/cluster-api/cluster-api-presubmits-main.yaml#L113-L140)
 just execute:
 
@@ -76,7 +76,8 @@ GINKGO_FOCUS="\[PR-Blocking\]" ./scripts/ci-e2e.sh
 ### Test execution via make test-e2e
 
 `make test-e2e` will run e2e tests by using whatever provider images already exist on disk.
-After running `make docker-build-e2e` at least once, this can be used for a faster test run, if there are no provider code changes.
+After running `make docker-build-e2e` at least once, `make test-e2e` can be used for a faster test run, if there are no 
+provider code changes. If the provider code is changed, run `make docker-build-e2e` to update the images.
 
 ### Test execution via IDE