diff --git a/modules/sysadmin_guide/nav.adoc b/modules/sysadmin_guide/nav.adoc
index 75e5238..ad7d756 100644
--- a/modules/sysadmin_guide/nav.adoc
+++ b/modules/sysadmin_guide/nav.adoc
@@ -47,7 +47,7 @@
 ** xref:guestedit.adoc[Guest Editing - SOP]
 ** xref:haproxy.adoc[Haproxy Infrastructure - SOP]
 ** xref:hotfix.adoc[HOTFIXES - SOP]
-** xref:hotness.adoc[hotness - SOP in review ]
+** xref:hotness.adoc[The New Hotness - SOP]
 ** xref:index.adoc[index - SOP in review ]
 ** xref:infra-git-repo.adoc[infra-git-repo - SOP in review ]
 ** xref:infra-hostrename.adoc[infra-hostrename - SOP in review ]
diff --git a/modules/sysadmin_guide/pages/hotness.adoc b/modules/sysadmin_guide/pages/hotness.adoc
index ce0b151..1bfbce5 100644
--- a/modules/sysadmin_guide/pages/hotness.adoc
+++ b/modules/sysadmin_guide/pages/hotness.adoc
@@ -17,15 +17,7 @@ Contact::
 Persons::
   zlopez
 Location::
-  iad2.fedoraproject.org
-Servers::
-  Production
-  +
-  * hotness01.iad2.fedoraproject.org
-  +
-  Staging
-  +
-  * hotness01.stg.iad2.fedoraproject.org
+  os.fedoraproject.org
 Purpose::
   File issues when upstream projects release new versions of a package
 
@@ -34,7 +26,6 @@ Purpose::
 The current deployment is made up of the-new-hotness OpenShift
 namespace.
 
-[[the-new-hotness-1]]
 === the-new-hotness
 
 This OpenShift namespace runs following pods:
@@ -43,7 +34,7 @@ This OpenShift namespace runs following pods:
 
 This OpenShift project relies on:
 
-* `anitya-sop` as message publisher
+* xref:anitya.adoc[Anitya] as message publisher
 * Fedora messaging RabbitMQ hub for consuming messages
 * Koji for scratch builds
 * Bugzilla for issue reporting
@@ -56,8 +47,7 @@ documentation].
 
 === Deploying
 
-Staging deployment of the-new-hotness is deployed in OpenShift on
-os-master01.stg.iad2.fedoraproject.org.
+Staging deployment of the-new-hotness is deployed in staging OpenShift.
 
 To deploy staging instance of the-new-hotness you need to push changes
 to staging branch on
@@ -65,8 +55,7 @@ https://github.com/fedora-infra/the-new-hotness[the-new-hotness GitHub].
 GitHub webhook will then automatically deploy a new version of
 the-new-hotness on staging.
 
-Production deployment of the-new-hotness is deployed in OpenShift on
-os-master01.iad2.fedoraproject.org.
+Production deployment of the-new-hotness is deployed in production OpenShift.
 
 To deploy production instance of the-new-hotness you need to push
 changes to production branch on
@@ -78,7 +67,7 @@ the-new-hotness on production.
 
 To deploy the new configuration, you need
 https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/sshaccess.html[ssh
-access] to batcave01.iad2.fedoraproject.org and
+access] to _batcave01.iad2.fedoraproject.org_ and
 https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/ansible.html[permissions
 to run the Ansible playbook].
 
@@ -126,7 +115,7 @@ It can be nice to check up on the-new-hotness to make sure its behaving
 correctly. You can see all the Bugzilla activity using the
 https://bugzilla.redhat.com/page.cgi?id=user_activity.html[user activity
 query] (staging uses
-https://partner-bugzilla.redhat.com/page.cgi?id=user_activity.html[partner-bugzilla.redhat.com])
+https://bugzilla.stage.redhat.com//page.cgi?id=user_activity.html[bugzilla.stage.redhat.com])
 and querying for the `upstream-release-monitoring@fedoraproject.org`
 user.