diff --git a/doc/source/backup/kubernetes/restoring-starlingx-system-data-and-storage.rst b/doc/source/backup/kubernetes/restoring-starlingx-system-data-and-storage.rst
index 0bb0c1b0f..568b70a11 100644
--- a/doc/source/backup/kubernetes/restoring-starlingx-system-data-and-storage.rst
+++ b/doc/source/backup/kubernetes/restoring-starlingx-system-data-and-storage.rst
@@ -321,11 +321,8 @@ conditions are in place:
 
        If the message HEALTH_WARN appears, wait a few minutes and then try
        again. If the warning condition persists, consult the public
-       documentation for troubleshooting Ceph monitors (for example,
-       `http://docs.ceph.com/docs/master/rados/troubleshooting/troubleshootin
-       g-mon/
-       <http://docs.ceph.com/docs/master/rados/troubleshooting/troubleshootin
-       g-mon/>`__).
+       documentation for troubleshooting Ceph monitors (for example
+       http://docs.ceph.com/docs/master/rados/troubleshooting/troubleshooting-mon/).
 
 #. Restore the compute (worker) hosts, one at a time.
 
diff --git a/doc/source/fault-mgmt/kubernetes/snmp-active-alarm-table.rst b/doc/source/fault-mgmt/kubernetes/snmp-active-alarm-table.rst
index f5053fa8f..a4527b555 100644
--- a/doc/source/fault-mgmt/kubernetes/snmp-active-alarm-table.rst
+++ b/doc/source/fault-mgmt/kubernetes/snmp-active-alarm-table.rst
@@ -12,30 +12,30 @@ MIB via |SNMP|.
 The active alarm table contains a list of all active or set alarms in the
 system. Each entry in the table includes the following variables:
 
-- wrsAlarmActiveUuid                      
+- wrsAlarmActiveUuid
 
-- wrsAlarmActiveAlarmId                   
+- wrsAlarmActiveAlarmId
 
-- wrsAlarmActiveEntityInstanceId          
+- wrsAlarmActiveEntityInstanceId
 
-- wrsAlarmActiveDateAndTime               
+- wrsAlarmActiveDateAndTime
 
-- wrsAlarmActiveAlarmSeverity             
+- wrsAlarmActiveAlarmSeverity
 
-- wrsAlarmActiveReasonText                
+- wrsAlarmActiveReasonText
 
-- wrsAlarmActiveEventType                 
+- wrsAlarmActiveEventType
 
-- wrsAlarmActiveProbableCause             
+- wrsAlarmActiveProbableCause
 
-- wrsAlarmActiveProposedRepairAction     
+- wrsAlarmActiveProposedRepairAction
 
-- wrsAlarmActiveServiceAffecting          
+- wrsAlarmActiveServiceAffecting
 
-- wrsAlarmActiveSuppressionAllowed 
+- wrsAlarmActiveSuppressionAllowed
 
 
-See https://opendev.org/starlingx/snmp-armada-app/src/branch/master/stx-snmp-helm/centos/docker/stx-snmp/mibs/wrsAlarmMib.mib.txt
+See https://opendev.org/starlingx/snmp-armada-app/src/branch/master/stx-snmp-helm/docker/stx-snmp/mibs/wrsAlarmMib.mib.txt
 for alarm details.
 
 An external |SNMP| Manager can examine the Active Alarm table contents by doing
diff --git a/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst b/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst
index 17baac97b..897982433 100644
--- a/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst
+++ b/doc/source/guest_integration/kubernetes/ptp-notifications-overview.rst
@@ -39,8 +39,7 @@ PTP-notification consists of two main components:
 
 -   Enables operators to install the **ptp-notification-armada-app**, Sidecar
     container, and the application supporting the REST API. For more information,
-    see, `https://docs.starlingx.io/api-ref/ptp-notification-armada-app/index.html
-    <https://docs.starlingx.io/api-ref/ptp-notification-armada-app/index.html>`__.
+    see https://docs.starlingx.io/api-ref/ptp-notification-armada-app/index.html.
 
 -   Supports the **ptp4l** module and |PTP| port that is configured in
     Subordinate mode (Secondary mode).
diff --git a/doc/source/node_management/index-node-mgmt-cd0f9d8eaee6.rst b/doc/source/node_management/index-node-mgmt-cd0f9d8eaee6.rst
index 2b89fb41b..c1e71574a 100644
--- a/doc/source/node_management/index-node-mgmt-cd0f9d8eaee6.rst
+++ b/doc/source/node_management/index-node-mgmt-cd0f9d8eaee6.rst
@@ -34,8 +34,7 @@ You can change the resource pool in several ways:
     still meets the requirements for your system.
 
 Complete instructions for adding a worker node are provided in the
-`StarlingX Installation and Deployment Guide
-<https://docs.starlingx.io/deploy_install_guides/index.html>`__.
+:ref:`index-install-r7-8966076f0e81`.
 
 .. kub-end
 
diff --git a/doc/source/security/kubernetes/establish-keystone-credentials-from-a-linux-account.rst b/doc/source/security/kubernetes/establish-keystone-credentials-from-a-linux-account.rst
index 2880bfbcc..55bc142a5 100644
--- a/doc/source/security/kubernetes/establish-keystone-credentials-from-a-linux-account.rst
+++ b/doc/source/security/kubernetes/establish-keystone-credentials-from-a-linux-account.rst
@@ -48,7 +48,7 @@ Platform OpenStack |CLIs|, using one of the following methods:
     Keystone user credentials, download an OpenStack RC file (openrc.sh), and
     use it to source the required environment within your local LDAP user shell
     . For more information on downloading your OpenStack RC file from Horizon,
-    see, `http://docs.openstack.org <http://docs.openstack.org/>`__.
+    see http://docs.openstack.org.
 
 #.  (Method 2) Add the required environment variables manually into a
     wrcprc.sh file and use this to source the required environment within your
diff --git a/doc/source/security/kubernetes/install-the-kubernetes-dashboard.rst b/doc/source/security/kubernetes/install-the-kubernetes-dashboard.rst
index 89b17d82c..dda07a08d 100644
--- a/doc/source/security/kubernetes/install-the-kubernetes-dashboard.rst
+++ b/doc/source/security/kubernetes/install-the-kubernetes-dashboard.rst
@@ -112,7 +112,7 @@ Dashboard.
     defined above for |prod| cluster's |OAM| floating IP.
 
 
-    #.  Access the dashboard at https://<fqdn>:32000
+    #.  Access the dashboard at `https://<fqdn>:32000`
 
         Because the certificate created earlier in this procedure was not
         signed by a trusted |CA|, you will need to acknowledge an insecure
diff --git a/doc/source/security/kubernetes/security-access-the-gui.rst b/doc/source/security/kubernetes/security-access-the-gui.rst
index 26ba61d9b..cd14ce147 100644
--- a/doc/source/security/kubernetes/security-access-the-gui.rst
+++ b/doc/source/security/kubernetes/security-access-the-gui.rst
@@ -19,7 +19,7 @@ from a browser.
 
       Access the Horizon in your browser at the address:
 
-      http://<oam-floating-ip-address>:8080
+      `http://<oam-floating-ip-address>:8080`
 
       Use the username **admin** and the sysadmin password to log in.
 
diff --git a/doc/source/storage/kubernetes/replication-groups.rst b/doc/source/storage/kubernetes/replication-groups.rst
index 8178ae47c..125aa8aab 100644
--- a/doc/source/storage/kubernetes/replication-groups.rst
+++ b/doc/source/storage/kubernetes/replication-groups.rst
@@ -48,8 +48,7 @@ member.
     of 20 seconds. This means that a Ceph filesystem may not respond to I/O
     for up to 20 seconds when a storage node or OSD goes out of service.
     For more information, see the Ceph documentation:
-    `http://docs.ceph.com/docs/master/rados/configuration/mon-osd-interaction
-    <http://docs.ceph.com/docs/master/rados/configuration/mon-osd-interaction>`__.
+    http://docs.ceph.com/docs/master/rados/configuration/mon-osd-interaction.
 
 Replication groups are shown on the Hosts Inventory page in association
 with the storage hosts. You can also use the following CLI commands to
diff --git a/doc/source/usertasks/kubernetes/letsencrypt-example.rst b/doc/source/usertasks/kubernetes/letsencrypt-example.rst
index f63c94411..45aefaa5e 100644
--- a/doc/source/usertasks/kubernetes/letsencrypt-example.rst
+++ b/doc/source/usertasks/kubernetes/letsencrypt-example.rst
@@ -140,4 +140,4 @@ This example requires that:
 
 #.  Access the kuard demo from your browser to inspect and verify that the
     certificate is signed by LetsEncrypt |CA|. For this example, the URL
-    would be https://kuard.starlingx.mycompany.com.
+    would be `https://kuard.starlingx.mycompany.com`.