Corrected some typos in the docs

README.md

@@ -172,7 +172,7 @@ Context "When route table is created" -Tag route-table-create {
 Also, the test results are very easy to grasp, by just looking at the detailed output of [Invoke-Pester](https://github.com/pester/Pester#simple-and-advanced-interface):
 ![Test results generated by Pester](./docs/pester-test-results.png)
 
-Finally, Pester tests can also run during [continuous integration](https://martinfowler.com/articles/continuousIntegration.html) as part of your DevOps pipeline. Following an example using [GitHub Actions](https://github.com/features/actions) (See: [test-policies.yml](./.github/workflows/test-policies.yml))::
+Finally, Pester tests can also run during [continuous integration](https://martinfowler.com/articles/continuousIntegration.html) as part of your DevOps pipeline. Following an example using [GitHub Actions](https://github.com/features/actions) (See: [test-policies.yml](./.github/workflows/test-policies.yml)):
 
 ```yaml
 - name: Test Azure Policies
@@ -451,7 +451,7 @@ Before going into the steps to setup this repository with your GitHub account us
 
 
 ## FAQ
-### Should I run the tests to validate a pull request?
+### Should we run the tests to validate a pull request?
 Running the tests can take a few minutes up to some hours. The long duration is mainly caused by waiting for policy compliance scans and remediations to complete. So while you certainly can run the tests to validate your pull request, it is not advisable since a pull request should provide your developers feedback in just a couple of minutes to reduce their unproductive waiting time. That being said, running them as part of your [continuous integration](https://martinfowler.com/articles/continuousIntegration.html) on the main branch is what you should aim for.
 
 ### The tests take a long time to complete, can we speed things up?