Merge pull request #2222 from cgoveas/main

Broken doc links

docs/source/Overview/NetworkTopologies/dedicated.rst

@@ -1,27 +1,27 @@
 Network Topology: Dedicated Setup
 =================================
 
+
+
 Depending on internet access for host nodes, there are two ways to achieve a dedicated NIC setup:
 
 .. image:: ../../images/omnia_network_Dedicated.png
 
 
-1. Dedicated Setup with dedicated public NIC on cluster  nodes
-
+1. Dedicated Setup with dedicated public NIC on compute nodes
 
 
-When all cluster  nodes have their own public network access, ``primary_dns`` and ``secondary_dns`` in ``provision_config.yml`` become optional variables as the control plane is not required to be a gateway to the network. The network design would follow the below diagram:
 
+When all compute nodes have their own public network access, ``primary_dns`` and ``secondary_dns`` in ``provision_config.yml`` become optional variables as the control plane is not required to be a gateway to the network. The network design would follow the below diagram:
 
 
-2. Dedicated Setup with single NIC on cluster  nodes
 
+2. Dedicated Setup with single NIC on compute nodes
 
 
-When all cluster  nodes rely on the control plane for public network access, the variables ``primary_dns`` and ``secondary_dns`` in ``provision_config.yml`` are used to indicate that the control plane is the gateway for all cluster  nodes to get internet access. Since all public network traffic will be routed through the control plane, the user may have to take precautions to avoid bottlenecks in such a set-up.
 
-**Recommended discovery mechanism**
+When all compute nodes rely on the control plane for public network access, the variables ``primary_dns`` and ``secondary_dns`` in ``provision_config.yml`` are used to indicate that the control plane is the gateway for all compute nodes to get internet access. Since all public network traffic will be routed through the control plane, the user may have to take precautions to avoid bottlenecks in such a set-up.
 
-* `mapping <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/mapping.html>`_
-* `snmpwalk <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/snmpwalk.html>`_
 
+* `mapping <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/mappingfile.html>`_
+* `snmpwalk <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/snmp.html>`_

docs/source/Overview/NetworkTopologies/lom.rst

@@ -10,7 +10,7 @@ A LOM port could be shared with the host operating system production traffic. Al
 
 **Recommended discovery mechanism**
 
-* `mapping <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/mapping.html>`_
+* `mapping <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/mappingfile.html>`_
 * `bmc <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/bmc.html>`_
 * `switch-based  <../../InstallationGuides/InstallingProvisionTool/DiscoveryMechanisms/switch-based.html>`_