diff --git a/.travis.yml b/.travis.yml
index d28e6f5..bd223b5 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,17 +1,9 @@
 language: ruby
 rvm:
-- 2.3.3
+- 2.4
 branches:
   only:
   - gh-pages
 script:
 - bundle exec jekyll build --config _config.yml
-- bundle exec htmlproofer ./_site --external_only --only-4xx --url-ignore \"/#.*/,/getting-started\"
-notifications:
-  slack:
-    rooms:
-      - secure: PkPpJ4ICMhdm3lv7iQ0Xs7hU1Qca5FA8nceYJ8v1KE72keshYirKidIMdvCMgBzT9D2lWJ9uzqSGN89TF3rwPnijB6Kl5x9bqEcVBPj/VYETfEzXt7NQ0WhuxEo1rwnjV8Vx6SqKHyoW4o2ojPOhS6vR7fMYXvCSqPDGJ9WPeNHAYSoaba7+znrqqxwNiNHoNLa5siiraBxCjPArKuaeYhxsDwjTp20cGuittd2qs1oMgnCXtRUmMnEC7MMnrNn3n/DqQ/LZDcoN/YASK6GqizPN8hEx7PKjf7WXsKsT3qTQkUA6RO1PX4Swuh0Hi2qGgnXBzgF8wFjnmJIqPG408+XHOQIsely+Dr+Gd+62DlYdReaxydMyYfdcf2rzRMJScWQP2hNzfU7NNFhUeil0iLpzMDftZDwvcpJUEA9GLc9s3sFufyWPJyFNnVjKo0FOjkyhvCmX26fmQfAdcq7Tbs/jNR7NAoHRtjF+POD17P/6TtVX8MqV7l7qRM4KzQQt7CCmDi6hpXgZtsRHkNnbTxJU5Hxix1TeI+oVOjFnrzygDjOvaVlMoIyrphMqAnSQDnH+ZG9bCsYmqCV4w/vKrErD0LUDHViZK82oxc9ERUfyWX7ae8zpQGd/ctBqiHyiGQsJ0FodPQlguun+vbdXfBAWnxltc3zQt+BYvJkydew=
-    on_success: never
-    on_failure: always
-    template:
-      - "Build <%{build_url}|#%{build_number}> (<%{compare_url}|%{commit}>) of %{repository_slug}@%{branch} by %{author} %{result}. Click on the build number to see details."
+- bundle exec htmlproofer ./_site --external_only --only-4xx --url-ignore \"/#.*/,/getting-started\"
\ No newline at end of file
diff --git a/_blogs/2018-03-08-enabling-ios-xr-on-third-party-network-hardware.md b/_blogs/2018-03-08-enabling-ios-xr-on-third-party-network-hardware.md
index 84358be..16bbf94 100644
--- a/_blogs/2018-03-08-enabling-ios-xr-on-third-party-network-hardware.md
+++ b/_blogs/2018-03-08-enabling-ios-xr-on-third-party-network-hardware.md
@@ -164,7 +164,7 @@ There are four primary steps to enable a NOS on third-party hardware:
          </div>
           with hardware specific hooks implemented in hardware platform  specific directories:  
          <div style="word-wrap: break-word;">
-         <blockquote><p><a href="https://github.com/opencomputeproject/OpenNetworkLinux/tree/master/packages/platforms/accton/x86-64/x86-64-accton-as7816-64x/onlp/builds/src/module/src">https://github.com/opencomputeproject/OpenNetworkLinux/tree/master/packages/platforms/accton/x86-64/x86-64-accton-as7816-64x/onlp/builds/src/module/src</a>
+         <!-- <blockquote><p><a href="https://github.com/opencomputeproject/OpenNetworkLinux/tree/master/packages/platforms/accton/x86-64/x86-64-accton-as7816-64x/onlp/builds/src/module/src">https://github.com/opencomputeproject/OpenNetworkLinux/tree/master/packages/platforms/accton/x86-64/x86-64-accton-as7816-64x/onlp/builds/src/module/src</a> -->
          </p>
          </blockquote>
          </div>  
diff --git a/_blogs/2018-05-07-ncs-5500-buffering-architecture.md b/_blogs/2018-05-07-ncs-5500-buffering-architecture.md
index 7a0490f..29f2e7e 100644
--- a/_blogs/2018-05-07-ncs-5500-buffering-architecture.md
+++ b/_blogs/2018-05-07-ncs-5500-buffering-architecture.md
@@ -14,15 +14,15 @@ tags:
   - cisco
 ---
 
-{% include toc icon="table" title="NCS 5500 Buffering Architecture" %}
+<!-- {% include toc icon="table" title="NCS 5500 Buffering Architecture" %}
 
-{% include base_path %}
+{% include base_path %} -->
 
-<meta http-equiv="refresh" content="0; 
-url=https://xrdocs.io/ncs5500/blogs/2018-05-07-ncs-5500-buffering-architecture/">
+<!-- <meta http-equiv="refresh" content="0; 
+url=https://xrdocs.io/ncs5500/blogs/2018-05-07-ncs-5500-buffering-architecture/"> -->
 
-<link rel="canonical" 
-href="https://xrdocs.io/ncs5500/blogs/2018-05-07-ncs-5500-buffering-architecture/" />
+<!-- <link rel="canonical" 
+href="https://xrdocs.io/ncs5500/blogs/2018-05-07-ncs-5500-buffering-architecture/" /> -->
 
 The NCS 5500 uses an innovative design to provide deep buffering while maintaining high performance and power efficiency. This paper explores this design and shows its strengths over traditional forwarding architectures. It also will address criticism of these optimizations coming from other vendors.
 
diff --git a/_tutorials/ncs5500-routing-in-vrf.md b/_tutorials/ncs5500-routing-in-vrf.md
index 9ccb2d3..a0aa28d 100644
--- a/_tutorials/ncs5500-routing-in-vrf.md
+++ b/_tutorials/ncs5500-routing-in-vrf.md
@@ -571,7 +571,7 @@ Per-VRF
  - Potential forwarding loop during local traffic diversion to support PIC
  - No support for EIBGP multipath
 
-A lot of litterature is available for free on places like [CiscoLive (London 2013 BRKIPM-2265)](http://d2zmdbbm9feqrf.cloudfront.net/2013/eur/pdf/BRKIPM-2265.pdf) (pdf file).
+<!-- A lot of litterature is available for free on places like [CiscoLive (London 2013 BRKIPM-2265)](http://d2zmdbbm9feqrf.cloudfront.net/2013/eur/pdf/BRKIPM-2265.pdf) (pdf file). -->
 
 Let's verify that per-ce allocation is not changing anything in the resource usage: