ELI-338: Fixes 'English' and 'Markdown'

Author: shweta-nhs

.github/DEPLOYMENT_README.md

@@ -5,6 +5,7 @@ This directory contains GitHub Actions workflows that automate CI/CD processes f
 ## Workflows Overview
 
 ### 1. dev_sandbox_publish_deploy.yaml
+
 - **Triggers:** On push to `main` branch.
 - **Environments:** Dev (internal-dev), Sandbox.
 - **Steps:**
@@ -16,6 +17,7 @@ This directory contains GitHub Actions workflows that automate CI/CD processes f
   - Notifies a Slack channel on completion.
 
 ### 2. preprod_publish_deploy.yaml
+
 - **Triggers:** Manually via GitHub UI (`workflow_dispatch`).
 - **Inputs:** Tag to promote (defaults to latest).
 - **Environment:** Preprod.
@@ -26,6 +28,7 @@ This directory contains GitHub Actions workflows that automate CI/CD processes f
   - Deploys the spec to the Preprod Proxygen instance.
 
 ### 3. prod_publish_deploy.yaml
+
 - **Triggers:** Manually via GitHub UI (`workflow_dispatch`).
 - **Inputs:** Tag to promote (required).
 - **Environment:** Prod.
@@ -39,6 +42,7 @@ This directory contains GitHub Actions workflows that automate CI/CD processes f
 ## How to Use
 
 ### Dev & Sandbox Deployment
+
 - Push changes to the `main` branch.
 - The workflow will automatically:
   - Deploy to Dev and Sandbox.
@@ -47,20 +51,23 @@ This directory contains GitHub Actions workflows that automate CI/CD processes f
   - Notify Slack.
 
 ### Preprod Deployment
+
 - Go to the **Actions** tab in GitHub.
 - Select **Deploy to Preprod** workflow.
 - Click **Run workflow**.
 - Enter the tag to promote (or use the default `latest`).
 - The workflow will deploy the specified tag to Preprod.
 
 ### Prod Deployment
+
 - Go to the **Actions** tab in GitHub.
 - Select **Deploy to Prod** workflow.
 - Click **Run workflow**.
 - Enter the tag to promote (must match a tag from previous deployments).
 - The workflow will deploy the specified tag to Prod and create a GitHub Release.
 
 ## Notes
+
 - All workflows require secrets to be set in the repository (e.g., `PROXYGEN_PRIVATE_KEY`, `POSTMAN_API_KEY`, `SLACK_WORKFLOW_WEBHOOK_URL`, `GITHUB_TOKEN`).
 - The tags created follow the format `spec-YYYYMMDDHHMMSS` indicative of the deployment time. This is NOT related to the [specification/eligibility-signposting-api](../specification/eligibility-signposting-api.yaml) version.
 - For more details, see the steps in each workflow YAML file.

scripts/config/vale/styles/config/vocabularies/words/accept.txt

@@ -25,3 +25,5 @@ Terraform
 toolchain
 Trufflehog
 uat
+Dev
+Preprod