Try moving the integrations paragraph to the end

aroben · aroben · commit 6342381ee9ea · 2015-09-03T15:13:10.000-04:00
diff --git a/content/changes/2015-09-03-ensure-your-app-is-ready-for-protected-branches.md b/content/changes/2015-09-03-ensure-your-app-is-ready-for-protected-branches.md
@@ -14,17 +14,6 @@ fail unless the that commit (or another commit with the same [Git tree][tree])
 has a [Status][statuses] in the `success` state for each required status
 check.
 
-Required status checks can be used for more than just ensuring your branch
-passes Continuous Integration tests before merging. For example, you could
-write a Status integration that only posts a `success` Status when the pull
-request’s author has signed your project’s Contributor License Agreement. Or
-you could write one that only posts a `success` Status when three or more
-members of your `@initech/senior-engineers` team have left a comment saying
-they’ve reviewed the changes. Combined with required status checks,
-integrations like these can help contributors to follow your project’s
-conventions. See our [Status API guide][guide] to learn how to create
-integrations like these.
-
 These restrictions apply to branch manipulations performed via the GitHub API
 as well. So when you protect a branch, you will no longer be able to [delete
 the branch][delete] via the API or perform [update it][update] to point at a
@@ -46,6 +35,17 @@ HTTP/1.1 422 Unprocessable Entity
 }
 </pre>
 
+Protected branches and required status checks are a great way to ensure your
+project’s conventions are followed. For example, you could write a Status
+integration that only posts a `success` Status when the pull request’s author
+has signed your project’s Contributor License Agreement. Or you could write one
+that only posts a `success` Status when three or more members of your
+`@initech/senior-engineers` team have left a comment saying they’ve reviewed
+the changes. If you configure these integrations as required status checks, you
+can be sure that these conditions have been satisfied before a pull request is
+merged. See our [Status API guide][guide] to learn how to create integrations
+like these.
+
 If you have any questions, please [let us know][contact].
 
 [blog]: https://github.com/blog/2051-protected-branches-and-required-status-checks
