From f42f0de349c47b54edb40b3bc0319c91ca04eed4 Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Wed, 29 May 2024 17:02:00 -0400
Subject: [PATCH] docs: Specify fix is for self-managed versions

---
 website/content/docs/release-notes/v0_16_0.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/content/docs/release-notes/v0_16_0.mdx b/website/content/docs/release-notes/v0_16_0.mdx
index 99377c107c..0761b10a58 100644
--- a/website/content/docs/release-notes/v0_16_0.mdx
+++ b/website/content/docs/release-notes/v0_16_0.mdx
@@ -147,6 +147,8 @@ description: |-
   <tr>
     <td style={{verticalAlign: 'middle'}}>
     0.16.0
+    <br /><br />
+    (Fixed in 0.16.1 for Community and Enterprise editions)
     </td>
     <td style={{verticalAlign: 'middle'}}>
     Controller dead lock with database connections stuck in <code>idle in transaction</code> state
@@ -156,7 +158,7 @@ description: |-
     <br /><br />
     The cause of this problem was due to a combination of issues including the lack of a request timeout for worker-to-controller GRPC requests, and the session repository attempting to use a separate database connection to retrieve a KMS wrapper, after already starting a database transaction.
     <br /><br />
-    This issue is fixed in release 0.16.1. KMS operations now occur outside of the transaction, and a max request duration for GRPC requests is now set based on the cluster's listener configuration.
+    This issue is fixed in release 0.16.1 for Community and Enterprise editions. KMS operations now occur outside of the transaction, and a max request duration for GRPC requests is now set based on the cluster's listener configuration.
     <br /><br />
     <a href="/boundary/tutorials/self-managed-deployment/upgrade-version">Upgrade to the latest version of Boundary</a>
     </td>