Update wording to match definitions added in #375 (#388)

Signed-off-by: Ben Cotton <[email protected]>

Author: funnelfiasco

baseline/OSPS-GV.yaml

@@ -260,13 +260,13 @@ controls:
       - id: OSPS-GV-04.01
         text: |
           While active, the project documentation MUST have a policy that code
-          contributors are reviewed prior to granting escalated permissions to
+          collaborators are reviewed prior to granting escalated permissions to
           sensitive resources.
         applicability:
           - Maturity Level 3
         recommendation: |
           Publish an enforceable policy in the project documentation that
-          requires code contributors to be reviewed and approved before being
+          requires code collaborators to be reviewed and approved before being
           granted escalated permissions to sensitive resources, such as merge
           approval or access to secrets. It is recommended that vetting includes
           establishing a justifiable lineage of identity such as confirming the

baseline/OSPS-QA.yaml

@@ -543,5 +543,5 @@ controls:
           Configure the project's version control system to require at least one
           non-author approval of changes before merging into the release or
           primary branch. This can be achieved by requiring a pull request to be
-          reviewed and approved by at least one other contributor before it can
+          reviewed and approved by at least one other collaborator before it can
           be merged.