From 1b8db889a3ec7ffa61702832fd308002fff06c91 Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Tue, 4 Jun 2024 15:17:37 -0400
Subject: [PATCH] docs: Minor edits

---
 website/content/docs/troubleshoot/common-errors.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/content/docs/troubleshoot/common-errors.mdx b/website/content/docs/troubleshoot/common-errors.mdx
index 611fcc6861..5540995642 100644
--- a/website/content/docs/troubleshoot/common-errors.mdx
+++ b/website/content/docs/troubleshoot/common-errors.mdx
@@ -76,7 +76,7 @@ You may experience this error when attempting credential injection via Vault. Cu
 types are supported for credential injection, but only username_password can be set up using the Web UI. If you experience this error,
 attempt to create the Vault ssh_private_key credential library using the CLI instead of the UI.
 
-## Error from controller when performing authorize-session action against given target: No ingress workers with valid next-hop paths could be found for this multi-hop session.
+## Error from controller when performing authorize-session action against given target: No ingress workers with valid next-hop paths could be found for this multi-hop session
 
 ```
 boundary connect ssh -target-id ttcp_3DxjpP9Y3o Error from controller when performing authorize-session action against given target
@@ -88,4 +88,4 @@ Error information:
   context:             Error from controller when performing authorize-session action against given target
 ```
 
-You may experience this error when deploying multiple Boundary controllers in HA mode if you have not assigned a unique name to each controller. Ensure each controller has a [unique name](/boundary/docs/configuration/controller#name) in the controller stanza.
+You may experience this error when deploying multiple Boundary controllers in high availability (HA) mode if you have not assigned a unique name to each controller. Ensure each controller has a [unique name](/boundary/docs/configuration/controller#name) in the controller stanza.