🐛 Fix more broken links

docs/layouts/shortcodes/guides/tools.md

@@ -4,7 +4,7 @@ Next, you need a couple tools to interact with your Platform.sh project, one of
   Git is the primary tool you use to manage everything your app needs to run.
   Every commit pushed results in a new deployment, and all of your configuration is driven almost entirely by a small number of YAML files in your Git repository (which we will get to in the steps below).
   Your infrastructure, described in these files, becomes part of your application itself - completely transparent and version-controlled.
-  If you do not already have Git on your computer, you should [install it now](https://help.github.com/articles/set-up-git/).
+  If you do not already have Git on your computer, you should [install it now](https://docs.github.com/en/get-started/quickstart/set-up-git).
 
 * The [Platform.sh CLI](/development/cli/_index.md).
   This lets you interact with your Platform.sh project from the command line.

docs/src/development/private-repository.md

@@ -52,4 +52,4 @@ Since this account isn't used by a human, it's called a machine user.
 You can then add the machine account as collaborator
 or add the machine user to a team with access to the repositories it needs to manipulate.
 
-More information about this is available on [GitHub](https://developer.github.com/v3/guides/managing-deploy-keys/#machine-users).
+More information about this is available on [GitHub](https://docs.github.com/en/developers/overview/managing-deploy-keys#machine-users).

docs/src/development/ssh/ssh-keys.md

@@ -74,7 +74,7 @@ generate a key and have it added to your Platform.sh account automatically.
    ssh-add 'PATH_TO_YOUR_KEY'
    ```
 
-To generate a key otherwise, GitHub has a good [walk-through for creating SSH key pairs](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/) on various operating systems.
+To generate a key otherwise, GitHub has a good [walk-through for creating SSH key pairs](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) on various operating systems.
 
 Then you need to [add it to your Platform.sh account](#2-add-an-ssh-key-to-your-platform-account).
 

docs/src/development/tools.md

@@ -13,14 +13,14 @@ Any change you make to your Platform.sh project will need to be committed via Gi
 Before getting started, make sure you have it installed on your computer to be able to interact with Platform.sh.
 
 {{< note title="See also">}}
-* [Install Git](https://help.github.com/articles/set-up-git/)
+* [Install Git](https://docs.github.com/en/get-started/quickstart/set-up-git)
 * [Learn more about Git](https://git-scm.com/)
 {{< /note >}}
 
 ## SSH
 
 Secure Shell (SSH) is a secure, encrypted connection between your computer and the Platform.sh environment.  That includes connecting to your Git repository.  SSH offers two secure types of authentication, based on keys or certificates.  We support both.
 
-Certificates are used automatically when you use the [Platform.sh CLI](/development/cli/_index.md) and run almost any command.  You may force a login using `platform login -f` on the command line, provided you have a web browser available.
+Certificates are used automatically when you use the [Platform.sh CLI](./cli/_index.md) and run almost any command.  You may force a login using `platform login -f` on the command line, provided you have a web browser available.
 
 To use key pairs, see the [SSH keys](./ssh/ssh-keys.md).

docs/src/integrations/activity/_index.md

@@ -8,7 +8,7 @@ description: |
 
 {{< description >}}
 
-Check out examples from other users on the Platform.sh [Community site.](https://community.platform.sh/c/activity-scripts)
+Check out examples from other users on the Platform.sh [Community site](https://community.platform.sh/c/activity-scripts/10).
 
 ## Installing
 

docs/src/integrations/source/github.md

@@ -68,7 +68,7 @@ Optional parameters:
 * `--fetch-branches`: Track and deploy branches (true by default)
 * `--prune-branches`: Delete branches that do not exist in the remote GitHub repository (true by default)
 * `--build-pull-requests`: Track and deploy pull-requests (true by default)
-* `--build-draft-pull-requests`: If set to `true`, [draft pull requests](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request) will also have an environment created.
+* `--build-draft-pull-requests`: If set to `true`, [draft pull requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) will also have an environment created.
   If false they will be ignored.
   If `--build-pull-requests` is `false` this value is ignored.  (`true` by default)
 * `--build-pull-requests-post-merge`: `false` to have Platform.sh build the branch specified in a PR.