diff --git a/docs/infrastructure-management/devices/device-add-edit.mdx b/docs/infrastructure-management/devices/device-add-edit.mdx
index 28427c89..4aba039e 100644
--- a/docs/infrastructure-management/devices/device-add-edit.mdx
+++ b/docs/infrastructure-management/devices/device-add-edit.mdx
@@ -138,7 +138,7 @@ Consider the following example of a network switch:
 
 ### Non-Editable Fields 
 
-Fields populated through EnrichAI Data, like **OS Version** or OS **End of Life**, are not editable. To set these fields, you need to [disable EnrichAI Data](auto-discovery/enrichai-data/enrichai-opt-out.md) and disconnect the record from the EnrichAI Data record.
+Fields populated through EnrichAI Data, like **OS Version** or OS **End of Life**, are not editable. To set these fields, you need to [disable EnrichAI Data](auto-discovery/enrichai-data/enrichai-opt-out.mdx) and disconnect the record from the EnrichAI Data record.
 
 <ThemedImage
   alt="Non-editable fields"
diff --git a/docs/infrastructure-management/operating-systems.md b/docs/infrastructure-management/operating-systems.md
index adf9a763..726466eb 100644
--- a/docs/infrastructure-management/operating-systems.md
+++ b/docs/infrastructure-management/operating-systems.md
@@ -19,7 +19,7 @@ If the operating system record has been enriched, key maintenance dates may be d
 
 ![Windows device EnrichAI data example](/assets/images/operating-system-enrichai-data.png)
 
-See the [Operating System Attributes](auto-discovery/enrichai-data/index.md#operating-system-attributes) and [Key Support Dates](auto-discovery/enrichai-data/index.md#key-support-dates) sections of the [EnrichAI Data](auto-discovery/enrichai-data/#operating-system-attributes) page for the list of fields that can be populated through EnrichAI.
+See the [Operating System Attributes](auto-discovery/enrichai-data/index.mdx#operating-system-attributes) and [Key Support Dates](auto-discovery/enrichai-data/index.mdx#key-support-dates) sections of the [EnrichAI Data](auto-discovery/enrichai-data/#operating-system-attributes) page for the list of fields that can be populated through EnrichAI.
 
 Note that data will only be populated by EnrichAI if it's used by the OS vendor and if the data is available.
 
diff --git a/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.md b/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.md
index ac3ade98..938843e0 100644
--- a/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.md
+++ b/docs/infrastructure-management/power-and-environmental-monitoring/getting-started-with-power-and-environmental-monitoring.md
@@ -45,9 +45,7 @@ The actual monitoring occurs in a separate virtual appliance from the main Devic
 
 The installation process for one or more monitoring appliances is similar to installation of the Device42 main appliance. If you would like to set up power monitoring using a Remote Collector (RC), see the [instructions for setting up an RC](auto-discovery/remote-collector-rc.mdx).
 
-Refer to the appropriate link(s) below for installation on your selected virtualization platform:  
-\- [VMWare Player](getstarted/installation/installation-vmware-player.mdx)  
-\- [Virtual Box](getstarted/installation/installation-virtual-box.md)  
+Refer to the appropriate link(s) below for installation on your selected virtualization platform:
 \- [Citrix Xen Server](getstarted/installation/installation-citrix-xen-server.mdx)  
 \- [Microsoft Hyper V](getstarted/installation/installation-microsoft-hyperv.md)  
 \- [vCenter Server](getstarted/installation/installation-vcenter-server.md)
diff --git a/docs/integration/external-integrations/cloud-services-settings.md b/docs/integration/external-integrations/cloud-services-settings.md
index 50dd7f67..3f8888c6 100644
--- a/docs/integration/external-integrations/cloud-services-settings.md
+++ b/docs/integration/external-integrations/cloud-services-settings.md
@@ -3,7 +3,7 @@ title: "Cloud Services Settings"
 sidebar_position: 6
 ---
 
-Device42 includes a new Cloud Services page that you can use to specify external integration settings. Device42 cloud services includes product registration services and [EnrichAI Data](auto-discovery/enrichai-data/index.md) normalization for discovered data. This information was formerly part of the Global Settings page.
+Device42 includes a new Cloud Services page that you can use to specify external integration settings. Device42 cloud services includes product registration services and [EnrichAI Data](auto-discovery/enrichai-data/index.mdx) normalization for discovered data. This information was formerly part of the Global Settings page.
 
 ## Integration Settings
 
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 10a0794e..a3da4100 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -95,10 +95,6 @@ const config = {
             to: '/getstarted/installation/installation-microsoft-hyperv/',
             from: ['/getstarted/installation/installation-microsoft-hyper/'],
           },
-          {
-            to: '/getstarted/installation/installation-vmware-player/',
-            from: ['/getstarted/installation/installation-vmware-player-workstation-2/'],
-          },
           {
             to: '/getstarted/installation/installation-xen-or-kvm-using-virt-manager/',
             from: ['/getstarted/installation/installation-xen-kvm-virt-manager/'],