Merge pull request #27 from ritza-co/rename-sub-cats

Rename sub cats
device42 · Aug 2, 2023 · b28c5d0 · b28c5d0
2 parents a9284cb + 5f1ef2c
commit b28c5d0
Show file tree

Hide file tree

Showing 87 changed files with 100 additions and 112 deletions.
diff --git a/...stration/appliance_manager/_category_.yml → ...stration/appliance-manager/_category_.yml b/...stration/appliance_manager/_category_.yml → ...stration/appliance-manager/_category_.yml
diff --git a/...work-interface-cardsnic-to-device42-vm.md → ...work-interface-cardsnic-to-device42-vm.md b/...work-interface-cardsnic-to-device42-vm.md → ...work-interface-cardsnic-to-device42-vm.md
diff --git a/...istration/appliance_manager/api-limits.md → ...istration/appliance-manager/api-limits.md b/...istration/appliance_manager/api-limits.md → ...istration/appliance-manager/api-limits.md
diff --git a/...r/changing-device42-appliance-hostname.md → ...r/changing-device42-appliance-hostname.md b/...r/changing-device42-appliance-hostname.md → ...r/changing-device42-appliance-hostname.md
diff --git a/...ng-snmpwalk-output-for-troubleshooting.md → ...ng-snmpwalk-output-for-troubleshooting.md b/...ng-snmpwalk-output-for-troubleshooting.md → ...ng-snmpwalk-output-for-troubleshooting.md
diff --git a/.../appliance_manager/delete-history-logs.md → .../appliance-manager/delete-history-logs.md b/.../appliance_manager/delete-history-logs.md → .../appliance-manager/delete-history-logs.md
diff --git a/...nager/device42-appliance-manager-login.md → ...nager/device42-appliance-manager-login.md b/...nager/device42-appliance-manager-login.md → ...nager/device42-appliance-manager-login.md
diff --git a/...ion/appliance_manager/device42-restore.md → ...ion/appliance-manager/device42-restore.md b/...ion/appliance_manager/device42-restore.md → ...ion/appliance-manager/device42-restore.md
@@ -35,7 +35,7 @@ Active directory settings are crucial for logging back in. Otherwise, you can us
 
 Restore will delete all current data in the appliance. If you are doing a test restore, we recommend the following two options:
 
-1. Spin up a new device42 virtual appliance and restore there. Note: A second instance can also be used for disaster recovery / business continuity purposes. As described in our ["Warm HA Configuration."](administration/appliance_manager/warm-ha-setup-failover-and-automated-backups.md)
+1. Spin up a new device42 virtual appliance and restore there. Note: A second instance can also be used for disaster recovery / business continuity purposes. As described in our ["Warm HA Configuration."](administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.md)
 
 (Your license allows one production and one backup instance.)
 

diff --git a/...le-tls-versions-from-appliance-manager.md → ...le-tls-versions-from-appliance-manager.md b/...le-tls-versions-from-appliance-manager.md → ...le-tls-versions-from-appliance-manager.md
diff --git a/...ager/enabling-ssl-in-appliance-manager.md → ...ager/enabling-ssl-in-appliance-manager.md b/...ager/enabling-ssl-in-appliance-manager.md → ...ager/enabling-ssl-in-appliance-manager.md
diff --git a/.../appliance_manager/generate-log-bundle.md → .../appliance-manager/generate-log-bundle.md b/.../appliance_manager/generate-log-bundle.md → .../appliance-manager/generate-log-bundle.md
@@ -9,7 +9,7 @@ To generate log bundle for a support call:
 
     ![Enable debug by editing discovery job settings](/assets/images/edit_discovery_debug_hl-note.png)
 2. _(If your issues are NOT autodiscovery related, skip to step 3)_ If your issue is AutoDiscovery related, re-run the failing autodiscovery job now that you've enabled the debug flag.
