doc: use repository instead of repo

Stick with "repository" instead of using both "repository" and "repo". PR-URL: #39157 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Darshan Sen <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Harshitha K P <[email protected]>
nodejs · Sep 4, 2021 · 1996580 · 1996580
1 parent 62b439e
commit 1996580
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/doc/guides/collaborator-guide.md b/doc/guides/collaborator-guide.md
@@ -95,7 +95,7 @@ issues. If a user opens a security issue in the public repository:
 
 * Ask the user to submit a report through HackerOne as outlined in
   [SECURITY.md][].
-* Move the issue to the private repo called
+* Move the issue to the private repository called
   [premature-disclosures](https://github.com/nodejs/premature-disclosures).
 * For any related pull requests, create an associated issue in the
   `premature-disclosures` repository.  Add a copy of the patch for the
@@ -552,7 +552,7 @@ Checkout proper target branch:
 $ git checkout master
 ```
 
-Update the tree (assumes your repo is set up as detailed in
+Update the tree (assumes your repository is set up as detailed in
 [CONTRIBUTING.md](./contributing/pull-requests.md#step-1-fork)):
 
 ```text