diff --git a/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md b/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
index 7815859b8e..af5c3e50d9 100644
--- a/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
+++ b/content/authentication/troubleshooting-ssh/using-ssh-over-the-https-port.md
@@ -63,7 +63,7 @@ $ ssh -T git@{% data variables.command_line.codeblock %}
## Updating known hosts
-The first time you interact with GitHub after switching to port 443, you may get a warning message
+The first time you interact with {% data variables.product.prodname_dotcom %} after switching to port 443, you may get a warning message
that the host wasn't found in `known_hosts`, or that it was found by another name.
```ShellSession
@@ -75,4 +75,4 @@ that the host wasn't found in `known_hosts`, or that it was found by another nam
```
It is safe to answer "yes" to this question, assuming that the SSH fingerprint matches
-one of GitHub's published fingerprints. For the list of fingerprints, see "[Github's SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
+one of {% data variables.product.prodname_dotcom %}'s published fingerprints. For the list of fingerprints, see "[{% data variables.product.prodname_dotcom %}'s SSH key fingerprints](/authentication/keeping-your-account-and-data-secure/githubs-ssh-key-fingerprints)."
diff --git a/content/site-policy/privacy-policies/github-privacy-statement.md b/content/site-policy/privacy-policies/github-privacy-statement.md
index 7b0ea37303..a370f90c31 100644
--- a/content/site-policy/privacy-policies/github-privacy-statement.md
+++ b/content/site-policy/privacy-policies/github-privacy-statement.md
@@ -286,7 +286,7 @@ United States
[Privacy contact form](https://support.github.com/contact/privacy)
-**Github Data Protection Officer**
+**GitHub Data Protection Officer**
c/o DP Dock DPO Services GmbH,
Attn: GitHub BV, Gut Projensdorf,