-3. Login to the appliance manager via the main menu, _Tools -> Appliance Manager_ or follow these directions: [administration/appliance_manager/device42-appliance-manager-login.md](administration/appliance_manager/device42-appliance-manager-login.md)
+3. Login to the appliance manager via the main menu, _Tools -> Appliance Manager_ or follow these directions: [administration/appliance-manager/device42-appliance-manager-login.md](administration/appliance-manager/device42-appliance-manager-login.md)
 4. **Application > Generate Log Bundle > Run**
 
     ![Generate Log Bundle via Appliance Manager](/assets/images/app-mgr_generate_log_bundle.png)
diff --git a/...rating-ipmi-output-for-troubleshooting.md → ...rating-ipmi-output-for-troubleshooting.md b/...rating-ipmi-output-for-troubleshooting.md → ...rating-ipmi-output-for-troubleshooting.md
diff --git a/...l-and-password-manager-session-timeout.md → ...l-and-password-manager-session-timeout.md b/...l-and-password-manager-session-timeout.md → ...l-and-password-manager-session-timeout.md
diff --git a/...r/installing-vmware-or-xenserver-tools.md → ...r/installing-vmware-or-xenserver-tools.md b/...r/installing-vmware-or-xenserver-tools.md → ...r/installing-vmware-or-xenserver-tools.md
diff --git a/...tours-and-usage-information-collection.md → ...tours-and-usage-information-collection.md b/...tours-and-usage-information-collection.md → ...tours-and-usage-information-collection.md
diff --git a/.../securing-the-vm-console-with-password.md → .../securing-the-vm-console-with-password.md b/.../securing-the-vm-console-with-password.md → .../securing-the-vm-console-with-password.md
diff --git a/...liance_manager/set-fqdn-for-web-access.md → ...liance-manager/set-fqdn-for-web-access.md b/...liance_manager/set-fqdn-for-web-access.md → ...liance-manager/set-fqdn-for-web-access.md
diff --git a/...on/appliance_manager/set-up-https-cert.md → ...on/appliance-manager/set-up-https-cert.md b/...on/appliance_manager/set-up-https-cert.md → ...on/appliance-manager/set-up-https-cert.md
diff --git a/...g-up-backup-device42-appliance-manager.md → ...g-up-backup-device42-appliance-manager.md b/...g-up-backup-device42-appliance-manager.md → ...g-up-backup-device42-appliance-manager.md
@@ -69,7 +69,7 @@ If your Current System Time is incorrect, \["AWS Regions and Endpoints"\]you wil
 
 ### Important Note for Scheduled Back-Up's
 
-If you intend to use a back-up schedule for an auto-restore configuration to a stand-by appliance, as described in our ["Warm HA Configuration."](administration/appliance_manager/warm-ha-setup-failover-and-automated-backups.md)
+If you intend to use a back-up schedule for an auto-restore configuration to a stand-by appliance, as described in our ["Warm HA Configuration."](administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.md)
 
 It is critical that you select to include "Backup Meta Data" as an option for the Back-up Schedule.
 

diff --git a/...a-setup-failover-and-automated-backups.md → ...a-setup-failover-and-automated-backups.md b/...a-setup-failover-and-automated-backups.md → ...a-setup-failover-and-automated-backups.md
@@ -33,7 +33,7 @@ Without the meta data, restore and passphrase settings will not be in the back-u
 
 A back-up file without meta data can still be used for an on-demand “Restore”.
 
