respond to pr comments

Signed-off-by: Tom Hennen <tomhennen@google.com>

docs/spec/draft/source-requirements.md

@@ -224,14 +224,14 @@ For example, this would happen if the revision was created on another SCS, or if
 
 The SCS MUST ensure that all technical controls governing changes to a [branch](#definitions)
 
-1.  Cannot be bypassed except via the [Safe Expunging Process](#safe-expunging-process).
-2.  Are discoverable by authorized users of the repo.
+1.  Are discoverable by authorized users of the repo.
+2.  Cannot be bypassed except via the [Safe Expunging Process](#safe-expunging-process).
 
-For example, this can be accomplished:
+For example, this could be accomplished by:
 
--   Via the configuration of branch protection rules (e.g.[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule), [GitLab](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html)).
--   Via application and verification of [gittuf](https://github.com/gittuf/gittuf) policies.
--   Or some other mechanism as enforced by the [Change management tool](#change-management-tool-requirements).
+-   Via the configuration of branch protection rules (e.g.[GitHub](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule), [GitLab](https://docs.gitlab.com/ee/user/project/repository/branches/protected.html)), or
+-   via application and verification of [gittuf](https://github.com/gittuf/gittuf) policies, or
+-   some other mechanism as enforced by the [Change management tool](#change-management-tool-requirements).
 
 <td><td><td>✓
 </table>