cleanup: remove Travis CI references

SAML-Toolkits · Jan 19, 2025 · c89d78c · c89d78c
1 parent 78bc99c
commit c89d78c
Show file tree

Hide file tree

Showing 3 changed files with 2 additions and 40 deletions.
diff --git a/.coveralls.yml b/.coveralls.yml
@@ -1,4 +1,4 @@
-service_name: travis-ci
+service_name: github
 
 src_dir: lib
 

diff --git a/.travis.yml b/.travis.yml
diff --git a/README.md b/README.md
@@ -198,7 +198,7 @@ A replay attack is basically try to reuse an intercepted valid SAML Message in o
 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 validated and processed. Those values only need
+In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs already 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.