correct urls following ccos-scripts reorg and tidy formatting

Author: TimidRobot

content/contributing-code/github-repo-guidelines/contents.lr

@@ -4,68 +4,122 @@ _template: page-with-toc.html
 ---
 title: GitHub Repo Guidelines
 ---
-description: This is a checklist for all public repositories hosted on the [Creative Commons GitHub organization](https://github.com/creativecommons). Not all repositories meet these criteria yet. Please notify us if a project you'd like to work on does not meet this checklist by opening a GitHub issue associated with the repository.
+description: This is a checklist for all public repositories hosted on the
+[Creative Commons GitHub organization](https://github.com/creativecommons). Not
+all repositories meet these criteria yet. Please notify us if a project you'd
+like to work on does not meet this checklist by opening a GitHub issue
+associated with the repository.
 ---
 body:
 
+
 ## Required Items
-All GitHub repositories should have the following items to be considered fully ready for external contributors.
+
+All GitHub repositories should have the following items to be considered fully
+ready for external contributors.
+
 
 ### Files
+
 - `/.github/CODEOWNERS`: Defined code owners
-  - [About code owners - GitHub Help](https://help.github.com/en/articles/about-code-owners)
+  - [About code owners - GitHub Help][about-owners]
 - `/.cc-metadata.yml`: The standard [CC metadata YAML file](#cc-metadata-file).
 - `/CODE_OF_CONDUCT.md`: Code of Conduct
-	- Feel free to use our standard [`CODE_OF_CONDUCT.md`](https://github.com/creativecommons/vocabulary/blob/main/CODE_OF_CONDUCT.md) file from [creativecommons/.github](https://github.com/creativecommons/.github)
-	- [Adding a code of conduct to your project - GitHub Help](https://help.github.com/en/articles/adding-a-code-of-conduct-to-your-project)
+  - Feel free to use our standard [`CODE_OF_CONDUCT.md`][conduct] file from
+    [creativecommons/.github][dot-github]
+    - [Adding a code of conduct to your project - GitHub Help][help-condcut]
 - `/LICENSE`: license file.
 - `/CONTRIBUTING.md`: contributor guidelines
-	- Can be project-specific or our standard [`CONTRIBUTING.md`](https://github.com/creativecommons/vocabulary/blob/main/CONTRIBUTING.md) file from [creativecommons/.github](https://github.com/creativecommons/.github)
-	- [Setting guidelines for repository contributors - GitHub Help](https://help.github.com/en/articles/setting-guidelines-for-repository-contributors)
+  - Can be project-specific or our standard [`CONTRIBUTING.md`][contributing]
+    file from [creativecommons/.github][dot-github]
+  - [Setting guidelines for repository contributors - GitHub
+    Help][setting-guidelines]
 - `/README.md`: read me information file
-	- Must documents how to install and build the project locally and documents a high level overview of the project and code structure. It should also link to any other available documentation.
-- **All pull request templates must include the full text of the [DCO](https://developercertificate.org/)**.
+  - Must documents how to install and build the project locally and documents a
+    high level overview of the project and code structure. It should also link
+    to any other available documentation.
+- **All pull request templates must include the full text of the [DCO][dco].**
+
+[about-owners]: https://help.github.com/en/articles/about-code-owners
+[conduct]: https://github.com/creativecommons/vocabulary/blob/main/CODE_OF_CONDUCT.md
+[dot-github]: https://github.com/creativecommons/.github
+[help-condcut]: https://help.github.com/en/articles/adding-a-code-of-conduct-to-your-project
+[contributing]: https://github.com/creativecommons/vocabulary/blob/main/CONTRIBUTING.md
+[setting-guidelines]: https://help.github.com/en/articles/setting-guidelines-for-repository-contributors
+[dco]: https://developercertificate.org/
+
 
 ### Additional Items
-- CI and code style linters that run automatically whenever new code is pushed (if applicable to the project).
+
+- CI and code style linters that run automatically whenever new code is pushed
+  (if applicable to the project).
 - At least a couple of automated tests (if applicable to the project).
 
+
 ## Optional items
 
-- [Issue templates](https://help.github.com/en/articles/creating-issue-templates-for-your-repository). GitHub pulls the default templates from our [`.github` repository](https://github.com/creativecommons/.github) automatically, but if you want/need to customize them, create them in your repository.
-- A [pull request template](https://help.github.com/en/articles/creating-a-pull-request-template-for-your-repository). GitHub pulls the default template from our [`.github` repository](https://github.com/creativecommons/.github) automatically, but if you want/need to customize it, create it in your repository.
-- [Support resources](https://help.github.com/en/articles/adding-support-resources-to-your-project). GitHub pulls the default `SUPPORT.md` file from our [`.github` repository](https://github.com/creativecommons/.github) automatically, but if you want/need to customize it, create it in your repository.
+- [Issue templates][issue-templates]. GitHub pulls the default templates from
+  our [`.github` repository][dot-github] automatically, but if you want/need to
+  customize them, create them in your repository.
+- A [pull request template][pr-template]. GitHub pulls the default template
+  from  our [`.github` repository][dot-github] automatically, but if you
+  want/need to customize it, create it in your repository.
+- [Support resources][support-resources]. GitHub pulls the default `SUPPORT.md`
+  file from our [`.github` repository][dot-github] automatically, but if you
+  want/need to customize it, create it in your repository.
+
+[issue-templates]: https://help.github.com/en/articles/creating-issue-templates-for-your-repository
+[dot-github]: https://github.com/creativecommons/.github
+[pr-template]: https://help.github.com/en/articles/creating-a-pull-request-template-for-your-repository
+[support-resources]: https://help.github.com/en/articles/adding-support-resources-to-your-project
+
 
 ## Standard Labels
 
-All repositories must contain a set of standard labels, [documented here](/contributing-code/repo-labels/), which comprise of common labels in addition to repository-specific skill labels.
-You don't have to set these up manually. The labels are [automatically managed](https://github.com/creativecommons/ccos-scripts/tree/master/normalize_repos) on all CC repositories, and so, must not be renamed.
+All repositories must contain a set of standard labels, [documented
+here](/contributing-code/repo-labels/), which comprise of common labels in
+addition to repository-specific skill labels. You don't have to set these up
+manually. The labels are [automatically
+managed](https://github.com/creativecommons/ccos-scripts) on all CC
+repositories, and so, must not be renamed.
+
+Repositories may contain additional custom labels as well which will remain
+unaffected by the sync. It is recommended that custom labels be explained in
+the contribution guidelines for that project.
 
-Repositories may contain additional custom labels as well which will remain unaffected by the sync. It is recommended that custom labels be explained in the contribution guidelines for that project.
 
 ## Branch Protections
 
-Branch protections are automatically set up by CC staff via [this script](https://github.com/creativecommons/ccos-scripts/tree/master/normalize_repos). By default, pushing directly to the `master` branch is disabled and all pull requests require review by at least one person before merge.
+Branch protections are automatically set up by CC staff via
+[creativecommons/ccos-scripts](https://github.com/creativecommons/ccos-scripts).
+By default, pushing directly to the *default branch* (ex. `main`) is disabled
+and all pull requests require review by at least one person before merge.
+
 
 ## CC Metadata file
 
-Each repo should have a `.cc-metadata.yml` file in the root directory with the following structure:
-
-<pre>
-  <code>
-    # Whether this GitHub repo is for a CC-led engineering project
-    engineering_project: true
-    # Name of the repository/project in English
-    english_name: CC Catalog API
-    # All technologies used
-    technologies: Python, Django, Django REST Framework, Elasticsearch
-    # Whether this repository should be featured on the CC Open Source site's "Projects" page
-    featured: false
-    # Slack channel name (optional key)
-    slack: 'cc-dev-catalog'
-  </code>
-</pre>
-
-This metadata file is used in the [Projects](/projects/) page. Repos that are marked as non-engineering projects are not displayed in the page and repos marked as featured as displayed at the top of the page. Repos should be marked as featured if we are actively looking for community contributions and have the bandwidth to review them quickly.
-
-Repos without this metadata file are treated as `engineering_projects: true`, `featured: false` and `slack: ""`. A default is necessary since it will take time for us to clean up and add metadata to all our repos.
+Each repo should have a `.cc-metadata.yml` file in the root directory with the
+following structure:
+
+```yaml
+# Whether this GitHub repo is for a CC-led engineering project
+engineering_project: true
+# Name of the repository/project in English
+english_name: CC Catalog API
+# All technologies used
+technologies: Python, Django, Django REST Framework, Elasticsearch
+# Whether this repository should be featured on the CC Open Source site's "Projects" page
+featured: false
+# Slack channel name (optional key)
+slack: 'cc-dev-catalog'
+```
+
+This metadata file is used in the [Projects](/projects/) page. Repos that are
+marked as non-engineering projects are not displayed in the page and repos
+marked as featured as displayed at the top of the page. Repos should be marked
+as featured if we are actively looking for community contributions and have the
+bandwidth to review them quickly.
+
+Repos without this metadata file are treated as `engineering_projects: true`,
+`featured: false` and `slack: ""`. A default is necessary since it will take
+time for us to clean up and add metadata to all our repos.