Update docs/spec/draft/source-requirements.md

Co-authored-by: Aditya Sirish <8928778+adityasaky@users.noreply.github.com>
Signed-off-by: Tom Hennen <TomHennen@users.noreply.github.com>

docs/spec/draft/source-requirements.md

@@ -50,7 +50,7 @@ SCSs MAY allow the organization to expunge (remove) content from a repository an
 This includes changing files, history, or changing references in git and is used to accommodate legal/privacy compliance requirements.
 
 Removing a revision from a repository is similar to deleting a package version from a registry: it's almost impossible to estimate the amount of downstream supply chain impact.
-In version control systems like git, removal of a revision changes the object id of all subsequent revisions that were built on top of it.
+In version control systems like Git, removal of a revision changes the object IDs of all subsequent revisions that were built on top of it.
 Although there is no "safe" way to do it, it sometimes necessary and there are steps you can take to mitigate the damage.
 
 When used as an attack, this is called “repo hijacking” (or “repo-jacking”) and is one of the primary threats source provenance attestations protect against.