Merge pull request #6307 from EnterpriseDB/docs/pgd/fixhimeshreferences

Remove himesh references

product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx

@@ -35,7 +35,7 @@ If the <code>nodename</code> parameter is NULL, the function will wait for all n
 LSN. If the <code>target</code> LSN is NULL, it will wait for the current <code>wal_flush_lsn</code>.</p>
 </details></td><td></td></tr>
 <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Improvements made in SO Node Management and Progress Tracking.</summary><hr/><p>An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in
-progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh
+progress updates. Improvements include enhanced watermark management for SO leaders in the Optimized Topology
 configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted
 to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected,
 and the tap test for group slot movement has been revised.
@@ -72,13 +72,12 @@ that are prone to failure won't consistently impact the success of other tasks.<
 <tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting subscription with standbys.</summary><hr/><p>The parting subscription used to hang, failing to wait for standbys when the
 bdr.standby_slot_names parameter was defined.</p>
 </details></td><td>41821</td></tr>
-<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting SO node with multiple origins.</summary><hr/><p>All relevant origins must be removed when parting SO node
-With himesh, parting an SO node should result in removing all origins it
+<tr><td>BDR</td><td>5.6.1</td><td><details><summary>Fixed parting SO node with multiple origins.</summary><hr/><p>All relevant origins must be removed when parting SO node.
+With Optimized Topology, parting an SO node should result in removing all origins it
 has, not just the one related to its SO group leader.
 When parting a data node, even though there is no subscription to it
-from SO node, the origin should be removed
-DO not make SO node target of a part catchup subscription when himesh
-enabled</p>
+from SO node, the origin should be removed.
+DO not make SO node target of a part catchup subscription when Optimized Topology is 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>

product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml

@@ -104,7 +104,7 @@ relnotes:
   component_version: 5.6.1
   details: |
     An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in
-    progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh
+    progress updates. Improvements include enhanced watermark management for SO leaders in the Optimized Topology
     configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted
     to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected,
     and the tap test for group slot movement has been revised.
@@ -130,13 +130,12 @@ relnotes:
   component: BDR
   component_version: 5.6.1
   details: |
-    All relevant origins must be removed when parting SO node
-    With himesh, parting an SO node should result in removing all origins it
+    All relevant origins must be removed when parting SO node.
+    With Optimized Topology, parting an SO node should result in removing all origins it
     has, not just the one related to its SO group leader.
     When parting a data node, even though there is no subscription to it
-    from SO node, the origin should be removed
-    DO not make SO node target of a part catchup subscription when himesh
-    enabled
+    from SO node, the origin should be removed.
+    DO not make SO node target of a part catchup subscription when Optimized Topology is enabled.
   jira: BDR-5552
   addresses: ""
   type: Bug-fix