Wrapping and wording for scenarios/ci.

rshipp · rshipp · commit 7a65571383a9 · 2014-06-17T14:08:47.000-06:00
diff --git a/docs/scenarios/ci.rst b/docs/scenarios/ci.rst
@@ -26,16 +26,21 @@ engine. Use it.
 
 Buildbot
 --------
+
 `Buildbot <http://docs.buildbot.net/current/>`_ is a Python system to
 automate the compile/test cycle to validate code changes.
 
 
 Mule
 -----
 
-`Mule <http://www.mulesoft.org/documentation/display/current/Mule+Fundamentals>`_  is a lightweight integration platform that enables you to connect anything, anywhere. 
-You can use Mule to intelligently manage message routing, data mapping, orchestration, reliability, security, and scalability between nodes. 
-Plug other systems and applications into Mule and let it handle all the communication between systems, enabling you to track and monitor everything that happens. 
+`Mule <http://www.mulesoft.org/documentation/display/current/Mule+Fundamentals>`_
+is a lightweight integration platform that enables you to connect anything,
+anywhere. You can use Mule to intelligently manage message routing, data
+mapping, orchestration, reliability, security and scalability between nodes.
+Plug other systems and applications into Mule and let it handle all the
+communication between systems, enabling you to track and monitor everything
+that happens. 
 
 
 Tox
@@ -56,6 +61,7 @@ which provides the following features:
 
 Travis-CI
 ---------
+
 `Travis-CI <https://travis-ci.org/>`_ is a distributed CI server which builds tests
 for open source projects for free. It provides multiple workers to run Python tests
 on and seamlessly integrates with GitHub. You can even have it comment on your Pull
@@ -79,12 +85,13 @@ example content::
         - master
 
 
-This will get your project tested on all the listed Python versions by running the given
-script and only build the master branch. There are a lot more options you can enable, like
-notifications, before and after steps and much more. The
-`travis-ci docs <http://about.travis-ci.org/docs/>`_ explain all of those and are very
-thorough.
+This will get your project tested on all the listed Python versions by
+running the given script, and will only build the master branch. There are a
+lot more options you can enable, like notifications, before and after steps
+and much more. The `travis-ci docs <http://about.travis-ci.org/docs/>`_
+explain all of these options, and are very thorough.
 
 In order to activate testing for your project, go to `the travis-ci site <https://travis-ci.org/>`_
-and login with your GitHub account. Then activate your project in your profile settings and that's
-it. From now on, your project's tests will be run on every push to GitHub.
+and login with your GitHub account. Then activate your project in your
+profile settings and you're ready to go. From now on, your project's tests
+will be run on every push to GitHub.
