Fix services names casing

Author: MattiSG

content/terms/guideline/choosing-selectors.md

@@ -15,7 +15,7 @@ Selectors are used in the [`select`]({{< relref "terms/reference#select" >}}) an
 
 The “selectors” referred to are defined by the [W3C Selectors standard](https://www.w3.org/TR/selectors/), more commonly known as “CSS Selectors”.
 
-An easy-to-read introduction to CSS Selectors can be found on [mdn web docs](https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Selectors).
+An easy-to-read introduction to CSS Selectors can be found on [MDN web docs](https://developer.mozilla.org/en-US/docs/Learn/CSS/Building_blocks/Selectors).
 
 ## Choosing durable selectors eases maintenance
 

content/terms/guideline/declaring.md

@@ -18,7 +18,7 @@ aliases:
 
 ### Terms used by several services
 
-- If you want to add terms which happen to be shared with another service from the same parent company, be specific in naming the exact service you want to track. For instance, you may find that a company like Github uses the same terms for its code hosting and its AI assistant. While this does not mean that the terms for GitHub (code hosting) are the only terms of GitHub Copilot (assistant), it does mean that these two services have terms that are represented in the same document. In tracking terms for one of these services, say Github Copilot, be specific in naming it as the service you want to track. This way, if GitHub was to introduce dedicated terms for each of these services in the future, their locations can be updated without having to create new terms since the service already existed before.
+- If you want to add terms which happen to be shared with another service from the same parent company, be specific in naming the exact service you want to track. For instance, you may find that a company like GitHub uses the same terms for its code hosting and its AI assistant. While this does not mean that the terms for GitHub (code hosting) are the only terms of GitHub Copilot (assistant), it does mean that these two services have terms that are represented in the same document. In tracking terms for one of these services, say GitHub Copilot, be specific in naming it as the service you want to track. This way, if GitHub was to introduce dedicated terms for each of these services in the future, their locations can be updated without having to create new terms since the service already existed before.
 
 - - -
 

content/terms/guideline/reviewing.md

@@ -102,7 +102,7 @@ Since the Service ID is used as the file name of the JSON file associated with t
 
 1. Open the pull request associated with the contribution and service.
 2. Navigate to the "Files changed" tab of the pull request. Here, you will see the files being changed by the contribution, including the JSON file of the service.
-3. To edit the file, click on the three dots button on the right side of the file name and select "Edit file". This will open the file in the Github editor.
+3. To edit the file, click on the three dots button on the right side of the file name and select "Edit file". This will open the file in the GitHub editor.
 4. From here, you can change the file name from the current Service ID to the new Service ID, which represents the transliteration of the service name.
 5. Once you have made the changes, commit them and review the pull request as usual. If everything checks out, you can merge the pull request.
 
@@ -153,7 +153,7 @@ For example, tests may fail in CI because of a 403 Access Denied error, but succ
 ## Merging the Pull Request
 
 Beyond status checks, additional restriction requires branches to be up to date before merging. This ensures that the contribution has been tested with the latest version of the collection. This appears as a _“This branch is out-of-date with the base branch”_ warning on a pull request.
-You can fix this using the Github interface, by clicking on the arrow button next to the “Update Branch” button, and select “Update with Rebase”.
+You can fix this using the GitHub interface, by clicking on the arrow button next to the “Update Branch” button, and select “Update with Rebase”.
 
 ## Contributions FAQ