diff --git a/website/content/docs/nia/usage/errors-ref.mdx b/website/content/docs/nia/usage/errors-ref.mdx
index 4f433c9ef8..01aa10b6fd 100644
--- a/website/content/docs/nia/usage/errors-ref.mdx
+++ b/website/content/docs/nia/usage/errors-ref.mdx
@@ -67,7 +67,12 @@ $ curl --request GET cts-01.example.com:8558/v1/tasks
 
 **Resolution**:
 
-Identify the leader instance address and redirect the request to the leader. We recommend deploying a cluster that has three instances. You can query each instance until the leader responds. 
+Identify the leader instance address and redirect the request to the leader. You can identify the leader by calling the [`status/cluster` API endpoint](/docs/nia/api/status#cluster-status) or by checking the logs for the following entry:
+
+```shell-session
+[INFO] ha: acquired leadership lock: id=<ID-OF-CTS-INSTANCE>. 
+
+We recommend deploying a cluster that has three instances. 
 
 ---
 
@@ -90,7 +95,7 @@ Identify the leader instance address and redirect the request to the leader. We
 
 **Resolution**:
 
-Identify and send the request to the leader CTS instance. You can identify the leader by either making a call to the [`status` API endpoint](/docs/nia/api/status) or by checking the logs for the following entry:
+Identify and send the request to the leader CTS instance. You can identify the leader by calling the [`status/cluster` API endpoint](/docs/nia/api/status#cluster-status) or by checking the logs for the following entry:
 
 ```shell-session
 [INFO] ha: acquired leadership lock: id=<ID-OF-CTS-INSTANCE>
@@ -110,7 +115,7 @@ Identify and send the request to the leader CTS instance. You can identify the l
 
 **Conditions**:
 
-- CTS is not configured for [high availability](/docs/nia/usage/run-ha).
+- You called the [`status/cluster` API endpoint](/docs/nia/api/status#cluster-status) without configuring CTS for [high availability](/docs/nia/usage/run-ha).
 
 **Resolution**:
 
diff --git a/website/content/docs/nia/usage/run-ha.mdx b/website/content/docs/nia/usage/run-ha.mdx
index e7dac83c0a..81fa5c2d16 100644
--- a/website/content/docs/nia/usage/run-ha.mdx
+++ b/website/content/docs/nia/usage/run-ha.mdx
@@ -104,7 +104,7 @@ Repeat the procedure to start the remaining instances for your cluster. We recom
 
 You can implement a rolling update to update a non-task configuration for a CTS instance, such as the Consul connection settings. If you need to update a task in the instance configuration, refer to [Modify tasks](#modify-tasks). 
 
-1. Identify the leader CTS instance by either making a call to the [`status` API endpoint](/docs/nia/cli/start) or by checking the logs for the following entry:
+1. Identify the leader CTS instance by either making a call to the [`status/cluster` API endpoint](/docs/nia/api/status#cluster-status) or by checking the logs for the following entry:
   ```shell-session
   [INFO] ha: acquired leadership lock: id=<ID-OF-CTS-INSTANCE>
   ```
@@ -121,10 +121,10 @@ When high availability is enabled, CTS persists task and event data. Refer to [S
 You can use the following methods for modifying tasks when high availability is enabled. We recommend choosing a single method to make all task configuration changes because inconsistencies between the state and the configuration can occur when mixing methods.
 
 ### Delete and recreate the task (recommended)
-
+ 
 Use the CTS API to identify the CTS leader instance as well as delete and replace a task. 
 
-1. Identify the leader CTS instance by either making a call to the [`status` API endpoint](/docs/nia/api/status) or by checking the logs for the following entry:
+1. Identify the leader CTS instance by either making a call to the [`status/cluster` API endpoint](/docs/nia/api/status#cluster-status) or by checking the logs for the following entry:
 
   ```shell-session
   [INFO] ha: acquired leadership lock: id=<ID-OF-CTS-INSTANCE>