github · docs-bot · Oct 17, 2023 · Oct 17, 2023 · Oct 17, 2023
diff --git a/...ub/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md b/...ub/managing-subscriptions-for-activity-on-github/managing-your-subscriptions.md
@@ -17,7 +17,7 @@ To help you understand your subscriptions and decide whether to unsubscribe, see
 
 {% note %}
 
-**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please contact {% data variables.contact.contact_support %} so we can help. {% data reusables.policies.abuse %}{% endif %}
+**Note:** Instead of unsubscribing, you have the option to ignore a repository. If you ignore a repository, you won't receive any notifications. We don't recommend ignoring repositories as you won't be notified if you're @mentioned. {% ifversion fpt or ghec %}If you're experiencing abuse and want to ignore a repository, please visit {% data variables.contact.contact_support_page %} so we can help. {% data reusables.policies.abuse %}{% endif %}
 
 {% endnote %}
 

diff --git a/...ttings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md b/...ttings-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile.md
@@ -100,7 +100,7 @@ If your commits are in a non-default or non-`gh-pages` branch and you'd like the
 
 Commits made in a fork will not count toward your contributions. To make them count, you must do one of the following:
 - [Open a pull request](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) to have your changes merged into the parent repository.
-- To detach the fork and turn it into a standalone repository on {% data variables.location.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, let {% data variables.contact.contact_support %} know if the forks should move with your repository into a new network or remain in the current network. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
+- To detach the fork and turn it into a standalone repository on {% data variables.location.product_location %}, contact {% data variables.contact.contact_support %}. If the fork has forks of its own, state whether the forks should move with your repository into a new network or remain in the current network. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)."
 
 ## Further reading
 

diff --git a/...ries/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md b/...ries/maintaining-ownership-continuity-of-your-personal-accounts-repositories.md
@@ -25,7 +25,7 @@ Successors cannot log into your account.
 
 An appointed successor can manage your public repositories after presenting a death certificate then waiting for 7 days or presenting an obituary then waiting for 21 days. For more information, see "[AUTOTITLE](/free-pro-team@latest/site-policy/other-site-policies/github-deceased-user-policy)."
 