-You will be able to find additional details for [Backup Meta Data](administration/appliance_manager/setting-up-backup-device42-appliance-manager.md#backing-up-metadata) and [Scheduling the Backup.](administration/appliance_manager/setting-up-backup-device42-appliance-manager.md#scheduling-the-backup)
+You will be able to find additional details for [Backup Meta Data](administration/appliance-manager/setting-up-backup-device42-appliance-manager.md#backing-up-metadata) and [Scheduling the Backup.](administration/appliance-manager/setting-up-backup-device42-appliance-manager.md#scheduling-the-backup)
 
 ### Setting Appliance mode via API
 

diff --git a/docs/administration/data-reset-tool.md b/docs/administration/data-reset-tool.md
@@ -13,4 +13,4 @@ You can then run the script on any computer with Python 2.7+ installed.
 
 * * *
 
-**Note:** The Device42 reset script does not currently clear subnets from the application, they will need to manually be cleared. WARNING: THIS SCRIPT WILL CLEAR ALL DEVICES FROM DEVICE42 -- [Make a backup](appliance_manager/setting-up-backup-device42-appliance-manager.md) first if you're even a little bit unsure!
+**Note:** The Device42 reset script does not currently clear subnets from the application, they will need to manually be cleared. WARNING: THIS SCRIPT WILL CLEAR ALL DEVICES FROM DEVICE42 -- [Make a backup](appliance-manager/setting-up-backup-device42-appliance-manager.md) first if you're even a little bit unsure!
diff --git a/docs/administration/generating-csrs.md b/docs/administration/generating-csrs.md
@@ -29,7 +29,7 @@ To generate a CSR (Certificate Signing Request), open a terminal that has the _o
     $ openssl rsa -in server.key -out key_file
 ```
 
-Adding a new certificate is easy; See [add a new certificate via appliance manager instructions here](appliance_manager/set-up-https-cert.md).
+Adding a new certificate is easy; See [add a new certificate via appliance manager instructions here](appliance-manager/set-up-https-cert.md).
 
 ## Generating non-production CSRs
 

diff --git a/docs/apps/affinity_groups/_category_.yml → docs/apps/affinity-groups/_category_.yml b/docs/apps/affinity_groups/_category_.yml → docs/apps/affinity-groups/_category_.yml
diff --git a/.../apps/affinity_groups/appfocus-filters.md → .../apps/affinity-groups/appfocus-filters.md b/.../apps/affinity_groups/appfocus-filters.md → .../apps/affinity-groups/appfocus-filters.md
diff --git a/docs/apps/affinity_groups/index.md → docs/apps/affinity-groups/index.md b/docs/apps/affinity_groups/index.md → docs/apps/affinity-groups/index.md
diff --git a/...pps/application_components/_category_.yml → ...pps/application-components/_category_.yml b/...pps/application_components/_category_.yml → ...pps/application-components/_category_.yml
diff --git a/...onents/application-component-templates.md → ...onents/application-component-templates.md b/...onents/application-component-templates.md → ...onents/application-component-templates.md
@@ -5,7 +5,7 @@ sidebar_position: 1
 
 ## Introduction
 
-You can use Application Component Templates to create and define your own application components based on services discovered by Device42 [Hypervisor /\*nx/Windows](auto-discovery/windows-and-hyper-v-auto-discovery.md) autodiscovery jobs run against \*nix and Windows platforms. Device42 adds any application components created based on your templates to the [Application Components](apps/application_components/application-component-templates.md) list page.
+You can use Application Component Templates to create and define your own application components based on services discovered by Device42 [Hypervisor /\*nx/Windows](auto-discovery/windows-and-hyper-v-auto-discovery.md) autodiscovery jobs run against \*nix and Windows platforms. Device42 adds any application components created based on your templates to the [Application Components](apps/application-components/application-component-templates.md) list page.
 
 ## View Application Component Templates
 

diff --git a/docs/apps/business-applications/building-business-applications-in-device42.md b/docs/apps/business-applications/building-business-applications-in-device42.md
@@ -5,7 +5,7 @@ sidebar_position: 1
 
 ## Overview
 
-This is a technical guide that will walk you through a step-by-step process to building Business Applications within Device42.  [Once you have successfully performed discovery,](auto-discovery/auto-discovery.md) apply the methods outlined below to create Affinity Groups and then leverage these groups to facilitate the process of building your Business Applications.
+This is a technical guide that will walk you through a step-by-step process to building Business Applications within Device42.  [Once you have successfully performed discovery,](auto-discovery/index.md) apply the methods outlined below to create Affinity Groups and then leverage these groups to facilitate the process of building your Business Applications.
 
 ## Viewing Discovery Data
 
@@ -45,7 +45,7 @@ For highly active servers and environments, these visuals can be quite noisy mak
 
 ## Affinity Groups
 
-Affinity Groups are a result of a process that evaluates all the connections for a given device and constructs a more consumable view of its inter-dependencies.  Through a process of Pinning, Staring, and Hiding Services, noise is limited to just meaningful connections to better understand the impact or dependency of a particular device.  Please see: [affinity groups](apps/affinity_groups/index.md) to further understand this process.
+Affinity Groups are a result of a process that evaluates all the connections for a given device and constructs a more consumable view of its inter-dependencies.  Through a process of Pinning, Staring, and Hiding Services, noise is limited to just meaningful connections to better understand the impact or dependency of a particular device.  Please see: [affinity groups](apps/affinity-groups/index.md) to further understand this process.
 
 ### Enabling Affinity Groups
 

diff --git a/docs/apps/enterprise-application-dependency-mapping/adm-supported-applications.md b/docs/apps/enterprise-application-dependency-mapping/adm-supported-applications.md
@@ -9,7 +9,7 @@ Enterprise Application Dependency Mapping will discover **_all running services,
 
 The following is a list of applications that Enterprise Application Dependency Mapping can additionally create application components for.
 
-Additionally, for any application not on this list you can leverage the use of [Application Component Templates](apps/application_components/application-component-templates.md) to automate Application Component creation with custom logic that will supplement the discovery processes of Device42.
+Additionally, for any application not on this list you can leverage the use of [Application Component Templates](apps/application-components/application-component-templates.md) to automate Application Component creation with custom logic that will supplement the discovery processes of Device42.
 
 | Application | Services Discovered | Configuration Information Imported |
 | --- | --- | --- |

diff --git a/...ud_platforms_autodiscovery/_category_.yml → ...ud-platforms-autodiscovery/_category_.yml b/...ud_platforms_autodiscovery/_category_.yml → ...ud-platforms-autodiscovery/_category_.yml
diff --git a/...tforms_autodiscovery/aws-autodiscovery.md → ...tforms-autodiscovery/aws-autodiscovery.md b/...tforms_autodiscovery/aws-autodiscovery.md → ...tforms-autodiscovery/aws-autodiscovery.md
@@ -184,7 +184,7 @@ Device42 adds the new AWS Role to the roles list; it will also appear in the Ava
 
     2. We would need an account that uses just accountID and one that would be with the Require ExternalID option - Note no requirement for MFA option at this time
 
-    3. Policy to be added - use the example minimum policy needed for discovery from our docs site [here](auto-discovery/cloud_platforms_autodiscovery/index.md)
+    3. Policy to be added - use the example minimum policy needed for discovery from our docs site [here](auto-discovery/cloud-platforms-autodiscovery/index.md)
 
 2. From the Sub (or separate)-account
 

diff --git a/...orms_autodiscovery/azure-autodiscovery.md → ...orms-autodiscovery/azure-autodiscovery.md b/...orms_autodiscovery/azure-autodiscovery.md → ...orms-autodiscovery/azure-autodiscovery.md
@@ -25,7 +25,7 @@ Next, we will create a role with limited permissions that will be applied to thi
 
 Navigate to Access Control (IAM) >  Roles > Add > Add Custom Role. Give the custom role a name, an optional description, then select either Start from scratch or Start from JSON.
 
-1. If using the Start from scratch option, you will need to manually select each permission needed for this application to access the desired resources. The permissions needed are available in Device42 documentation [here](auto-discovery/cloud_platforms_autodiscovery/index.md). Select Add permissions, search for and select the desired permission, check the relevant box and choose Add. Repeat this for any desired permissions.
+1. If using the Start from scratch option, you will need to manually select each permission needed for this application to access the desired resources. The permissions needed are available in Device42 documentation [here](auto-discovery/cloud-platforms-autodiscovery/index.md). Select Add permissions, search for and select the desired permission, check the relevant box and choose Add. Repeat this for any desired permissions.
 2. If using the Start from JSON option, copy and paste the below JSON data, pulling in the necessary permissions from the list in Discovery section, and save it as a .json file. Upload this file on the Basics page when creating the role, and the permissions will be automatically defined.
 
 ```

diff --git a/...ry/google-cloud-platform-autodiscovery.md → ...ry/google-cloud-platform-autodiscovery.md b/...ry/google-cloud-platform-autodiscovery.md → ...ry/google-cloud-platform-autodiscovery.md
diff --git a/...ry/cloud_platforms_autodiscovery/index.md → ...ry/cloud-platforms-autodiscovery/index.md b/...ry/cloud_platforms_autodiscovery/index.md → ...ry/cloud-platforms-autodiscovery/index.md
diff --git a/...rms_autodiscovery/intune-autodiscovery.md → ...rms-autodiscovery/intune-autodiscovery.md b/...rms_autodiscovery/intune-autodiscovery.md → ...rms-autodiscovery/intune-autodiscovery.md
diff --git a/...autodiscovery/kubernetes-autodiscovery.md → ...autodiscovery/kubernetes-autodiscovery.md b/...autodiscovery/kubernetes-autodiscovery.md → ...autodiscovery/kubernetes-autodiscovery.md
@@ -9,7 +9,7 @@ sidebar_position: 6
 
 ### Kubernetes Discovery for AWS, Google Cloud, and MS Azure
 
-Kubernetes Discovery is available as an option for [Amazon AWS](auto-discovery/cloud_platforms_autodiscovery/index.md), [Google Cloud](auto-discovery/cloud_platforms_autodiscovery/index.md), and [Microsoft Azure](auto-discovery/cloud_platforms_autodiscovery/index.md) cloud autodiscovery jobs. Scroll down the Add Cloud Discovery page to select the _Kubernetes Discovery_ option.
+Kubernetes Discovery is available as an option for [Amazon AWS](auto-discovery/cloud-platforms-autodiscovery/index.md), [Google Cloud](auto-discovery/cloud-platforms-autodiscovery/index.md), and [Microsoft Azure](auto-discovery/cloud-platforms-autodiscovery/index.md) cloud autodiscovery jobs. Scroll down the Add Cloud Discovery page to select the _Kubernetes Discovery_ option.
 
 ![](/assets/images/discovery_cloud_platforms_autodiscovery_kubernetes-autodiscovery1.png)
 

diff --git a/...odiscovery/other-cloud-autodiscoveries.md → ...odiscovery/other-cloud-autodiscoveries.md b/...odiscovery/other-cloud-autodiscoveries.md → ...odiscovery/other-cloud-autodiscoveries.md
diff --git a/docs/auto-discovery/index.md b/docs/auto-discovery/index.md
@@ -41,7 +41,7 @@ HP & IBM Blade System (or Blade Center) chassis and blade details can be discove
 
 ## Cloud Platform Discovery
 
-Connect to Amazon AWS, Alibaba Cloud, Microsoft Azure, Digital Ocean, Google Cloud, Linode, and Openstack from the cloud discovery under _Discovery > Cloud_. Cloud discovery details can be found here: [Cloud Platforms Autodiscovery](./cloud_platforms_autodiscovery/index.md)
+Connect to Amazon AWS, Alibaba Cloud, Microsoft Azure, Digital Ocean, Google Cloud, Linode, and Openstack from the cloud discovery under _Discovery > Cloud_. Cloud discovery details can be found here: [Cloud Platforms Autodiscovery](./cloud-platforms-autodiscovery/index.md)
 
 ## DNS Autodiscovery
 

diff --git a/docs/auto-discovery/network-auto-discovery.md b/docs/auto-discovery/network-auto-discovery.md
@@ -13,7 +13,7 @@ SNMP, or Simple Network Management Protocol, is a protocol and a standard that i
 
 ### What can be autodiscovered using SNMP?
 
-Network devices can be discovered by Device42 using SNMP v1, v2c, or v3. If you're looking to do [Storage discovery](storage_arrays_autodiscovery/snmp-san-server-auto-discovery.md) via SNMP, you may want to visit the dedicated [SNMP SAN/Server Auto-Discovery](storage_arrays_autodiscovery/snmp-san-server-auto-discovery.md) page. SNMP discovery will pull in CDP/LLDP neighbors as long as SNMP credentials are the same across all neighbors. Should the credentials \*not\* be the same, you may instead add devices using different credentials separately, as their own discovery job.
+Network devices can be discovered by Device42 using SNMP v1, v2c, or v3. If you're looking to do [Storage discovery](storage-arrays-autodiscovery/snmp-san-server-auto-discovery.md) via SNMP, you may want to visit the dedicated [SNMP SAN/Server Auto-Discovery](storage-arrays-autodiscovery/snmp-san-server-auto-discovery.md) page. SNMP discovery will pull in CDP/LLDP neighbors as long as SNMP credentials are the same across all neighbors. Should the credentials \*not\* be the same, you may instead add devices using different credentials separately, as their own discovery job.
 
 ### Specific categories of data SNMP can discover
 

diff --git a/docs/auto-discovery/remote-collector-rc.md b/docs/auto-discovery/remote-collector-rc.md
@@ -102,4 +102,4 @@ Device42 Remote Collectors (RCs) are updated automatically as long as they are c
 
 ## Migrating Existing Power Appliance Jobs to a Remote Collector (RC)
 
-Migrating jobs that were created for the original standalone power appliance is possible with existing tools. Simply follow the [existing power job migration guide here](../infrastructure-management/power_and_environmental_monitoring/power-rc-setup-job-migration.md) to migrate jobs to the new RC of your choice.
+Migrating jobs that were created for the original standalone power appliance is possible with existing tools. Simply follow the [existing power job migration guide here](../infrastructure-management/power-and-environmental-monitoring/power-rc-setup-job-migration.md) to migrate jobs to the new RC of your choice.
diff --git a/...orage_arrays_autodiscovery/_category_.yml → ...orage-arrays-autodiscovery/_category_.yml b/...orage_arrays_autodiscovery/_category_.yml → ...orage-arrays-autodiscovery/_category_.yml
diff --git a/...covery/all-other-storage-autodiscovery.md → ...covery/all-other-storage-autodiscovery.md b/...covery/all-other-storage-autodiscovery.md → ...covery/all-other-storage-autodiscovery.md
diff --git a/...s_autodiscovery/dell-emc-autodiscovery.md → ...s-autodiscovery/dell-emc-autodiscovery.md b/...s_autodiscovery/dell-emc-autodiscovery.md → ...s-autodiscovery/dell-emc-autodiscovery.md
diff --git a/..._arrays_autodiscovery/hp-autodiscovery.md → ...-arrays-autodiscovery/hp-autodiscovery.md b/..._arrays_autodiscovery/hp-autodiscovery.md → ...-arrays-autodiscovery/hp-autodiscovery.md
diff --git a/...arrays_autodiscovery/ibm-autodiscovery.md → ...arrays-autodiscovery/ibm-autodiscovery.md b/...arrays_autodiscovery/ibm-autodiscovery.md → ...arrays-autodiscovery/ibm-autodiscovery.md
diff --git a/...ery/storage_arrays_autodiscovery/index.md → ...ery/storage-arrays-autodiscovery/index.md b/...ery/storage_arrays_autodiscovery/index.md → ...ery/storage-arrays-autodiscovery/index.md
@@ -17,7 +17,7 @@ Use the links below for additional information about access protocols and minimu
 
 ### Dell/EMC Arrays
 
-[See Dell/EMC Autodiscovery](auto-discovery/storage_arrays_autodiscovery/dell-emc-autodiscovery.md) for more information about the following storage arrays:
+[See Dell/EMC Autodiscovery](auto-discovery/storage-arrays-autodiscovery/dell-emc-autodiscovery.md) for more information about the following storage arrays:
 
 - Dell Compellent
 - VNX or VMAX using EMC SMIS Providor
@@ -28,21 +28,21 @@ Use the links below for additional information about access protocols and minimu
 
 ### HP Arrays
 
-[See HP Autodiscovery](auto-discovery/storage_arrays_autodiscovery/hp-autodiscovery.md) for more information about the following storage arrays:
+[See HP Autodiscovery](auto-discovery/storage-arrays-autodiscovery/hp-autodiscovery.md) for more information about the following storage arrays:
 
 - HP Nimble
 - HPE StoreEasy
 - HP 3PAR
 
 ### IBM Arrays
 
-[See IBM Autodiscovery](auto-discovery/storage_arrays_autodiscovery/ibm-autodiscovery.md) for more information about the following storage array:
+[See IBM Autodiscovery](auto-discovery/storage-arrays-autodiscovery/ibm-autodiscovery.md) for more information about the following storage array:
 
 - IBM V7000/Storwize
 
 ### All Other Storage Arrays
 
-[See All Other Storage Autodiscovery](auto-discovery/storage_arrays_autodiscovery/all-other-storage-autodiscovery.md) for more information about the following storage arrays:
+[See All Other Storage Autodiscovery](auto-discovery/storage-arrays-autodiscovery/all-other-storage-autodiscovery.md) for more information about the following storage arrays:
 
 - Infinidat
 - Netapp Filers

diff --git a/...scovery/snmp-san-server-auto-discovery.md → ...scovery/snmp-san-server-auto-discovery.md b/...scovery/snmp-san-server-auto-discovery.md → ...scovery/snmp-san-server-auto-discovery.md
diff --git a/...ge_arrays_autodiscovery/storage-arrays.md → ...ge-arrays-autodiscovery/storage-arrays.md b/...ge_arrays_autodiscovery/storage-arrays.md → ...ge-arrays-autodiscovery/storage-arrays.md
diff --git a/docs/auto-discovery/vendors-supported-in-snmp-auto-discovery.md b/docs/auto-discovery/vendors-supported-in-snmp-auto-discovery.md
@@ -5,7 +5,7 @@ sidebar_position: 35
 
 ## Have a device you'd like added to SNMP discovery?
 
-Device42 is open to supporting as many vendors as possible for SNMP-based discovery. Should you happen to run across a device that isn't being discovered properly, or if you have hardware you'd like to see supported -- Simply go ahead and [generate an SNMPwalk of the device](administration/appliance_manager/collecting-snmpwalk-output-for-troubleshooting.md) in question.  Within the Appliance Manager, go to Application>Generate SNMP Template.
+Device42 is open to supporting as many vendors as possible for SNMP-based discovery. Should you happen to run across a device that isn't being discovered properly, or if you have hardware you'd like to see supported -- Simply go ahead and [generate an SNMPwalk of the device](administration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.md) in question.  Within the Appliance Manager, go to Application>Generate SNMP Template.
 
 Fill out the form and attach your MIB Files. Once this processes, select the standard data you're looking to have added. After you've completed this form, it will be routed to our engineers to inclusion!
 

diff --git a/docs/getstarted/installation/installation-amazon-web-services.md b/docs/getstarted/installation/installation-amazon-web-services.md
@@ -115,7 +115,7 @@ The following video demonstrates updating your Device42 instance: how-to-videos/
 
 Device42’s backup facilities are accessible through the appliance manager. Backups can be executed immediately, and users have the ability to download a backup file immediately or on a schedule leveraging automatic saving to an SFTP, NFS, or AWS S3 destination.
 
-For more information on backups / restores, see our documentation: [administration/appliance_manager/setting-up-backup-device42-appliance-manager.md](administration/appliance_manager/setting-up-backup-device42-appliance-manager.md).
+For more information on backups / restores, see our documentation: [administration/appliance-manager/setting-up-backup-device42-appliance-manager.md](administration/appliance-manager/setting-up-backup-device42-appliance-manager.md).
 
 ### Monitoring / Health Checking Device42 on AWS
 
@@ -129,7 +129,7 @@ The above health-check will monitor the following:
 
 ### Configuring High Availability (HA) of Device42 on AWS
 
-If a High Availability (HA) deployment of Device42 is desired or required for a Device42 instance running on AWS, Device42 offers a supported "WarmHA" solution. To configure your deployment to run WarmHA, follow the instructions that can be found on the [Device42 WarmHA Documentation page - administration/appliance_manager/warm-ha-setup-failover-and-automated-backups.md](administration/appliance_manager/warm-ha-setup-failover-and-automated-backups.md). The linked page contains instructions on setting up WarmHA, failover, and if desired, configuring automatic backups.
+If a High Availability (HA) deployment of Device42 is desired or required for a Device42 instance running on AWS, Device42 offers a supported "WarmHA" solution. To configure your deployment to run WarmHA, follow the instructions that can be found on the [Device42 WarmHA Documentation page - administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.md](administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.md). The linked page contains instructions on setting up WarmHA, failover, and if desired, configuring automatic backups.
 
 An example configuration that leverages Nagios to automatically fail-over the instance in case of a failure is also described.