Remove "whether via updating or merging"

aroben · aroben · commit dd8e201268a7 · 2015-09-03T15:26:45.000-04:00
This is spelled out later and makes it harder to follow this sentence.
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
@@ -9,10 +9,9 @@ We’ve begun to [roll out Protected Branches][blog] across GitHub. When you
 protect a branch in one of your repositories, you will be prevented from
 force pushing to that branch or deleting it. You can also configure required
 status checks for your protected branch. When configured, changing a branch to
-point at a new commit (whether via [updating][update] or [merging][merge]) will
-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.
+point at a new commit will 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.
 
 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
