dump travis to 1.8 (#606)

2 files changed, 6 insertions, 7 deletions

diff --git a/.travis.yml b/.travis.yml
index e7e198ece..3a3f1aa26 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -7,7 +7,7 @@ services:
 
 language: go
 go:
-  - 1.7
+  - 1.8
 
 go_import_path: github.com/coredns/coredns
 
diff --git a/README.md b/README.md
index e8c1dea5e..074b98c5d 100644
--- a/README.md
+++ b/README.md
@@ -7,8 +7,9 @@
 
 CoreDNS is a DNS server that started as a fork of [Caddy](https://github.com/mholt/caddy/). It has
 the same model: it chains middleware. In fact it's so similar that CoreDNS is now a server type
-plugin for Caddy. CoreDNS is also a [Cloud Native Computing Foundation](https://cncf.io) inception
-level project.
+plugin for Caddy.
+
+CoreDNS is also a [Cloud Native Computing Foundation](https://cncf.io) inception level project.
 
 CoreDNS is the successor to [SkyDNS](https://github.com/skynetservices/skydns). SkyDNS is a thin
 layer that exposes services in etcd in the DNS. CoreDNS builds on this idea and is a generic DNS
@@ -17,10 +18,8 @@ server that can talk to multiple backends (etcd, kubernetes, etc.).
 CoreDNS aims to be a fast and flexible DNS server. The keyword here is *flexible*: with CoreDNS you
 are able to do what you want with your DNS data. And if not: write some middleware!
 
-CoreDNS can listen for DNS request coming in over UDP/TCP (go'old DNS), TLS
-([RFC 7858](https://tools.ietf.org/html/rfc7858)) and gRPC (not
-a standard.
-
+CoreDNS can listen for DNS request coming in over UDP/TCP (go'old DNS), TLS ([RFC
+7858](https://tools.ietf.org/html/rfc7858)) and gRPC (not a standard.
 
 Currently CoreDNS is able to: