From 6d1ec3fbfc2577a35c6713fd3bc1c68d9eb7f463 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 23 Apr 2025 06:57:41 -0400
Subject: [PATCH] spelling: mismatch

---
 update_security_groups_lambda/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/update_security_groups_lambda/README.md b/update_security_groups_lambda/README.md
index 24a24dc..df3e35d 100644
--- a/update_security_groups_lambda/README.md
+++ b/update_security_groups_lambda/README.md
@@ -104,7 +104,7 @@ Traceback (most recent call last):
   File "/var/task/lambda_function.py", line 29, in lambda_handler
     ip_ranges = json.loads(get_ip_groups_json(message['url'], message['md5']))
   File "/var/task/lambda_function.py", line 50, in get_ip_groups_json
-    raise Exception('MD5 Missmatch: got ' + hash + ' expected ' + expected_hash)
+    raise Exception('MD5 Mismatch: got ' + hash + ' expected ' + expected_hash)
 Exception: MD5 Mismatch: got <b>2e967e943cf98ae998efeec05d4f351c</b> expected 7fd59f5c7f5cf643036cbd4443ad3e4b
 </pre>
 You will see a message indicating there was a hash mismatch. Normally, a real SNS notification from the IP Ranges SNS topic will include the right hash, but because our sample event is a test case representing the event, you will need to update the sample event manually to have the expected hash.