diff --git a/guides/common/modules/proc_registering-a-host.adoc b/guides/common/modules/proc_registering-a-host.adoc
index ccc08ccf9e..8da3bb47bc 100644
--- a/guides/common/modules/proc_registering-a-host.adoc
+++ b/guides/common/modules/proc_registering-a-host.adoc
@@ -67,6 +67,18 @@ If an attacker, located in the network between {Project} and your host, fetches
 Therefore, if you have chosen to deploy SSH keys during registration, the attacker will be able to access your host using the SSH key.
 * On the *Advanced* tab, in the *Repositories* field, you can list repositories to be added before the registration is performed.
 You do not have to specify repositories if you provide them in an activation key.
+ifdef::orcharhino[]
+ifdef::debian,ubuntu[]
++
+To verify synchronized {client-content-type} content, you can use the `pulp_deb_signing.key` file on your {SmartProxy} as GPG public key.
+For example, `\https://{foreman-example-com}/pub/pulp_deb_signing.key`.
+endif::[]
+ifndef::debian,ubuntu[]
++
+To verify synchronized {client-content-type} content, you can use {Project} API to get associated GPG public keys of repositories.
+For example, `\https://{foreman-example-com}/katello/api/v2/repositories/_My_Repository_ID_/gpg_key_content`.
+endif::[]
+endif::[]
 * On the *Advanced* tab, in the *Token lifetime (hours)* field, you can change the validity duration of the JSON Web Token (JWT) that {Project} uses for authentication.
 The duration of this token defines how long the generated registration command works.
 +