Missed a word

aroben · aroben · commit aa7aaa5cd3af · 2015-09-03T15:10:45.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
@@ -19,10 +19,11 @@ 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` 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.
+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
