Merge pull request #2571 from OctopusDeploy/tk/docs-broken-link-fixes

Fixing broken link

src/pages/docs/deployments/custom-scripts/index.md

@@ -94,7 +94,7 @@ Learn about [script integrity](/docs/security/script-integrity).
 
 We recommend the following approaches for developing and testing your scripts, in order of preference:
 
- 1. Build your script to use script arguments as inputs so it can be invoked with equal fidelity from Octopus or directly in your development environment. You can test your scripts by invoking them directly in a development environment with a very fast feedback cycle. Learn about [passing parameters to scripts](passing-parameters-to-scripts/). The only difference in this approach may be the user context the script runs in.
+ 1. Build your script to use script arguments as inputs so it can be invoked with equal fidelity from Octopus or directly in your development environment. You can test your scripts by invoking them directly in a development environment with a very fast feedback cycle. Learn about [passing parameters to scripts](/docs/deployments/custom-scripts/passing-parameters-to-scripts). The only difference in this approach may be the user context the script runs in.
  2. Build your script as a reusable step template and test it using the `Run Now` feature. [Learn about step templates](/docs/projects/custom-step-templates). The only difference to this approach is the absence of deployment-specific variables provided by Octopus when actually running a deployment.
  3. Put your script in a test process and run that process in a test environment.
  4. Put your script in a real process and run that process in a test environment.

src/pages/docs/deployments/custom-scripts/scripts-in-packages/index.md

@@ -59,7 +59,7 @@ However, not all package steps support script hooks. As a general rule, any of t
 
 ## Running a script when a step fails
 
