From aefbab83fbed1f902ea3e2d436a9cd8bfc5a184c Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Thu, 22 Aug 2024 16:48:15 -0400
Subject: [PATCH] docs: Updates based on feedback

---
 website/content/docs/operations/health.mdx     | 4 ++--
 website/content/docs/release-notes/v0_16_0.mdx | 4 ++--
 website/content/docs/release-notes/v0_17_0.mdx | 4 ++--
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/content/docs/operations/health.mdx b/website/content/docs/operations/health.mdx
index 6854d1c383..3144f5c19d 100644
--- a/website/content/docs/operations/health.mdx
+++ b/website/content/docs/operations/health.mdx
@@ -38,7 +38,7 @@ All responses return empty bodies. `GET /health` does not support any input.
 
 ## Check the health endpoint using `wget`
 
-The Boundary Enterprise Docker image includes `wget`. It is also available to HCP Boundary users. You can use it to check the health endpoint.
+The Boundary Docker image includes `wget`. You can use it to check the health endpoint. Enterprise and Community edition users can check the health of controllers and workers. HCP Boundary users can check the health of their self-managed workers.
 
 Use the following command to check a worker's status to determine if it is healthy:
 
@@ -49,7 +49,7 @@ $ wget -q -O - http://localhost:9203/health?worker_info=1 | grep -c 'READY'
 - `-q` - Prints the response instead of saving it to a file.
 - `-0` - Allows Boundary to pass the worker's URL.
 
-If the command prints 1 to `stdout` or  exits with exit code 0, it means the worker is healthy. Exit code > 0, is unhealthy
+If the command prints 1 to `stdout` or exits with exit code 0, it means the worker is healthy. If the exit code is greater than 0, the worker is unhealthy.
 
 You can also use the following command without `grep -c 'READY'` to print a more verbose response that includes the worker's state, active session count, and connection state:
 
diff --git a/website/content/docs/release-notes/v0_16_0.mdx b/website/content/docs/release-notes/v0_16_0.mdx
index 760436681f..c78c61ae6c 100644
--- a/website/content/docs/release-notes/v0_16_0.mdx
+++ b/website/content/docs/release-notes/v0_16_0.mdx
@@ -36,7 +36,7 @@ description: |-
     Docker image no longer contains <code>curl</code>
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    As of version 0.16.3 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary Enterprise. The image now includes <code>wget</code>, which you can alternatively use to check the health endpoint for a worker. If your workflow depends on having <code>curl</code> in the image, you can dynamically install it using <code>apk</code>.
+    As of version 0.16.3 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary. The image now includes <code>wget</code>, which you can alternatively use to check the health endpoint for a worker. If your workflow depends on having <code>curl</code> in the image, you can dynamically install it using <code>apk</code>.
     <br /><br />
     Learn more:&nbsp; <a href="#known-issues-and-breaking-changes">Known issues and breaking changes </a>
     </td>
@@ -257,7 +257,7 @@ description: |-
     Docker image no longer contains <code>curl</code>
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    As of version 0.16.3 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary Enterprise.
+    As of version 0.16.3 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary.
     <br /><br />
     The image now includes <code>wget</code>. You can use <code>wget</code> to check the health endpoint for workers.
     <br /><br />
diff --git a/website/content/docs/release-notes/v0_17_0.mdx b/website/content/docs/release-notes/v0_17_0.mdx
index d89d7baa5d..0ffe2889a2 100644
--- a/website/content/docs/release-notes/v0_17_0.mdx
+++ b/website/content/docs/release-notes/v0_17_0.mdx
@@ -36,7 +36,7 @@ description: |-
     Docker image no longer contains <code>curl</code>
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    As of version 0.17.1 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary Enterprise. The image now includes <code>wget</code>, which you can alternatively use to check the health endpoint for a worker. If your workflow depends on having <code>curl</code> in the image, you can dynamically install it using <code>apk</code>.
+    As of version 0.17.1 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary. The image now includes <code>wget</code>, which you can alternatively use to check the health endpoint for a worker. If your workflow depends on having <code>curl</code> in the image, you can dynamically install it using <code>apk</code>.
     <br /><br />
     Learn more:&nbsp; <a href="#known-issues-and-breaking-changes">Known issues and breaking changes </a>
     </td>
@@ -166,7 +166,7 @@ description: |-
     Docker image no longer contains <code>curl</code>
     </td>
     <td style={{verticalAlign: 'middle'}}>
-    As of version 0.17.1 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary Enterprise.
+    As of version 0.17.1 and later, the <code>curl</code> binary is no longer included in the published Docker container image for Boundary.
     <br /><br />
     The image now includes <code>wget</code>. You can use <code>wget</code> to check the health endpoint for workers.
     <br /><br />