From f89605478d33b8ac6566b2ec54c0e1bd825c2a7d Mon Sep 17 00:00:00 2001 From: Jim Galasyn Date: Mon, 8 Jan 2018 08:54:52 -0800 Subject: [PATCH] Fix typo (#5693) --- .../monitor-and-troubleshoot/troubleshoot-configurations.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/datacenter/ucp/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-configurations.md b/datacenter/ucp/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-configurations.md index 0800fed532..2daee28043 100644 --- a/datacenter/ucp/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-configurations.md +++ b/datacenter/ucp/2.2/guides/admin/monitor-and-troubleshoot/troubleshoot-configurations.md @@ -10,7 +10,7 @@ components and trying to bring them to a healthy state. In most cases, if a single UCP component is in a failed state persistently, you should be able to restore the cluster to a healthy state by removing the unhealthy node from the cluster and joining it again. -[Lean how to remove and join nodes](../configure/scale-your-cluster.md). +[Learn how to remove and join nodes](../configure/scale-your-cluster.md). ## Troubleshoot the etcd key-value store