Hyphenate "double check" and "triple check"

src/pages/docs/deployments/packages/troubleshoot-missing-packages.md

@@ -27,7 +27,7 @@ Try manually deploying the same release again (in other words retry the exact sa
 
 - **If retrying the deployment fails** the most likely problems are the package wasn't pushed, or there is a mismatch in Package ID and/or Version somewhere.  
   - Make sure the correct package is [pushed to the built-in repository](/docs/packaging-applications/package-repositories/built-in-repository/#pushing-packages-to-the-built-in-repository) and try the deployment again.  
-  - Double check the package version and any metadata match what you expect. The index for the built-in repository will use embedded package metadata in preference to the file name of the package when determining the Package ID and Version.  
+  - Double-check the package version and any metadata match what you expect. The index for the built-in repository will use embedded package metadata in preference to the file name of the package when determining the Package ID and Version.  
 - **If retrying the deployment succeeds** the most likely problem is that the package wasn't pushed to the built-in feed before the deployment started.  
   - The built-in feed has no indexing delay, packages are immediately available after being pushed.  
   - By default Octopus will attempt several times to locate the package in the built-in feed over a period of time, just in case.  
@@ -45,7 +45,7 @@ If you are using an external feed you may see a message explaining the package c
   - **If retrying the deployment fails** the most likely problems are the package wasn't pushed, or there is a mismatch in Package ID and/or Version somewhere.
     - Make sure the package is pushed successfully to your external feed.
       - If the package exists in the external feed, check it hasn't been hidden/removed from the package feed's index. For example, in NuGet.org you cannot delete packages, you can only hide them from the index so it doesn't appear in search results.
-      - Double check the package version and any metadata inside the package actually match what you expect. The index for your external feed will usually read the embedded package metadata in preference to the file name of the package when determining the Package ID and Version.
+      - Double-check the package version and any metadata inside the package actually match what you expect. The index for your external feed will usually read the embedded package metadata in preference to the file name of the package when determining the Package ID and Version.
   - **If retrying the deployment succeeds** the most likely problem is that the external feed didn't index the package quickly enough after the package was pushed.
     - By default Octopus will attempt several times to download the package from your external feed over a period of time.
     - Try to improve the indexing performance of your external feed by cleaning up old packages. Most external feeds provide automatic retention policies to help keep your feeds clean.

src/pages/docs/infrastructure/accounts/username-and-password.md

@@ -23,7 +23,7 @@ If you experience problems connecting, it may help to try connecting directly to
 
 :::div{.warning}
 **Different distributions use different conventions**
-While the above instructions should work on common platforms like Ubuntu or Red Hat, you may need to double check the details for specific instructions relating to SSH authentication on target operating system. There are many different Linux based distributions, and some of these have their own unique way of doing things. For this reason we cannot guarantee that these SSH instructions will work in every case.
+While the above instructions should work on common platforms like Ubuntu or Red Hat, you may need to double-check the details for specific instructions relating to SSH authentication on target operating system. There are many different Linux based distributions, and some of these have their own unique way of doing things. For this reason we cannot guarantee that these SSH instructions will work in every case.
 :::
 
 ## Create a username and password account {#UsernameandPassword-Creatingtheaccount}

src/pages/docs/infrastructure/deployment-targets/linux/sudo-commands.md

@@ -80,7 +80,7 @@ Ideally your Octopus Deploy SSH endpoint should be configured with a special use
 
 ## Different Distributions use Different Conventions
 
-While the above instructions should work on common platforms like Ubuntu or RedHat, you may need to double check the details for specific instructions relating to SSH authentication on target operating system. There are many Linux based distributions, some of which have their own unique way of doing things. For this reason, we cannot guarantee that these instructions will work in every case.
+While the above instructions should work on common platforms like Ubuntu or RedHat, you may need to double-check the details for specific instructions relating to SSH authentication on target operating system. There are many Linux based distributions, some of which have their own unique way of doing things. For this reason, we cannot guarantee that these instructions will work in every case.
 
 ## Learn more
 

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

@@ -216,7 +216,7 @@ If you find a previously working Jira integration has stopped working after upgr
 
 ### Map Jira environments to Octopus environments {#troubleshooting-map-your-environments}
 
-If your deployments aren't being displayed in Jira, this likely means you will need to double check that your Octopus environments are correctly mapped to your Jira environments.
+If your deployments aren't being displayed in Jira, this likely means you will need to double-check that your Octopus environments are correctly mapped to your Jira environments.
 
 Navigate to **Infrastructure ➜ Environments**, and next to each environment click on the overflow menu (`...`) and click **Edit**. From here, you can map each Octopus environment to your corresponding Jira environment.
 

src/pages/docs/security/authentication/oidc-authentication/configuring-authentik.mdx

@@ -106,7 +106,7 @@ If you already have Octopus user accounts and you want to enable external authen
 
 If you are having difficulty configuring Octopus to authenticate with Authentik, check your [server logs](/docs/support/log-files) for warnings and check the Authentik logs. You can access logs in Authentik by navigating to the **Admin interface**, then selecting **Events** and then **Logs** from the sidebar.
 
-### Double and triple check your configuration
+### Double- and triple-check your configuration
 
 Unfortunately security-related configuration is sensitive to everything. Make sure:
 

src/pages/docs/security/authentication/oidc-authentication/configuring-keycloak.mdx

@@ -119,7 +119,7 @@ If you already have Octopus user accounts and you want to enable external authen
 
 If you are having difficulty configuring Octopus to authenticate with Keycloak, check your [server logs](/docs/support/log-files) for warnings and check the Keycloak logs. You may need to enable logging in Keycloak if it's not already turned on, by going to `Realm settings` then the `Events` tab.
 
-### Double and triple check your configuration
+### Double- and triple-check your configuration
 
 Unfortunately security-related configuration is sensitive to everything. Make sure:
 

src/pages/docs/security/authentication/oidc-authentication/configuring-ping.mdx

@@ -109,7 +109,7 @@ If you already have Octopus user accounts and you want to enable external authen
 
 If you are having difficulty configuring Octopus to authenticate with Ping Identity, check your [server logs](/docs/support/log-files) for warnings.
 
-### Double and triple check your configuration
+### Double- and triple-check your configuration
 
 Unfortunately security-related configuration is sensitive to everything. Make sure:
 

src/pages/docs/security/authentication/oidc-authentication/index.mdx

@@ -94,7 +94,7 @@ We do our best to log warnings to your Octopus Server log whenever possible. If
 
 Your identity provider likely also has logging functionality, so check to see what the logs report on that side too.
 
-### Double and triple check your configuration
+### Double- and triple-check your configuration
 
 Unfortunately security-related configuration is sensitive to everything. Make sure:
 

src/pages/docs/security/authentication/okta-authentication.mdx

@@ -165,7 +165,7 @@ You can also check Okta logs by clicking the **View Logs** link on the Okta admi
 ![](/docs/img/security/authentication/okta/okta-view-logs.png)
 :::
 
-### Double and triple check your configuration
+### Double- and triple-check your configuration
 
 Unfortunately security-related configuration is sensitive to everything. Make sure:
 

src/pages/docs/security/octopus-tentacle-communication/custom-certificates-with-octopus-server-and-tentacle.md

@@ -132,4 +132,4 @@ The thumbprint of this Tentacle is: DE010ABF6FF8ED1B7895A31F005B8D88A3329867
 
 5. Open the Octopus Web Portal and select to the Tentacle on the Environments Page.
 6. Update the Tentacle thumbprint to use the value from Step 4 above and click the save button.
-7. Select the Connectivity tab and then click Check health to verify the connection is working.  If it's not, double check the Octopus Server and Tentacle thumbprints to ensure they are correct.
+7. Select the Connectivity tab and then click Check health to verify the connection is working.  If it's not, double-check the Octopus Server and Tentacle thumbprints to ensure they are correct.

src/pages/docs/support/troubleshooting-failed-or-hanging-tasks.md

@@ -13,7 +13,7 @@ Sometimes your deployments, health checks, or other tasks may unexpectedly fail,
 
 The first step to debug your failed tasks is to check the [Task Log](/docs/support/get-the-raw-output-from-a-task). This will usually contain detailed information about the failure. For deployments, this includes the step, and information about the deployment targets that the step was running on.
 
-If a deployment failed unexpectedly within a built-in step, you may have misconfigured the step. Double check the configuration of your [step](/docs/projects/steps/) in your [deployment process](/docs/projects/deployment-process/). If your step is relying on [variables](/docs/projects/variables/), then you may have also misconfigured your variables. There are [some methods](/docs/support/debug-problems-with-octopus-variables) available that can help you debug your variables.
+If a deployment failed unexpectedly within a built-in step, you may have misconfigured the step. Double-check the configuration of your [step](/docs/projects/steps/) in your [deployment process](/docs/projects/deployment-process/). If your step is relying on [variables](/docs/projects/variables/), then you may have also misconfigured your variables. There are [some methods](/docs/support/debug-problems-with-octopus-variables) available that can help you debug your variables.
 
 If a task fails while executing a PowerShell script, you may be able to get more information by debugging the PowerShell script. You can easily [debug PowerShell scripts](/docs/deployments/custom-scripts/debugging-powershell-scripts) as they are executed by Tentacle.