diff --git a/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst b/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst
index 1362607d0..c43a9316a 100644
--- a/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst
+++ b/doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst
@@ -386,13 +386,11 @@ subcloud ansible log files: ``/var/log/dcmanager/ansible``, and named as
 
         "DNS.1: registry.local DNS.2: registry.central IP.1: floating_management IP.2: floating_OAM"
 
-    If required, run the following command on the Central Cloud prior to
-    bootstrapping the subcloud to install the new certificate for the Central
-    Cloud with the updated |SAN| list:
-
-    .. code-block:: none
-
-        ~(keystone_admin)]$ system certificate-install -m docker_registry path_to_cert
+    If required, refer to the
+    :ref:`migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d`
+    procedure to update the Docker Registry certificate for the Central Cloud.
+    The procedure will include the  with required Domain Names and IPs in the
+    the certificate's |SAN| list.
 
     If you prefer to install container images from the default external
     registries, make the following substitutions for the **docker_registries**
diff --git a/doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst b/doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst
index 819daacb8..bef476617 100644
--- a/doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst
+++ b/doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst
@@ -282,13 +282,11 @@ subcloud, the subcloud installation process has two phases:
     list ``"DNS.1: registry.local DNS.2: registry.central IP.1: <floating
     management\> IP.2: <floating OAM\>"``.
 
-    If required, run the following command on the Central Cloud prior to
-    bootstrapping the subcloud to install the new certificate for the Central
-    Cloud with the updated |SAN| list:
-
-    .. code-block:: none
-
-        ~(keystone_admin)]$ system certificate-install -m docker_registry path_to_cert
+    If required, refer to the
+    :ref:`migrate-platform-certificates-to-use-cert-manager-c0b1727e4e5d`
+    procedure to update the Docker Registry certificate for the Central Cloud.
+    The procedure will include the  with required Domain Names and IPs in the
+    the certificate's |SAN| list.
 
 #. Post installation, run the following command to add a subcloud on the system
    controller.