Skip to content

Commit 0139e76

Browse files
Replace en-dash with hyphen
1 parent 1e56873 commit 0139e76

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • src/pages/docs/kubernetes/live-object-status/troubleshooting

src/pages/docs/kubernetes/live-object-status/troubleshooting/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ Refer to the [agent installation docs](/docs/kubernetes/targets/kubernetes-agent
3939

4040
## Runtime
4141

42-
### Failed to establish connection with Kubernetes Monitor \{#failed-to-establishconnection-with-kubernetes-monitor}
42+
### Failed to establish connection with Kubernetes Monitor \{#failed-to-establish-connection-with-kubernetes-monitor}
4343

4444
Some actions, such as logs and events, require per request communication with the Kubernetes monitor running in your cluster.
4545

@@ -53,7 +53,7 @@ In almost all cases, we have found restarting the Kubernetes monitor pod will re
5353

5454
### We couldn't find a Kubernetes monitor associated with the deployment target \{#kubernetes-monitor-not-found}
5555

56-
Similar to the [error above](/docs/kubernetes/live-object-status/troubleshooting#failed-to-establishconnection-with-kubernetes-monitor), however more severe.
56+
Similar to the [error above](/docs/kubernetes/live-object-status/troubleshooting#failed-to-establish-connection-with-kubernetes-monitor), however more severe.
5757

5858
This error will be shown when Octopus fails to find the registration of a Kubernetes monitor at all. If the Kubernetes agent and monitor are both still running in your Kubernetes cluster, this means the Kubernetes monitor will need to be re-registered with Octopus.
5959

0 commit comments

Comments
 (0)