diff --git a/website/content/docs/use-cases.mdx b/website/content/docs/use-cases.mdx
index ec651e9ea1..6eabb9f146 100644
--- a/website/content/docs/use-cases.mdx
+++ b/website/content/docs/use-cases.mdx
@@ -14,7 +14,7 @@ This page describes common Vault use cases and provides related resources that c
 
 ## General secret storage
 
-As workloads become more and more ephemeral and short-lived, having long-lived static credentials pose a big security threat vector. What if credentials are accidentally leaked, or an employee leaves with their post it notes that contain the AWS access key, or someone checks their S3 access token to a public GH repo?
+As workloads become more and more ephemeral and short-lived, having long-lived static credentials pose a big security threat vector. What if credentials are accidentally leaked, or an employee leaves with their post it notes that contain the AWS access key, or someone checks their S3 access token into a public GH repo?
 With Vault, you can generate short-lived, just-in-time credentials that are automatically revoked when their time expires. This means users and security teams do not have to worry about manually revoking or changing these credentials.
 
 ### Static secrets