Merge pull request #2230 from OctopusDeploy/tk/fixing-broken-links

Fixing broken links

dictionary-octopus.txt

@@ -16,6 +16,7 @@ Bento
 bootstrap
 bootstrapped
 bootstrapper
+changeit
 childelement
 choco
 cicd
@@ -54,6 +55,7 @@ dockerhub
 DONTVALIDATEPATH
 dpkg
 Dspring
+Elyton
 emptytitle
 Fargate
 feedcred
@@ -236,4 +238,4 @@ octopusbob
 servername
 octopusdemos
 sqlcmd
-sqlvolume
+sqlvolume

src/pages/docs/administration/managing-infrastructure/subscriptions/index.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2023-01-01
+modDate: 2023-04-10
 title: Subscriptions
 description: Subscriptions allow you to subscribe to events that are happening within Octopus, so you can be notified when events have occurred and react accordingly.
 navOrder: 1600
@@ -55,7 +55,7 @@ A subscription with the filters:
 That filter is translated to look for events where the category is Deployment Started AND for the environments Staging OR Production AND for the project Hello World.  
 :::
 
-You can read more about getting started with notifications in our [Getting Started guide](docs/getting-started/best-practices/notifications).
+You can read more about getting started with notifications in our [Getting Started guide](/docs/getting-started/best-practices/notifications).
 
 :::div{.hint}
 **Dates and Timezone**
@@ -113,7 +113,7 @@ While we make every effort to ensure events are only ever sent *once* to a given
 :::
 
 
-## Event visibility and permissions {#Subscriptions-EventVisibilityandPermissions}
+## Event visibility and permissions {#Subscriptions-Event-Visibility-and-Permissions}
 
 Because certain teams may be restricted to only see certain events, subscriptions give you the ability to scope to one or more teams. Teams may be restricted to certain criteria, such as project(s) and/or environment(s). Combine these restrictions with team roles and you can successfully control which events get seen for a given subscription. See more information on [Managing Users and Teams](/docs/security/users-and-teams/) as well as our [User Roles](/docs/security/users-and-teams/user-roles) documentation if you wish to learn more.
 

src/pages/docs/deployments/certificates/wildfly-certificate-import.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2023-01-01
+modDate: 2024-04-10
 title: Import certificates into WildFly and JBoss EAP
 description: Configure WildFly or JBoss EAP with a certificate managed by Octopus.
 navOrder: 50
@@ -158,9 +158,9 @@ The `Elytron server SSL context name` defines the name of the Elytron SSL Contex
 :::
 
 :::div{.hint}
-You can find more information of the Elytron subsystem components in the [WildFly documentation](https://docs.jboss.org/author/display/WFLY/Using+the+Elytron+Subsystem#UsingtheElytronSubsystem-onewayapps).
+You can find more information of the Elytron subsystem components in the [WildFly documentation](https://docs.jboss.org/author/display/WFLY/Elytron%20Subsystem.html).
 :::
 
 ## Configuration file backups
 
-Before any changes are made to the WildFly or JBoss EAP configurations, a `:take-snapshot` command is run. This will create a backup file in the `domain/configuration/standalone_xml_history/snapshot` or `standaline/configuration/standalone_xml_history/snapshot` directory.
+Before any changes are made to the WildFly or JBoss EAP configurations, a `:take-snapshot` command is run. This will create a backup file in the `domain/configuration/standalone_xml_history/snapshot` or `standalone/configuration/standalone_xml_history/snapshot` directory.

src/pages/docs/deployments/deployment-freezes.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2024-03-25
-modDate: 2024-03-25
+modDate: 2024-04-10
 title: Deployment freezes
 description: Deployment freezes allow you to pause deployments for a specified time range
 navOrder: 170
@@ -83,5 +83,5 @@ As this is an early access feature, we are aware of some flaws in the UI when as
 ## Learn more
 
 - [Projects](/docs/projects/)
-- [Environments](/docs/infrastructure/environments/index)
+- [Environments](/docs/infrastructure/environments)
 - Learn more about our concept of [Spaces](/docs/administration/spaces)

src/pages/docs/projects/community-step-templates.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2023-01-01
+modDate: 2024-04-10
 title: Community step templates
 description: How to take advantage of step templates contributed by the Octopus community.
 navOrder: 50
@@ -78,8 +78,8 @@ If you run into any problems with a community step template, don't worry - [we a
 
 Our community step templates live in our [Library repository](https://github.com/OctopusDeploy/Library) on GitHub. If you're familiar with GitHub, you can raise an [issue](https://github.com/OctopusDeploy/Library/issues), and a member of the Octopus team will triage the issue and work with you to get the issue resolved. 
 
-In addition, as the code is open-source, you can also submit a [pull request](https://github.com/OctopusDeploy/Library/pulls) to fix an issue. We have [contributing guidelines](https://github.com/OctopusDeploy/Library/blob/master/.github/CONTRIBUTING/) that we recommend reading before submitting a change.
+In addition, as the code is open-source, you can also submit a [pull request](https://github.com/OctopusDeploy/Library/pulls) to fix an issue. We have [contributing guidelines](https://github.com/OctopusDeploy/Library/blob/master/.github/CONTRIBUTING.md) that we recommend reading before submitting a change.
 
 ## Security 
 
-Community step templates are created, updated, and fixed by the Octopus team and the Octopus community. The Octopus team reviews all contributions before they are added to the Octopus library so that the step template only does what the template is designed to do and nothing malicious. 
+Community step templates are created, updated, and fixed by the Octopus team and the Octopus community. The Octopus team reviews all contributions before they are added to the Octopus library so that the step template only does what the template is designed to do and nothing malicious. 

src/pages/docs/projects/custom-step-templates.md

@@ -1,7 +1,7 @@
 ---
 layout: src/layouts/Default.astro
 pubDate: 2023-01-01
-modDate: 2023-01-01
+modDate: 2024-04-10
 title: Custom step templates
 description: How to create reusable steps
 navOrder: 60
@@ -93,7 +93,7 @@ If you want to transport, backup, or share your custom step templates with the c
 Now you can take that exported template document and commit it to source control, or share it on the [Community Library](https://library.octopus.com/).
 
 :::div{.success}
-Take a look at the [contributing guide](https://github.com/OctopusDeploy/Library/blob/master/.github/CONTRIBUTING/) for the Community Library and submit your step template as a [pull request](https://github.com/OctopusDeploy/Library/pulls).
+Take a look at the [contributing guide](https://github.com/OctopusDeploy/Library/blob/master/.github/CONTRIBUTING.md) for the Community Library and submit your step template as a [pull request](https://github.com/OctopusDeploy/Library/pulls).
 :::
 
 ## Linking custom step templates to community step templates