markdown fixes

Author: davethepunkyone

docs/getting-started/1_Understanding_Playwright_Python.md

@@ -71,7 +71,9 @@ through a browser to generate the code for a test. You can access the `codegen`
 
 This will bring up a browser window, with the Playwright code generator running alongside, like so:
 
+<!-- vale off -->
 ![An image of the Playwright codegen tool](./img/1-codegen.png "Playwright codegen")
+<!-- vale on -->
 
 When using the `codegen` tool, it is recommended to do the following:
 
@@ -92,5 +94,5 @@ understanding of how to construct tests using Playwright Python, but you will so
 
 [Chromium](https://www.chromium.org/Home/) is one of the open source browser that comes bundled with Playwright on install (if using the instructions
 within the [README](../../README.md) of this blueprint) but also more importantly, serves as the base code for both Google Chrome and Microsoft Edge.
-Whilst this doesn't replace the need to test in independent browsers as required, Chromium provides the opportunity to do some initial broad testing 
+Whilst this doesn't replace the need to test in independent browsers as required, Chromium provides the opportunity to do some initial broad testing
 which should largely be representative of the user experience with Chrome and Edge respectively.

docs/getting-started/2_Blueprint_File_Breakdown.md

@@ -12,7 +12,7 @@ This guide outlines the breakdown of this blueprint, and specifically the files
     - [`tests/`](#tests)
     - [`pages/`](#pages)
     - [`utils/`](#utils)
-  - [Directories \& Files Specific For This Repo](#directories--files-specific-for-this-repo)
+  - [Directories \& Files Specific For This Repository](#directories--files-specific-for-this-repository)
 
 ## Directories & Files Directly Impacting Tests
 
@@ -52,14 +52,13 @@ We want this directory to be treated as a [Python package](https://docs.python.o
 
 > NOTE: If you write a utility class for your own project that you think other projects may benefit from and can be applied in a generic way, please raise a [Feature Request](https://github.com/nhs-england-tools/playwright-python-blueprint/issues/new/choose) as we welcome any contributions of this fashion.
 
-## Directories & Files Specific For This Repo
+## Directories & Files Specific For This Repository
 
-The following directories and files are specific for this repository (playwright-python-blueprint), and may require modification or removal
-if transferring this code into a new repository.
+The following directories and files are specific for this repository, and may require modification or removal if transferring this code into a new repository.
 
-- `.github/`: This directory has the code used to manage our repo and pipelines including CI/CD checks. You may find some useful for your own repo, especially if you are using GitHub to manage your code.
+- `.github/`: This directory has the code used to manage our repository and pipelines including CI/CD checks. You may find some useful for your own repository, especially if you are using GitHub to manage your code.
 - `.vscode/`: This directory houses the default recommended configuration and settings for VSCode, if you use it as an IDE.
 - `docs/`: This directory houses the documentation for this repo (including documents like this one).
 - `scripts/`: This directory houses the scripts used by this repo, primarily as part of the CI/CD checks.
-- `tests_utils/`: This directory houses the unit tests for the utilities provided by this repo. You may want to copy these over if you want to ensure utilities are behaving as expected.
+- `tests_utils/`: This directory houses the unit tests for the utilities provided by this repository. You may want to copy these over if you want to ensure utilities are behaving as expected.
 - `.editorconfig`, `.gitattributes`, `.gitignore`, `.gitleaks.toml`, `.gitleaksignore`: These files are configuration for git, and quality and security checks provided via the CI/CD checks.