From 8a870bd5352124b22c3cfd4f8b487739c7f4ef1a Mon Sep 17 00:00:00 2001 From: Joshua Levy Date: Sun, 30 Oct 2016 21:07:01 -0700 Subject: [PATCH] Clarify gotcha severities. --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 2c5a632..7672f9a 100644 --- a/README.md +++ b/README.md @@ -114,8 +114,8 @@ Legend - 📒 Marks standard/official AWS pages and docs - 🔹 Important or often overlooked tip -- ❗ Gotcha or warning (where risks or time or resource costs are significant) -- 🔸 Limitation or quirk (where it’s not quite so bad) +- ❗ “Serious” gotcha (used where risks or time or resource costs are significant: critical security risks, mistakes with significant financial cost, or poor architectural choices that are fundamentally difficult to correct) +- 🔸 “Regular” gotcha, limitation, or quirk (used where where consequences are things not working, breaking, or not scaling gracefully) - 📜 Undocumented feature (folklore) - 🐥 Relatively new (and perhaps immature) services or features - ⏱ Performance discussions