Update about-ssh-certificate-authorities.md to separate GHEC and GHES information (#57041)

bss-mc · vgrl · web-flow · commit ffc5b41de47c · 2025-08-11T03:25:45.000Z
Co-authored-by: Vanessa &lt;vgrl@github.com&gt;
diff --git a/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md b/content/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md
@@ -39,11 +39,11 @@ Unless you make SSH certificates a requirement, organization members and outside
 
 ## About SSH URLs with SSH certificates
 
-If your organization requires SSH certificates, to prevent authentication errors, organization members and outside collaborators should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@github.com`, the SSH client might offer the wrong key, causing the operation to fail.
+If your organization requires SSH certificates, to prevent authentication errors, organization members and outside collaborators should use a special URL that includes the organization ID when performing Git operations over SSH. This special URL allows the client and server to more easily negotiate which key on the member's computer should be used for authentication. If a member uses the normal URL, which starts with `git@{% data variables.product.product_url %}`, the SSH client might offer the wrong key, causing the operation to fail.
 
 Anyone with read access to the repository can find this URL by selecting the **Code** dropdown menu on the main page of the repository, then clicking **Use SSH**.
 
-If your organization doesn't require SSH certificates, contributors can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@github.com`, will work.
+If your organization doesn't require SSH certificates, contributors can continue to use their own SSH keys, or other means of authentication. In that case, either the special URL or the normal URL, which starts with `git@{% data variables.product.product_url %}`, will work.
 
 ## Issuing certificates
 
diff --git a/data/reusables/organizations/can-require-ssh-cert.md b/data/reusables/organizations/can-require-ssh-cert.md
@@ -1 +1 @@
-You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository.
+You can require that members use SSH certificates to access organization resources{% ifversion ghes %}, unless SSH is disabled in your repository{% endif %}.

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-You can require that members use SSH certificates to access organization resources, unless SSH is disabled in your repository.`
	`1`	`+You can require that members use SSH certificates to access organization resources{% ifversion ghes %}, unless SSH is disabled in your repository{% endif %}.`