fix some links and update htmlproofer config to ignore private links

Author: rosieyohannan

.circleci/config.yml

@@ -125,15 +125,13 @@ jobs:
           command: |
             set -e
             echo "[INFO] Validating built site with HTML Proofer..."
-            ls -la
-            htmlproofer --help
             # Handle path prefix and ignore search template placeholders
             htmlproofer ./build \
               --ignore-empty-alt \
               --checks 'Links,Images' \
               --swap-urls '^/docs/:/' \
               --ignore-files './build/api/v1/index.html,./build/api/v2/index.html' \
-              --ignore-urls '[url],[path],https://circleci.com/api/v1.1/me,https://circleci.com/docs/webhooks/#outbound-webhooks' \
+              --ignore-urls '[url],[path],https://circleci.com/api/v1.1/me,https://circleci.com/docs/webhooks/#outbound-webhooks,.*circleci-docs-static.*' \
               --ignore-status-codes '403,429,999' \
               --no-check-external-hash \
               --typhoeus '{"timeout":30,"followlocation":true,"headers":{"User-Agent":"Mozilla/5.0 (compatible; LinkChecker)"}}'

docs/guides/modules/execution-managed/pages/custom-images.adoc

@@ -145,7 +145,7 @@ The example uses Docker Hub, but you can use different registries if you prefer.
 [#preparing-the-image-for-the-registry]
 === 8. Prepare the image for the registry
 
-. Log in to Docker Hub with your account and create a new repository on the https://hub.docker.com/add/repository/[add repository] page.
+. Log in to Docker Hub with your account and create a new repository on the Repositories page.
 It is best practice to use a pattern similar to `<project-name>-<container-name>` for a repository name (for example, `cci-demo-docker-primary`).
 
 . Next, rebuild your image using your account and repository name:
@@ -199,7 +199,7 @@ NOTE: This section assumes you have already used Docker login locally.
 
 This section demonstrates how to build a Ruby container to use on CircleCI.
 
-The example starts with the link:https://hub.docker.com/_/ruby/[Ruby 2.1] image. However, instead of using FROM `ruby:2.1` as the base image it describes how the container is built. From the Ruby Docker Hub page, go to the link:https://raw.githubusercontent.com/docker-library/ruby/e32433a12099d96dc5a1b28a011b73af4f17cfff/2.1/Dockerfile10[2.1/Dockerfile].
+The example starts with the link:https://hub.docker.com/_/ruby/[Ruby 2.1] image. However, instead of using FROM `ruby:2.1` as the base image it describes how the container is built. From the Ruby Docker Hub page, go to the 2.1/Dockerfile.
 
 Notice the environment variables that are used to pull in the correct versions.
 

docs/guides/modules/permissions-authentication/pages/set-up-sso.adoc

@@ -22,7 +22,7 @@ To begin setting up a SAML SSO connection in your CircleCI organization, follow
 
 === Configure your Identity Provider (IdP)
 
-Next you will configure your IdP. The steps to do this will vary depending on your IdP. For example, if you are using Okta, refer to link:https://help.okta.com/en-us/content/topics/apps/apps_app_integration_wizard_saml.html[Okta's documentation].
+Next you will configure your IdP. The steps to do this will vary depending on your IdP. For example, if you are using Okta, refer to link:https://help.okta.com/[Okta's documentation].
 
 . Open your IdP and paste the required configuration details (**Setup Parameters** and **Allowed iFrame Origin**) retrieved from CircleCI in the previous section to configure your IdP.
 . Add `https://app.circleci.com` to your IdP's trusted origins for iframe embedding. This is required to validate a user's active SSO session when they are interacting with an SSO organization in CircleCI.