[EDI] Remediating a leaked secret in your repository (#59313)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: sabrowning1

content/code-security/tutorials/remediate-leaked-secrets/remediating-a-leaked-secret.md

@@ -23,7 +23,7 @@ Secrets, such as API keys, tokens and credentials, can pose significant security
 
 You should consider any leaked secret to be immediately compromised and it is essential that you undertake proper remediation steps, such as revoking the secret. Simply removing the secret from the codebase, pushing a new commit, or deleting and recreating the repository do not prevent the secret from being exploited.
 
-This how-to walks you through what to do if you've accidentally committed a secret to your repository, or if you've been alerted to a secret leak in your repository.
+This tutorial walks you through what to do if you've accidentally committed a secret to your repository, or if you've been alerted to a secret leak in your repository.
 
 ### Prerequisites