Merge pull request #955 from github/ThatStoney-patch-1

Update broken link

Author: ThatStoney

docs/getting-started.md

@@ -13,7 +13,7 @@
 
  2. Copy the [`backup.config-example`][3] file to `backup.config` and modify as
     necessary. The `GHE_HOSTNAME` value must be set to the primary GitHub Enterprise Server
-    host name. Additional options are available and documented in the
+    hostname. Additional options are available and documented in the
     configuration file but none are required for basic backup functionality.
 
     As the data on a High Availability replica may be in a transient state at the time of backup,
@@ -22,7 +22,7 @@
     * Backup Utilities will attempt to load the backup configuration from the following
       locations, in this order:
 
-      ```
+      ```bash
       $GHE_BACKUP_CONFIG (User configurable environment variable)
       $GHE_BACKUP_ROOT/backup.config (Root directory of backup-utils install)
       $HOME/.github-backup-utils/backup.config
@@ -32,7 +32,7 @@
       with the `-i <abs path to private key>` SSH option.
 
  3. Add the backup host's SSH key to the GitHub appliance as an *Authorized SSH
-    key*. See [Adding an SSH key for shell access][4] for instructions.
+    key*. See [Adding your SSH key to the ssh-agent][4] for instructions.
 
  4. Run `bin/ghe-host-check` to verify SSH connectivity with the GitHub
     appliance.
@@ -42,4 +42,4 @@
 [1]: https://github.com/github/backup-utils/releases
 [2]: https://github.com/github/backup-utils/releases/tag/v2.11.4
 [3]: https://github.com/github/enterprise-backup-site/blob/master/backup.config-example
-[4]: https://enterprise.github.com/help/articles/adding-an-ssh-key-for-shell-access
+[4]: https://docs.github.com/enterprise-server/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent