From 3305ba9724be81a6adc45f1edab618d0e96a07b2 Mon Sep 17 00:00:00 2001
From: Jeff Puckett <84726901+jpuckett-di@users.noreply.github.com>
Date: Wed, 17 Jul 2024 14:38:54 -0400
Subject: [PATCH] doc fix typos

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 020da37c..027d9330 100644
--- a/README.md
+++ b/README.md
@@ -191,14 +191,14 @@ a trusted and expected URL.
 Read more about Open Redirect [CWE-601](https://cwe.mitre.org/data/definitions/601.html).
 
 
-### Avoiding Reply attacks ###
+### Avoiding Replay attacks ###
 
-A reply attack is basically try to reuse an intercepted valid SAML Message in order to impersonate a SAML action (SSO or SLO).
+A replay attack is basically try to reuse an intercepted valid SAML Message in order to impersonate a SAML action (SSO or SLO).
 
 SAML Messages have a limited timelife (NotBefore, NotOnOrAfter) that
 make harder this kind of attacks, but they are still possible.
 
-In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs alredy valdidated and processed. Those values only need
+In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs alredy validated and processed. Those values only need
 to be stored the amount of time of the SAML Message life time, so
 we don't need to store all processed message/assertion Ids, but the most recent ones.