diff --git a/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx b/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx
index ac5e69aaf0a..7d5b4b340b4 100644
--- a/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx
+++ b/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx
@@ -14,7 +14,7 @@ EDB Postgres Distributed 5.6.1 includes a number of enhancements and bug fixes.
 
 ## Features
 
-<table class="table w-100"><thead><tr><th>Component</th><th>Version</th><th width="75%">Description</th><th width="10%">Addresses</th></tr></thead><tbody>
+<table class="table w-100"><thead><tr><th>Component</th><th>Version</th><th>Description</th><th width="10%">Addresses</th></tr></thead><tbody>
 <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Added Postgres 17 support</summary><hr/><p>Support for Postgres 17 has been added for all flavors (PostgreSQL, EDB Postgres Extended,
 and EDB Postgres Advanced Server) starting with version 17.2.</p>
 </details></td><td></td></tr>
@@ -45,6 +45,8 @@ Additionally, the <code>bdr_get_all_origins</code> function now considers SO nod
 topology configuration, the LSN progress of all data nodes is periodically communicated to these
 subscriber-only nodes through logical replication.</p>
 </details></td><td></td></tr>
+<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Some DDL commands are now allowed by <code>bdr.permit_unsafe_commands</code> when set.</summary><hr/><p>The <code>bdr.permit_unsafe_commands</code> parameter now allows some DDL commands that were previously disallowed. Specifically <code>ALTER COLUMN...TYPE...USING</code> can now be permitted if the user knows the operation is safe.</p>
+</details></td><td></td></tr>
 </tbody></table>
 
 
@@ -80,6 +82,8 @@ enabled</p>
 </details></td><td></td></tr>
 <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Stopped creation of slots for subscriber only nodes on witness nodes.</summary><hr/><p>Subscriber only nodes should not have slots on witness nodes.</p>
 </details></td><td></td></tr>
+<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Ensure no waiting for DEGRADE timeout when in an already degraded state.</summary><hr/><p>When using commit scope with DEGRADE clause, if system detects that it's in degraded state, transactions should start in the DEGRADE mode. This ensures that the timeout is not applied on every commit.</p>
+</details></td><td></td></tr>
 <tr><td>PGD Proxy</td><td>5.6.1</td><td><details><summary>Fixed routing strategy for read nodes.</summary><hr/><p>Corrected routing strategy for read nodes after a network partition.</p>
 </details></td><td></td></tr>
 </tbody></table>
diff --git a/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml b/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml
index e62ff6c7547..ddfd29bf032 100644
--- a/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml
+++ b/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml
@@ -152,25 +152,21 @@ relnotes:
   type: Bug-fix
   severity: High
   impact: High
-- relnote: Allow (some) disallowed DDL when bdr.permit_unsafe_commands is enabled
+- relnote: Some DDL commands are now allowed by `bdr.permit_unsafe_commands` when set.
   component: BDR
   component_version: 5.6.1
   details: |
-    Some DDL commands can be safe in situations PGD does not allow them yet. For example rewriting
-    ALTER TABLE that only does immutable conversions. The `bdr.permit_unsafe_commands` now allows user
-    to override the safety check and execute the command anyway, if they are know the command is safe.
+    The `bdr.permit_unsafe_commands` parameter now allows some DDL commands that were previously disallowed. Specifically `ALTER COLUMN...TYPE...USING` can now be permitted if the user knows the operation is safe.
   jira: ""
   addresses: ""
   type: Enhancement
   severity: High
   impact: High
-- relnote: Don't wait for DEGRADE clause in every session
+- relnote: Ensure no waiting for DEGRADE timeout when in an already degraded state.
   component: BDR
   component_version: 5.6.1
   details: |
-    When using commit scope with DEGRADE clause, the transactions are supposed to start in DEGRADE
-    mode already if system detects that it's in degraded state, so that the timeout is not
-    applied on every commit. 
+    When using commit scope with DEGRADE clause, if system detects that it's in degraded state, transactions should start in the DEGRADE mode. This ensures that the timeout is not applied on every commit. 
   jira: BDR-5651
   addresses: ""
   type: Bug-fix