Merge pull request #177 from clintonskitson/feature/README_updates

Updated README

README.md

@@ -1,6 +1,8 @@
 # REX-Ray [![GoDoc](https://godoc.org/github.com/emccode/rexray?status.svg)](http://godoc.org/github.com/emccode/rexray) [![Build Status](http://travis-ci.org/emccode/rexray.svg?branch=master)](https://travis-ci.org/emccode/rexray) [![Go Report Card](http://goreportcard.com/badge/emccode/rexray)](http://goreportcard.com/report/emccode/rexray) [![Coverage Status](http://coveralls.io/repos/emccode/rexray/badge.svg?branch=master&service=github&i=3)](https://coveralls.io/github/emccode/rexray?branch=master) [ ![Download](http://api.bintray.com/packages/emccode/rexray/stable/images/download.svg) ](https://dl.bintray.com/emccode/rexray/stable/latest/)
 
-`REX-Ray` provides visibility and management of external or underlying storage for operating systems such as `Linux`. Integrated with popular container platforms such as `Docker` and `Mesos`, its primary purpose is to extend external storage natively to be consumed through containers.  It is additionally available as a Go package, CLI tool, and Linux service which enables it to be used for additional use cases.
+`REX-Ray` provides a vendor agnostic storage orchestration engine.  The primary design goal is to provide persistent storage for `Docker` containers as well as `Mesos` frameworks and tasks.
+
+It is additionally available as a Go package, CLI tool, and Linux service which enables it to be used for additional use cases.
 
 ## Architecture
 It is available as a standalone process today and in the future (0.3) as a distributed model of client-server.  The `client` performs a level of software-defined abstraction of local host processes (request for volume attachment, discovery, format, and mounting of devices) while the `server` provides the necessary abstraction of the control plane for multiple storage platforms.