resolving markdown recommendations

Author: walteck

practices/guides/commit-purge.md

@@ -2,13 +2,13 @@
 
 ## Overview
 
-There are multiple steps required to ensure sensitive data committed to a GitHub hosted Git repository is fully removed. 
+There are multiple steps required to ensure sensitive data committed to a GitHub hosted Git repository is fully removed.
 
-Engineering teams must take all necessary precautions to ensure that sensitive data does not leak into Source Control Management Systems. This includes secrets being pushed to a remote branch, as well as merging into the default branch. Teams must consider **any** secret posted to a branch of a public repository as compromised and must take necessary steps to revoke and rotate this secret. For Private and Internal repositories teams must still treat leaked credentials as compromised and revoke and rotate them. 
+Engineering teams must take all necessary precautions to ensure that sensitive data does not leak into Source Control Management Systems. This includes secrets being pushed to a remote branch, as well as merging into the default branch. Teams must consider **any** secret posted to a branch of a public repository as compromised and must take necessary steps to revoke and rotate this secret. For Private and Internal repositories teams must still treat leaked credentials as compromised and revoke and rotate them.
 
-Teams must also review their Near Miss reporting requirements and ensure that necessary steps are taken. 
+Teams must also review their Near Miss reporting requirements and ensure that necessary steps are taken.
 
-Teams must ensure that a [Secret scanner](https://github.com/NHSDigital/software-engineering-quality-framework/tree/main/tools/nhsd-git-secrets) is enabled on their repositories. 
+Teams must ensure that a [Secret scanner](https://github.com/NHSDigital/software-engineering-quality-framework/tree/main/tools/nhsd-git-secrets) is enabled on their repositories.
 
 Teams must also ensure that developers follow standard processes to ensure any pre-commit hooks are enabled and enforced to reduce the risk of sensitive information being accidentally published. Teams should also contribute to the rule set for these tools to ensure secrets are identified correctly.