Update README.md
diff --git a/README.md b/README.md
index d54357a..9e63134 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,6 @@
# gvt, the go vendoring tool
-[](https://godoc.org/github.com/FiloSottile/gvt) [](https://travis-ci.org/FiloSottile/gvt)
+[](https://godoc.org/github.com/FiloSottile/gvt)
+[](https://travis-ci.org/FiloSottile/gvt)
`gvt` is a simple Go vendoring tool made for the
[GO15VENDOREXPERIMENT](https://docs.google.com/document/d/1Bz5-UB7g2uPBdOx-rw5t9MxJwkfpx90cqG9AFL0JAYo/edit),
@@ -8,19 +9,20 @@
It lets you easily and "idiomatically" include external dependencies in your repository to get
reproducible builds.
- * No need to learn a new tool or format! You already know how to use `gvt`: just run `gvt fetch`
- when and like you would run `go get`. You can imagine what `gvt update` and `gvt delete` do.
+ * No need to learn a new tool or format!
+ You already know how to use `gvt`: just run `gvt fetch` when and like you would run `go get`.
+ You can imagine what `gvt update` and `gvt delete` do.
- * No need to change how you build your project! `gvt` downloads packages to `./vendor/...`. With
- `GO15VENDOREXPERIMENT=1` the stock Go compiler will find and use those dependencies
- automatically (without import path or GOPATH changes).
+ * No need to change how you build your project!
+ `gvt` downloads packages to `./vendor/...`. With `GO15VENDOREXPERIMENT=1` the stock Go compiler
+ will find and use those dependencies automatically (without import path or GOPATH changes).
- * No need to manually chase, copy or cleanup dependencies! `gvt` works recursively as you would
- expect, and lets you update vendored dependencies. It also writes a manifest to
- `./vendor/manifest` and never touches your system GOPATH. Finally, it strips the VCS metadata so
- that you can commit the vendored source cleanly.
+ * No need to manually chase, copy or cleanup dependencies!
+ `gvt` works recursively as you would expect, and lets you update vendored dependencies. It also
+ writes a manifest to `./vendor/manifest` and never touches your system GOPATH. Finally, it
+ strips the VCS metadata so that you can commit the vendored source cleanly.
- * No need for your users and occasional contributors to install **or even know about** gvt!
+ * No need for your users and occasional contributors to install **or even know about** gvt!
Packages whose dependencies are vendored with `gvt` are `go build`-able and `go get`-able out of
the box by Go 1.5 with `GO15VENDOREXPERIMENT=1` set.
@@ -43,7 +45,7 @@
You know how to use `go get`? That's how you use `gvt fetch`.
```
-# This will fetch the dependency into the /vendor folder.
+# This will fetch the dependency into the ./vendor folder.
$ gvt fetch github.com/fatih/color
2015/09/05 02:38:06 fetching recursive dependency github.com/mattn/go-isatty
2015/09/05 02:38:07 fetching recursive dependency github.com/shiena/ansicolor