-You can create a file named `DeployFailed.<ext>`, which will be invoked if the step fails. Our blog post about this feature [describes how DeployFailed.<ext> works](https://octopus.com/blog/deployfailed).
+You can create a file named `DeployFailed.<ext>`, which will be invoked if the step fails.
 
 ## How Octopus executes your scripts
 
@@ -115,4 +115,4 @@ If you are using OctoPack to package a Windows Service or console application, s
 
 Read more about [using OctoPack](/docs/packaging-applications/create-packages/octopack).
 
-If the scripts in your package are still not running, make sure someone has not set a project variable called `Octopus.Action.Package.RunScripts` to `false` for the step where the scripts should run.
+If the scripts in your package are still not running, make sure someone has not set a project variable called `Octopus.Action.Package.RunScripts` to `false` for the step where the scripts should run.

src/pages/docs/packaging-applications/package-repositories/docker-registries/index.md

@@ -54,7 +54,7 @@ When you create a release in Octopus, you need to choose the "version" of the Im
 
 :::div{.hint}
 **Container images are downloaded directly by the Deployment Target or Worker**
-Octopus Deploy does not currently support functionality to push Images from the Octopus Server to the deployment targets in the same way that it does with other [supported packages](/docs/packaging-applications/#supported-formats). That being said, the [layered architecture of Images](https://docs.docker.com/engine/userguide/storagedriver/imagesandcontainers) allows your deployment targets to retrieve only those pieces that have changed from previous versions that are locally available, which is behavior built in to the Docker Engine.
+Octopus Deploy does not currently support functionality to push Images from the Octopus Server to the deployment targets in the same way that it does with other [supported packages](/docs/packaging-applications/#supported-formats). That being said, the layered architecture of images allows your deployment targets to retrieve only those pieces that have changed from previous versions that are locally available, which is behavior built in to the Docker Engine.
 :::
 
 ## Private registry {#private-registry}

src/pages/docs/packaging-applications/package-repositories/guides/container-registries/docker-hub.md

@@ -16,7 +16,7 @@ From September 5th 2022, the Docker Hub Registry is [deprecating v1 endpoints](h
 **DockerHub Private Repository Limitations**
 
 By design, Docker Hub **does not support** [searching for private repositories](https://docs.docker.com/docker-hub/#/explore-repositories), even with valid credentials. Additionally, while you will be able to search for a non-official repository, Docker Hub *will not return any tags for unofficial images*. If you are using an unofficial image, you will be able to select this when configuring your run step, but you will need to manually enter the version that you wish to deploy. So long as it exists in the registry, your Docker Engine will be able to pull it down.
-The Docker Hub API endpoint [https://index.docker.io/v1](https://index.docker.io/v1) provides access to repositories with different levels of access
+The Docker Hub API endpoint `https://index.docker.io/v1` provides access to repositories with different levels of access
 
 | Repository | Shows In Search | Lists Tags |
 | --- | --- | --- |
@@ -33,7 +33,7 @@ To use the Docker Hub registry in Octopus Deploy, create an external feed with t
 
 - **Feed Type:** Docker Container Registry
 - **Name:** DockerHub (or anything else that makes sense to you)
-- **URL:** [https://index.docker.io](https://index.docker.io)
+- **URL:** `https://index.docker.io`
 - **Registry Path:** *leave blank*
 - **Credentials:** Username and Password (Login for your DockerHub account, this is required for accessing public repositories)
 

src/pages/docs/projects/steps/configuration-features/substitute-variables-in-templates.md

@@ -26,8 +26,8 @@ The following example shows you how to use the Substitute Variables in Templates
 
 | Variable Name    | Value     | Scope    |
 | ----------------------- | --------------- | -------- |
-| LoginURL | https://test.example.com/login | Test |
-| LoginURL | https://example.com/login | Production |
+| LoginURL | `https://test.example.com/login` | Test |
+| LoginURL | `https://example.com/login` | Production |
 
 2. Include the loginURL variable in the app you're deploying, by adding the variable `#{LoginURL}`. For instance:
 
@@ -77,7 +77,7 @@ If you include a configuration file that you are also doing a [transformation](/
 By default **warnings** will be treated as **errors** when replacing variables in files using this feature. To override this behavior, set the variable **Octopus.Action.Package.IgnoreVariableReplacementErrors** to **True** in your project. By doing this, warnings will be treated as such and the deployment will not be marked as failed.
 :::
 
-## Examples {#SubstituteVariablesinFiles-SomeExamples}
+## Examples {#SubstituteVariablesInFiles-SomeExamples}
 
 ### Swapping design elements
 

src/pages/docs/releases/issue-tracking/jira.md

@@ -91,7 +91,7 @@ This process is for Jira Cloud, if you are using Jira Server, see [Connecting Ji
 
     In the Octopus Web Portal, navigate to **Configuration ➜ Settings ➜ Jira Integration** and copy the following values from the Jira App configuration page:
 
-    - **Jira Base URL**. This tells Octopus where your Jira instance is located and enables Octopus to render the links back to Jira issues. i.e., https://your-jira-instance.atlassian.net.
+    - **Jira Base URL**. This tells Octopus where your Jira instance is located and enables Octopus to render the links back to Jira issues. i.e., `https://your-jira-instance.atlassian.net`.
     - **Jira Connect App Password**.
 
     Ensure the **Is Enabled** property is set.
@@ -111,7 +111,7 @@ This process is for Jira Cloud, if you are using Jira Server, see [Connecting Ji
 
 4. Ensure the Octopus Server URL is set.
 
-    If you are using Octopus Cloud, this value is automatically set for you. If you are not using Octopus Cloud, navigate to the **Configuration ➜ Nodes** page and ensure you have set the Server URI field to your Octopus Server's base URL. i.e., https://my-company.octopus.app or https://my-company-internal-name
+    If you are using Octopus Cloud, this value is automatically set for you. If you are not using Octopus Cloud, navigate to the **Configuration ➜ Nodes** page and ensure you have set the Server URI field to your Octopus Server's base URL. i.e., `https://my-company.octopus.app` or `https://my-company-internal-name`
     Note: Octopus passes this value to Jira so it can build hyperlinks back to the deployments from the Jira UI. It never actually tries to connect to this URL itself.
 
 5. Configure the Octopus plugin in Jira.

src/pages/docs/security/users-and-teams/user-roles.md

@@ -82,7 +82,7 @@ The results will show:
 - The teams of which the user is a member of. There are two separate Permission context that you can check.
    - **Show System permissions** will show [System level permissions](/docs/security/users-and-teams/system-and-space-permissions)
    - **Show permissions within a specific space** will show [Space specific Permissions](/docs/security/users-and-teams/system-and-space-permissions).
-- A chart detailing each role and on which Environment/Project this permission can be executed. The chart can be exported to a CSV file by clicking the Export button. Once the file is downloaded it can viewed in browser using [Online CSV Editor and Viewer](http://www.convertcsv.com/csv-viewer-editor.htm).
+- A chart detailing each role and on which Environment/Project this permission can be executed. The chart can be exported to a CSV file by clicking the Export button. Once the file is downloaded it can viewed in browser using [Online CSV Editor and Viewer](https://www.convertcsv.com/csv-viewer-editor.htm).
 
 :::figure
 ![](/docs/security/users-and-teams/images/systempermissions.png)

src/shared-content/teamcity/teamcity-pack.include.md

@@ -2,7 +2,7 @@
 
 Octopus supports multiple [package formats](/docs/packaging-applications/#supported-formats) for deploying your software. TeamCity can be configured to monitor your source control and package your applications when changes are made.
 
-You configure TeamCity to package your applications by creating a [build configuration](https://www.jetbrains.com/help/teamcity/build-configuration.html), and adding a step to the configuration of runner type, **Octopus Deploy: Pack**.
+You configure TeamCity to package your applications by creating a [build configuration](https://www.jetbrains.com/help/teamcity/creating-and-editing-build-configurations.html), and adding a step to the configuration of runner type, **Octopus Deploy: Pack**.
 
 1. Give the step a name.
 2. Enter the [package ID](/docs/packaging-applications/#package-id).