Vale for prose checking (nhs-england-tools#135)

<!-- markdownlint-disable-next-line first-line-heading -->
## Description

[Vale](https://vale.sh/) is a tool for performing a certain set of style
checks, which this PR introduces for markdown files only. Vale can scan
code comments, but as an initial validation we should limit the scope.

WIP for the moment while I sort out github action integration.

## Context

We want to be sure that our documentation is consistent and readable.  

## Type of changes


- [ ] Refactoring (non-breaking change)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->

- [x] I am familiar with the [contributing
guidelines](../docs/CONTRIBUTING.md)
- [x] I have followed the code style of the project
- [ ] I have added tests to cover my changes
- [x] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming

---

## Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.

- [x] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.

---------

Co-authored-by: Dan Stefaniuk <[email protected]>

Author: regularfry

.github/SECURITY.md

@@ -32,4 +32,4 @@ You can report vulnerabilities here: [https://www.ncsc.gov.uk/information/vulner
 
 ## General Security Enquiries
 
-If you have general enquiries regarding our cyber security, please reach out to us at [[email protected]]([email protected])
+If you have general enquiries regarding our cybersecurity, please reach out to us at [[email protected]]([email protected])

.github/actions/lint-prose/action.yaml

@@ -0,0 +1,9 @@
+name: "Check English usage"
+description: "Check English usage"
+runs:
+  using: "composite"
+  steps:
+    - name: "Check English usage"
+      shell: bash
+      run: |
+        check=branch ./scripts/githooks/check-english-usage.sh

.github/workflows/stage-1-commit.yaml

@@ -66,6 +66,17 @@ jobs:
           fetch-depth: 0 # Full history is needed to compare branches
       - name: "Check markdown format"
         uses: ./.github/actions/check-markdown-format
+  lint-prose:
+    name: "Check English usage"
+    runs-on: ubuntu-latest
+    timeout-minutes: 2
+    steps:
+      - name: "Checkout code"
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0 # Full history is needed to compare branches
+      - name: "Check English usage"
+        uses: ./.github/actions/lint-prose
   lint-terraform:
     name: "Lint Terraform"
     runs-on: ubuntu-latest

README.md

@@ -45,15 +45,15 @@ cd nhs-england-tools/repository-template
 
 The following software packages, or their equivalents, are expected to be installed and configured:
 
-- [docker](https://www.docker.com/) container runtime or a compatible tool, e.g. [podman](https://podman.io/),
+- [Docker](https://www.docker.com/) container runtime or a compatible tool, e.g. [Podman](https://podman.io/),
 - [asdf](https://asdf-vm.com/) version manager,
 - [GNU make](https://www.gnu.org/software/make/) 3.82 or later,
 - [GNU coreutils](https://www.gnu.org/software/coreutils/) and [GNU binutils](https://www.gnu.org/software/binutils/) may be required to build dependencies like Python, which may need to be compiled during installation. For macOS users, this has been scripted and automated by the `dotfiles` project; please see this [script](https://github.com/nhs-england-tools/dotfiles/blob/main/assets/20-install-base-packages.macos.sh) for details,
 - [Python](https://www.python.org/) required to run Git hooks,
-- [jq](https://jqlang.github.io/jq/) a lightweight and flexible command-line JSON processor.
+- [`jq`](https://jqlang.github.io/jq/) a lightweight and flexible command-line JSON processor.
 
 > [!NOTE]<br>
-> The version of GNU make available by default on macOS is earlier than 3.82. You will need to upgrade it or certain `make` tasks will fail. On macOS, you will need [homebrew](https://brew.sh/) installed, then to install `make`, like so:
+> The version of GNU make available by default on macOS is earlier than 3.82. You will need to upgrade it or certain `make` tasks will fail. On macOS, you will need [Homebrew](https://brew.sh/) installed, then to install `make`, like so:
 >
 > ```shell
 > brew install make

docs/adr/ADR-001_Use_git_hook_and_GitHub_action_to_check_the_editorconfig_compliance.md

@@ -106,7 +106,7 @@ This option is an extension built upon option 2a.
 - Pros
   - Usage of a GitHub native functionality
 - Cons
-  - Reliance on the GitHub DSL (coding in yaml) may lead to less portable solution
+  - Reliance on the GitHub DSL (coding in YAML) may lead to less portable solution
   - Implementation of the functionality has to be duplicated for the git hook
 
 ### Outcome

docs/adr/ADR-002_Scan_repository_for_hardcoded_secrets.md

@@ -1,4 +1,4 @@
-# ADR-002: Scan repository for hardcoded secrets
+# ADR-002: Scan repository for hard-coded secrets
 
 >|              |                                                               |
 >| ------------ | ------------------------------------------------------------- |
@@ -10,7 +10,7 @@
 
 ---
 
-- [ADR-002: Scan repository for hardcoded secrets](#adr-002-scan-repository-for-hardcoded-secrets)
+- [ADR-002: Scan repository for hard-coded secrets](#adr-002-scan-repository-for-hard-coded-secrets)
   - [Context](#context)
   - [Decision](#decision)
     - [Assumptions](#assumptions)
@@ -42,7 +42,7 @@ Within NHS England, we are observing an adoption of the `gitleaks` tool, which i
 
 There are three options presented in this decision record.
 
-1. [git-secrets](https://github.com/awslabs/git-secrets)
+1. [Git-secrets](https://github.com/awslabs/git-secrets)
 
    - Repository metadata
      - Contributions
@@ -66,9 +66,9 @@ There are three options presented in this decision record.
    - Cons
      - Rules and exclusion patterns are not easy to manage as no comments or metadata are allowed in the definition
      - No pre-backed Docker image
-     - Activity of the repo has dropped (last commit a while ago)
+     - Activity of the repository has dropped (last commit a while ago)
 
-2. [trufflehog](https://github.com/trufflesecurity/trufflehog)
+2. [Trufflehog](https://github.com/trufflesecurity/trufflehog)
 
    - Repository metadata
      - Contributions
@@ -93,7 +93,7 @@ There are three options presented in this decision record.
    - Cons
      - [AGPL-3.0](https://choosealicense.com/licenses/agpl-3.0/) licence comes with conditions
 
-3. [gitleaks](https://github.com/gitleaks/gitleaks)
+3. [Gitleaks](https://github.com/gitleaks/gitleaks)
 
    - Repository metadata
 

docs/adr/ADR-XXX_Agree_CICD_pipeline_structure.md

@@ -55,7 +55,7 @@ Requirements:
 
 ### Assumptions
 
-Summarise the underlying assumptions in the environment in which you make the decision. This could be related to technology changes, forecast of the monetary and non-monetary costs, further delivery commitments, impactful external drivers etc., and any known unknowns that translate to risks.
+Summarise the underlying assumptions in the environment in which you make the decision. This could be related to technology changes, forecast of the monetary and non-monetary costs, further delivery commitments, impact from external drivers etc., and any known unknowns that translate to risks.
 
 ### Drivers
 

docs/adr/ADR-nnn_Any_Decision_Record_Template.md

@@ -32,7 +32,7 @@ Describe the context and the problem statement. Is there a relationship to other
 
 ### Assumptions
 
-Summarise the underlying assumptions in the environment in which you make the decision. This could be related to technology changes, forecast of the monetary and non-monetary costs, further delivery commitments, impactful external drivers etc., and any known unknowns that translate to risks.
+Summarise the underlying assumptions in the environment in which you make the decision. This could be related to technology changes, forecast of the monetary and non-monetary costs, further delivery commitments, impact from external drivers etc., and any known unknowns that translate to risks.
 
 ### Drivers
 

docs/adr/assets/ADR-003/examples/nodejs/README.md

@@ -26,4 +26,4 @@ $ yarn start
       ...
 ```
 
-See the [example (main.ts)](./main.ts) implementation. This script has been written to illustrate the concept in a clear and simple way. It is not a production ready code.
+See the [example (`main.ts`)](./main.ts) implementation. This script has been written to illustrate the concept in a clear and simple way. It is not a production ready code.

docs/developer-guides/Bash_and_Make.md

@@ -140,7 +140,7 @@ VERBOSE=1 scripts/shellscript-linter.sh
 
 ### Scripts
 
-Most scripts provided with this repository template can utilise tools installed on your `PATH` if they are available or run them from within a Docker container. To force a script to use Docker, the `FORCE_USE_DOCKER` variable is provided. This feature increases configurability of the development environment, allowing you to use custom tooling by default if present on the command-line path. Here is an example of how to use it:
+Most scripts provided with this repository template can use tools installed on your `PATH` if they are available or run them from within a Docker container. To force a script to use Docker, the `FORCE_USE_DOCKER` variable is provided. This feature allows you to use custom tooling if it is present on the command-line path. Here is how to use it:
 
 ```shell
 FORCE_USE_DOCKER=1 scripts/shellscript-linter.sh