Adjust wrapping with Rewrap

README.md

@@ -1,30 +1,34 @@
 # Opsani CLI
 
-Opsani CLI is cloud optimization in your terminal. It brings a suite of tools for 
-configuring & deploying Servos, managing optimization runs, and interacting with the optimization engine
-to your command line.
+Opsani CLI is cloud optimization in your terminal. It brings a suite of tools
+for configuring & deploying Servos, managing optimization runs, and interacting
+with the optimization engine to your command line.
 
 ## Status
 
 Opsani CLI is an early stage project in active development.
 
 We need your feedback to determine how best to evolve the tool.
 
-If you run into any bugs or think of a feature you'd like to see, please file a ticket on GitHub.
+If you run into any bugs or think of a feature you'd like to see, please file a
+ticket on GitHub.
 
 ## Usage
 
-The CLI currently supports controling optimization lifecycle, managing configuration, and building
-Servo artifacts for connecting new apps to Opsani for optimization.
+The CLI currently supports controling optimization lifecycle, managing
+configuration, and building Servo artifacts for connecting new apps to Opsani
+for optimization.
 
-To perform any meaningful work, you must first initialize the client via `opsani init` and supply
-details about your app and API token.
+To perform any meaningful work, you must first initialize the client via `opsani
+init` and supply details about your app and API token.
 
-Once initialized, you can work with the app using the subcommands of `opsani app`.
+Once initialized, you can work with the app using the subcommands of `opsani
+app`.
 
-The `opsani discover` commands is an evolving system for auto-discovering the environment
-to facilitate rapid integration with the optimization engine. Discovery connects to Docker,
-Kubernetes, and Prometheus and can execute over an SSH channel via `opsani discover --host ssh://user@host`.
+The `opsani discover` commands is an evolving system for auto-discovering the
+environment to facilitate rapid integration with the optimization engine.
+Discovery connects to Docker, Kubernetes, and Prometheus and can execute over an
+SSH channel via `opsani discover --host ssh://user@host`.
 
 Help is available via `opsani --help`.
 
@@ -36,26 +40,29 @@ Docs are forthcoming. Utilize the CLI help and read the code for now.
 
 Versioned releases are coming soon. Please build from source in the interim.
 
-`make install` is available on Unixy platforms and will drop the binary into /usr/local/bin. 
+`make install` is available on Unixy platforms and will drop the binary into
+/usr/local/bin. 
 
 ## Development
 
-Opsani CLI is implemented in Golang and utilizes a handful of well established libraries including
-Cobra, Viper, and Resty. Anyone reasonably well versed in Go should have no trouble following along.
+Opsani CLI is implemented in Golang and utilizes a handful of well established
+libraries including Cobra, Viper, and Resty. Anyone reasonably well versed in Go
+should have no trouble following along.
 
-There is a Makefile for running typical tasks but `go run .` is a great way to poke around.
+There is a Makefile for running typical tasks but `go run .` is a great way to
+poke around.
 
 ## Testing
 
-Opsani CLI has extensive automated test coverage. Unit tests exist
-alongside the code under test and there are integration tests in 
-the `integration` directory.
+Opsani CLI has extensive automated test coverage. Unit tests exist alongside the
+code under test and there are integration tests in the `integration` directory.
 
-Testing assertions and mocks are provided by the [Testify](https://github.com/stretchr/testify) library. Tests are organized using the 
-`testify.suite` package to provide familiar xUnit testing primitives.
+Testing assertions and mocks are provided by the
+[Testify](https://github.com/stretchr/testify) library. Tests are organized
+using the `testify.suite` package to provide familiar xUnit testing primitives.
 
-The local test package contains shared testing helpers useful in both
-unit and integration test scenarios.
+The local test package contains shared testing helpers useful in both unit and
+integration test scenarios.
 
 Tests can be run via the Makefile:
 
@@ -65,14 +72,13 @@ Tests can be run via the Makefile:
 
 ### Integration Tests
 
-The integration test harness functions by building the `opsani` binary,
-copying it into a temp directory, and then interacting with it as a 
-subprocess and evaluating stdout, stderr, and exit code status.
+The integration test harness functions by building the `opsani` binary, copying
+it into a temp directory, and then interacting with it as a subprocess and
+evaluating stdout, stderr, and exit code status.
 
-API interactions are mocked locally via an `http.httptest` server that
-runs in the test executor parent process. The `--base-url` flag is used
-to direct the CLI to interact with the test API server rather than the 
-Opsani API.
+API interactions are mocked locally via an `http.httptest` server that runs in
+the test executor parent process. The `--base-url` flag is used to direct the
+CLI to interact with the test API server rather than the Opsani API.
 
 ## License