Update known issue text about GHES 3.6 replica upgrade warning (#31310)

Co-authored-by: Roger D. Winans <solvaholic@users.noreply.github.com>
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>

data/release-notes/enterprise-server/3-6/0.yml

@@ -299,4 +299,4 @@ sections:
     - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
     - '{% data reusables.release-notes.ghas-3.4-secret-scanning-known-issue %}'
     - |
-      Running `ghe-repl-status` while upgrading a replica node may indicate `WARNING: git replication is behind the primary`. This warning is due to a change in how GitHub Enterprise Server 3.6.0 and later stores repositories. You can safely ignore this message, and the upgrade will proceed normally. [Updated: 2022-09-26]
+      After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue, [contact {% data variables.contact.enterprise_support %}](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket). [Updated: 2022-10-03]

data/release-notes/enterprise-server/3-6/1.yml

@@ -32,4 +32,4 @@ sections:
     - In some cases, users cannot convert existing issues to discussions.
     - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
     - |
-      Running `ghe-repl-status` while upgrading a replica node may indicate `WARNING: git replication is behind the primary`. This warning is due to a change in how GitHub Enterprise Server 3.6.0 and later stores repositories. You can safely ignore this message, and the upgrade will proceed normally. [Updated: 2022-09-26]
+      After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]

data/release-notes/enterprise-server/3-6/2.yml

@@ -41,5 +41,5 @@ sections:
     - In some cases, users cannot convert existing issues to discussions.
     - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter.
     - |
-      Running `ghe-repl-status` while upgrading a replica node may indicate `WARNING: git replication is behind the primary`. This warning is due to a change in how GitHub Enterprise Server 3.6.0 and later stores repositories. You can safely ignore this message, and the upgrade will proceed normally. [Updated: 2022-09-26]
-    - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'
+      After upgrading a replica node to GitHub Enterprise Server 3.6.0 or later and restarting replication, in some situations Git replication may stop progressing and continue to show `WARNING: git replication is behind the primary …`. If you encounter this known issue contact GitHub Support. For more information, see "[Creating a support ticket](https://docs.github.com/en/enterprise-server@3.6/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-10-03]
+    - '{% data reusables.release-notes.2022-09-hotpatch-issue %}'