diff --git a/.coveralls.yml b/.coveralls.yml
index 173ff356..cb6cdeb2 100644
--- 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
deleted file mode 100644
index f3c0a43e..00000000
--- a/.travis.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-language: php
-dist: trusty
-php:
-  - 5.5
-  - 5.6
-
-matrix:
-  fast_finish: true
-  include:
-    - php: 5.3
-      dist: precise
-    - php: 5.4
-      dist: precise
-
-env:
- - TRAVIS=true
-
-before_install:
- - composer self-update || true
- - composer install --prefer-source --no-interaction
-
-before_script:
-  - phpenv config-rm xdebug.ini
-
-script:
-  - vendor/bin/phpunit
-  - php vendor/bin/phpcpd --exclude tests --exclude vendor .
-  - php vendor/bin/phploc . --exclude vendor
-  - php vendor/bin/phploc lib/.
-  - mkdir -p tests/build/dependences
-  - php vendor/bin/pdepend --summary-xml=tests/build/logs/dependence-summary.xml --jdepend-chart=tests/build/dependences/jdepend.svg --overview-pyramid=tests/build/dependences/pyramid.svg  lib/.
-  - php vendor/bin/phpcs --standard=tests/ZendModStandard lib/Saml2 demo1 demo2 demo-old endpoints tests/src
-
-after_script:
-  - export TRAVIS=https://travis-ci.org/onelogin/php-saml
-  - echo $TRAVIS
-  - echo $TRAVIS_JOB_ID
-  - php vendor/bin/coveralls --config .coveralls.yml -v
diff --git a/README.md b/README.md
index fc0c25eb..8c6407af 100644
--- 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.