-To request access to manage repositories as a successor, contact [GitHub Support](https://support.github.com/contact?tags=docs-accounts).
+To request access to manage repositories as a successor, please contact us through the {% data variables.contact.contact_support_portal %}.
 
 ## Inviting a successor
 

diff --git a/...ing-your-personal-account/unlinking-your-email-address-from-a-locked-account.md b/...ing-your-personal-account/unlinking-your-email-address-from-a-locked-account.md
@@ -53,4 +53,4 @@ Since an email address can only be associated with a single {% data variables.pr
 
    {% endnote %}
 
-1. Optionally, if you have any form of payment set up on the locked account, contact [{% data variables.contact.github_support %}](https://support.github.com/contact) to cancel future payments. For example, you might have a paid subscription or sponsor developers through {% data variables.product.prodname_sponsors %}. If you are sponsored through {% data variables.product.prodname_sponsors %}, please mention this so that the team can help you migrate your sponsorships.
+1. Optionally, if you have any form of payment set up on the locked account, please contact us through the {% data variables.contact.contact_support_portal %} to cancel future payments. For example, you might have a paid subscription or sponsor developers through {% data variables.product.prodname_sponsors %}. If you are sponsored through {% data variables.product.prodname_sponsors %}, please mention this so that the team can help you migrate your sponsorships.
diff --git a/content/actions/learn-github-actions/usage-limits-billing-and-administration.md b/content/actions/learn-github-actions/usage-limits-billing-and-administration.md
@@ -12,7 +12,7 @@ topics:
   - Billing
 shortTitle: Workflow billing & limits
 ---
- 
+
 {% data reusables.actions.enterprise-github-hosted-runners %}
 
 ## About billing for {% data variables.product.prodname_actions %}
@@ -66,7 +66,7 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
 
   {% note %}
 
-  **Note:** If required, customers on enterprise plans can request a higher limit for concurrent jobs. For more information, contact {% data variables.contact.contact_ent_support %} or your sales representative.
+  **Note:** If required, customers on enterprise plans can request a higher limit for concurrent jobs. For more information, contact us through the {% data variables.contact.contact_support_portal %}, or contact your sales representative.
 
   {% endnote %}
 

diff --git a/...g-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh.md b/...g-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh.md
@@ -70,4 +70,4 @@ In an emergency situation, for example if SSH is unavailable, you can access the
 
 ## Access limitations for the administrative shell
 
-Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please contact {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
+Administrative shell access is permitted for troubleshooting and performing documented operations procedures only. Modifying system and application files, running programs, or installing unsupported software packages may void your support contract. Please visit {% data variables.contact.contact_ent_support %} if you have a question about the activities allowed by your support contract.
diff --git a/...nce/administering-your-instance-from-the-command-line/command-line-utilities.md b/...nce/administering-your-instance-from-the-command-line/command-line-utilities.md
@@ -62,7 +62,7 @@ This utility can help identify whether the Aqueduct server is having problems pr
 - Webhooks are not being triggered.
 - The web interface is not updating after a Git push.
 
-If you suspect Aqueduct is failing, contact {% data variables.contact.contact_ent_support %} for help.
+If you suspect Aqueduct is failing, visit {% data variables.contact.contact_ent_support %} for help.
 
 With this command, you can also pause or resume jobs in the queue.
 

diff --git a/.../backing-up-and-restoring-your-instance/configuring-backups-on-your-instance.md b/.../backing-up-and-restoring-your-instance/configuring-backups-on-your-instance.md
@@ -274,7 +274,7 @@ Optionally, to validate the restore, configure an IP exception list to allow acc
 
 On an instance in a high-availability configuration, after you restore to new disks on an existing or empty instance, `ghe-repl-status` may report that Git or Alambic replication is out of sync due to stale server UUIDs. These stale UUIDs can be the result of a retired node in a high-availability configuration still being present in the application database, but not in the restored replication configuration.
 
-To remediate after the restoration completes and before starting replication, you can tear down stale UUIDs using `ghe-repl-teardown`. If you need further assistance, contact {% data variables.contact.contact_ent_support %}.
+To remediate after the restoration completes and before starting replication, you can tear down stale UUIDs using `ghe-repl-teardown`. If you need further assistance, visit {% data variables.contact.contact_ent_support %}.
 
 {% ifversion backup-utilities-progress %}
 

diff --git a/...nfiguration/configuring-network-settings/configuring-built-in-firewall-rules.md b/...nfiguration/configuring-network-settings/configuring-built-in-firewall-rules.md
@@ -63,7 +63,7 @@ We do not recommend customizing UFW as it can complicate some troubleshooting is
 
 {% warning %}
 
-**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, contact {% data variables.contact.contact_ent_support %} to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server.
+**Warning:** Before you add custom firewall rules, back up your current rules in case you need to reset to a known working state. If you're locked out of your server, visit {% data variables.contact.contact_ent_support %} and contact us to reconfigure the original firewall rules. Restoring the original firewall rules involves downtime for your server.
 
 {% endwarning %}
 
@@ -88,7 +88,7 @@ If something goes wrong after you change the firewall rules, you can reset the r
 
 {% warning %}
 
-**Warning:** If you didn't back up the original rules before making changes to the firewall, contact {% data variables.contact.contact_ent_support %} for further assistance.
+**Warning:** If you didn't back up the original rules before making changes to the firewall, visit {% data variables.contact.contact_ent_support %} and contact us for further assistance.
 
 {% endwarning %}
 

diff --git a/...ng-user-applications-for-your-enterprise/configuring-email-for-notifications.md b/...ng-user-applications-for-your-enterprise/configuring-email-for-notifications.md
@@ -190,7 +190,7 @@ If {% data variables.location.product_location %} is behind a firewall or is bei
 ### Contact support
 
 {% ifversion ghes %}
-If you're still unable to resolve the problem, contact {% data variables.contact.contact_ent_support %}. Please attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email to help us troubleshoot your problem.
+If you're still unable to resolve the problem, contact us by visiting {% data variables.contact.contact_ent_support %}. Please attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email to help us troubleshoot your problem.
 {% elsif ghae %}
 You can contact {% data variables.contact.github_support %} for help configuring email for notifications to be sent through your SMTP server. For more information, see "[AUTOTITLE](/support/contacting-github-support)."
 {% endif %}
diff --git a/...dmin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md b/...dmin/identity-and-access-management/using-ldap-for-enterprise-iam/using-ldap.md
@@ -173,7 +173,7 @@ This has the potential to disclose sensitive organizational information to contr
 - The existence of specific LDAP Groups visible to the _Domain search user_.
 - Members of the LDAP group who have {% data variables.product.prodname_ghe_server %} user accounts, which is disclosed when creating a team synced with that LDAP group.
 
-If disclosing such information is not desired, your company or organization should restrict the permissions of the configured _Domain search user_ in the admin console. If such restriction isn't possible, contact {% data variables.contact.contact_ent_support %}.
+If disclosing such information is not desired, your company or organization should restrict the permissions of the configured _Domain search user_ in the admin console. If such restriction isn't possible, contact us by visiting {% data variables.contact.contact_ent_support %}.
 
 {% endwarning %}
 

diff --git a/...in-your-enterprise/exploring-user-activity-in-your-enterprise/log-forwarding.md b/...in-your-enterprise/exploring-user-activity-in-your-enterprise/log-forwarding.md
@@ -51,5 +51,5 @@ When you enable log forwarding, you must upload a CA certificate to encrypt comm
 
 ## Troubleshooting
 
-If you run into issues with log forwarding, contact {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your email.
+If you run into issues with log forwarding, contact us by visiting {% data variables.contact.contact_ent_support %} and attach the output file from `http(s)://[hostname]/setup/diagnostics` to your message.
 {% endif %}
diff --git a/...e/configuring-high-availability/monitoring-a-high-availability-configuration.md b/...e/configuring-high-availability/monitoring-a-high-availability-configuration.md
@@ -114,7 +114,7 @@ ghe-storage info OID
 
 ### Getting support from {% data variables.product.company_short %}
 
-If you review the troubleshooting advice for replication and continue to experience issues on your instance, collect the following information, then contact {% data variables.contact.contact_ent_support %}.
+If you review the troubleshooting advice for replication and continue to experience issues on your instance, collect the following information, then contact us by visiting {% data variables.contact.contact_ent_support %}.
 
 - On each affected node, run `ghe-repl-status -vv`, then copy the output to your ticket. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/command-line-utilities#ghe-repl-status)."
 - On each affected node, create a support bundle to attach to your ticket. For more information, see "[AUTOTITLE](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)."
diff --git a/...ating-your-instance/monitoring-your-instance/accessing-the-monitor-dashboard.md b/...ating-your-instance/monitoring-your-instance/accessing-the-monitor-dashboard.md
@@ -41,5 +41,5 @@ Use the monitor dashboard to stay informed on your appliance's resource health a
 | High CPU usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use fewer CPU resources. To increase total CPU resources for the VM, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)." |
 | High memory usage | VM contention from other services or programs running on the same host | If possible, reconfigure other services or programs to use less memory. To increase the total memory available on the VM, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources)." |
 | Low disk space availability | Large binaries or log files consuming disk space | If possible, host large binaries on a separate server, and compress or archive log files. If necessary, increase disk space on the VM by following the steps for your platform in "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-storage-capacity)." |
-| Higher than usual response times | Often caused by one of the above issues | Identify and fix the underlying issues. If response times remain high, contact {% data variables.contact.contact_ent_support %}. |
-| Elevated error rates | Software issues  | Contact {% data variables.contact.contact_ent_support %} and include your support bundle. For more information, see "[Providing data to {% data variables.product.prodname_enterprise %} Support](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." |
+| Higher than usual response times | Often caused by one of the above issues | Identify and fix the underlying issues. If response times remain high, contact us by visiting {% data variables.contact.contact_ent_support %}. |
+| Elevated error rates | Software issues  | Contact us by visiting {% data variables.contact.contact_ent_support %} and include your support bundle. For more information, see "[Providing data to {% data variables.product.prodname_enterprise %} Support](/enterprise/{{ currentVersion}}/admin/guides/enterprise-support/providing-data-to-github-support#creating-and-sharing-support-bundles)." |
diff --git a/...our-instance/monitoring-your-instance/configuring-collectd-for-your-instance.md b/...our-instance/monitoring-your-instance/configuring-collectd-for-your-instance.md
@@ -61,7 +61,7 @@ By default, `collectd` forwarding is disabled on {% data variables.product.prodn
 
 The command-line tool `ghe-export-graphs` will export the data that `collectd` stores in RRD databases. This command turns the data into XML and exports it into a single tarball (`.tgz`).
 
-Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting.
+Its primary use is to provide the {% data variables.contact.contact_ent_support %} team with data about a VM's performance, without the need for downloading a full Support Bundle. It shouldn't be included in your regular backup exports and there is no import counterpart. If you contact us through {% data variables.contact.contact_ent_support %}, we may ask for this data to assist with troubleshooting.
 
 ### Usage
 
@@ -75,4 +75,4 @@ ssh -p 122 admin@[hostname] -- 'ghe-export-graphs' && scp -P 122 admin@[hostname
 
 {% data variables.product.prodname_enterprise %} ships with `collectd` version 5.x. `collectd` 5.x is not backwards compatible with the 4.x release series. Your central `collectd` server needs to be at least version 5.x to accept data sent from {% data variables.location.product_location %}.
 
-For help with further questions or issues, contact {% data variables.contact.contact_ent_support %}.
+For help with further questions or issues, visit {% data variables.contact.contact_ent_support %}.
diff --git a/...tance/monitoring-your-instance/generating-a-health-check-for-your-enterprise.md b/...tance/monitoring-your-instance/generating-a-health-check-for-your-enterprise.md
@@ -38,10 +38,10 @@ If you're a Premium Plus customer and want to generate a Health Check for {% dat
 
 Before you can generate a Health Check, you must create a support bundle. For more information, see "[AUTOTITLE](/support/contacting-github-support/providing-data-to-github-support#creating-and-sharing-support-bundles)."
 
-1. Navigate to the [{% data variables.contact.support_portal %}](https://support.github.com/).
+1. Navigate to the {% data variables.contact.contact_landing_page_portal %}.
 1. In the upper-right corner of the page, click **Premium**.
 1. To the right of **Health Checks**, click **Request Health Check**.
 1. Under "Select an enterprise account", use the drop-down menu to select an enterprise account.
 1. Under "Upload a support bundle", click **Chose File** and choose a file to upload. Then, click **Request Health Check**.
 
-After you request a Health Check, a job is scheduled to generate the Health Check. After several hours to one day, the generated Health Check will appear in the "Health Checks" section of the {% data variables.contact.support_portal %}.
+After you request a Health Check, a job is scheduled to generate the Health Check. After several hours to one day, the generated Health Check will appear in the "Health Checks" section of the {% data variables.contact.landing_page_portal %}.
diff --git a/...nce/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md b/...nce/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md
@@ -18,7 +18,7 @@ topics:
 {% note %}
 
 **Notes:**
-- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, contact {% data variables.contact.contact_ent_support %} for assistance.
+- Upgrade packages are available at [enterprise.github.com](https://enterprise.github.com/releases) for supported versions. Verify the availability of the upgrade packages you will need to complete the upgrade. If a package is not available, visit {% data variables.contact.contact_ent_support %} and contact us for assistance.
 - If you're using {% data variables.product.prodname_ghe_server %} Clustering, see "[AUTOTITLE](/admin/enterprise-management/configuring-clustering/upgrading-a-cluster)" in the {% data variables.product.prodname_ghe_server %} Clustering Guide for specific instructions unique to clustering.
 - The release notes for {% data variables.product.prodname_ghe_server %} provide a comprehensive list of new features for every version of {% data variables.product.prodname_ghe_server %}. For more information, see the [releases page](https://enterprise.github.com/releases).
 

diff --git a/...ub-marketplace/github-marketplace-overview/about-github-marketplace-for-apps.md b/...ub-marketplace/github-marketplace-overview/about-github-marketplace-for-apps.md
@@ -64,4 +64,4 @@ You can access metrics and transactions for your listing. For more information,
 
 ## Contacting Support
 
-If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %} directly.
+If you have questions about {% data variables.product.prodname_marketplace %}, please contact {% data variables.contact.contact_support %}.