From b3ef2f99e8612fb443d39052ef7a5c173e737932 Mon Sep 17 00:00:00 2001
From: sbanszky <sbanszky@noreply.localhost>
Date: Sat, 7 Feb 2026 21:55:29 +0000
Subject: [PATCH] Update security/vault-like.prompt

---
 security/vault-like.prompt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/security/vault-like.prompt b/security/vault-like.prompt
index 742dc10..babf6d5 100644
--- a/security/vault-like.prompt
+++ b/security/vault-like.prompt
@@ -30,7 +30,7 @@ For each item below, mark as PUBLIC / INTERNAL / SENSITIVE / SECRET and explain:
 - Logs, traces, metrics labels, query samples
 - Migration tooling credentials
 - Read replicas endpoints
-Also: list “gray areas” (things people think are public but shouldn’t be).
+Also: list “gray areas” (things people think are public but shouldn't be).
 
 C) Prerequisites / Baseline Controls
 1. Identity & access:
@@ -72,7 +72,7 @@ G) Practical Implementation Playbooks
 - Incident response steps for secret compromise (rotate, revoke, invalidate sessions)
 
 H) Final Deliverable
-- A concise “Top 10 Do/Don’t”
+- A concise “Top 10 Do/Don't”
 - A checklist suitable for an engineering team to implement
 
 STYLE