Merge pull request #26 from ritza-co/rename-folders

Rename folders
device42 · Aug 1, 2023 · a9284cb · a9284cb
2 parents 4f729e3 + 7d67dde
commit a9284cb
Show file tree

Hide file tree

Showing 342 changed files with 1,005 additions and 1,014 deletions.
diff --git a/docs/administration/active-directory-and-openldap-support.md b/docs/administration/active-directory-and-openldap-support.md
@@ -27,4 +27,4 @@ You are able to review the domain found for the user found prior to adding them,
 
 ## Configuring an Active Directory User Sync / Discovery Job
 
-You may now configure an AD Sync Job to pull AD users in bulk and/or keep them synced. Proceed to [the Active Directory Discovery Job docs page](discovery/active-directory-sync.md) to view the AD discovery process.
+You may now configure an AD Sync Job to pull AD users in bulk and/or keep them synced. Proceed to [the Active Directory Discovery Job docs page](auto-discovery/active-directory-sync.md) to view the AD discovery process.
diff --git a/docs/administration/add-an-active-directory-user-as-a-device42-administrator.md b/docs/administration/add-an-active-directory-user-as-a-device42-administrator.md
@@ -23,4 +23,4 @@ Go to **Tools > Settings > Active Directory Settings** and enter and save the se
 
 ## Configuring the Active Directory User Discovery/sync Job
 
-You may now configure an AD Sync Job to pull AD users in bulk and/or keep them synced. Proceed to [the Active Directory Discovery Job docs page](discovery/active-directory-sync.md) to view the AD discovery process.
+You may now configure an AD Sync Job to pull AD users in bulk and/or keep them synced. Proceed to [the Active Directory Discovery Job docs page](auto-discovery/active-directory-sync.md) to view the AD discovery process.
diff --git a/docs/administration/advanced-routing.md b/docs/administration/advanced-routing.md
@@ -5,7 +5,7 @@ sidebar_position: 2
 
 If you have complex/advanced routing needs for your Device42 appliance – you can now add (or delete) those to the system from the console menu.
 
-**Advanced Routing instructions are also available in [video form, here.](videos/add-a-new-route-to-device42.md)**
+**Advanced Routing instructions are also available in [video form, here.](how-to-videos/add-a-new-route-to-device42.md)**
 
 1. To configure advanced routing, choose option 15 from the Device42 Setup/Troubleshooting Menu (Log in to the Console of the Device42 VM to access this menu.): ![advanced-routing-option](/assets/images/advanced_routing.png)
 

diff --git a/docs/administration/auto-clean-feature.md b/docs/administration/auto-clean-feature.md
@@ -52,7 +52,7 @@ You can use the basic filters (+ button) to add or remove filters for the search
 
 ![](/assets/images/18.06.00_auto-clean-add-device-search-2-filters.png)
 
-You can also use the [Advanced Search](getting_started/advanced-search-feature.md) feature (binocular button) to build a search criteria.
+You can also use the [Advanced Search](getstarted/advanced-search-feature.md) feature (binocular button) to build a search criteria.
 
 ![](/assets/images/18.06.00_auto-clean-add-device-search-3-advanced-search.png)
 

diff --git a/docs/administration/passwords/password-reporting.md b/docs/administration/passwords/password-reporting.md
@@ -25,4 +25,4 @@ Password Reporting Options:
 - Last Password Change NOT in the last - 1, 2, 3, 6, or 12 months
 - Expiration date NOT in the last - 1, 2, 3, 6, or 12 months (not shown)
 
-See [Reports](docs/reporting/index.md) for more information about creating Device42 reports.
+See [Reports](docs/reports/index.md) for more information about creating Device42 reports.
diff --git a/.../role-based_access_control/_category_.yml → .../role-based-access-control/_category_.yml b/.../role-based_access_control/_category_.yml → .../role-based-access-control/_category_.yml
diff --git a/...trol/role-based-permissions-and-access.md → ...trol/role-based-permissions-and-access.md b/...trol/role-based-permissions-and-access.md → ...trol/role-based-permissions-and-access.md
diff --git a/docs/applications/_category_.yml → docs/apps/_category_.yml b/docs/applications/_category_.yml → docs/apps/_category_.yml
diff --git a/...plications/affinity_groups/_category_.yml → docs/apps/affinity_groups/_category_.yml b/...plications/affinity_groups/_category_.yml → docs/apps/affinity_groups/_category_.yml
diff --git a/...tions/affinity_groups/appfocus-filters.md → .../apps/affinity_groups/appfocus-filters.md b/...tions/affinity_groups/appfocus-filters.md → .../apps/affinity_groups/appfocus-filters.md
diff --git a/docs/applications/affinity_groups/index.md → docs/apps/affinity_groups/index.md b/docs/applications/affinity_groups/index.md → docs/apps/affinity_groups/index.md
diff --git a/...ons/application_components/_category_.yml → ...pps/application_components/_category_.yml b/...ons/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](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](applications/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
 
@@ -17,7 +17,7 @@ Device42 displays the Application Component Templates list page.  On this page,
 
 ![](/assets/images/Screen-Shot-2022-08-15-at-8.10.58-AM.png)
 
-**Note**: The Application Component Templates list page also includes an _Advanced Search_ option you can use to construct more specific searches. See the [Advanced Search Feature](getting_started/advanced-search-feature.md) documentation page for instructions.
+**Note**: The Application Component Templates list page also includes an _Advanced Search_ option you can use to construct more specific searches. See the [Advanced Search Feature](getstarted/advanced-search-feature.md) documentation page for instructions.
 
 ![](/assets/images/WEB-757_Pic4.png)
 

diff --git a/...ions/business_applications/_category_.yml → ...apps/business-applications/_category_.yml b/...ions/business_applications/_category_.yml → ...apps/business-applications/_category_.yml
diff --git a/...ding-business-applications-in-device42.md → ...ding-business-applications-in-device42.md b/...ding-business-applications-in-device42.md → ...ding-business-applications-in-device42.md
@@ -5,11 +5,11 @@ 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,](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/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.
 
 ## Viewing Discovery Data
 
-After you have performed successful discovery, all discovered Application Dependency data can be viewed under the Applications section in the Device42 main menu. The Application Components section is where discovered infrastructure Application Components are stored. See a complete list of Device42’s supported applications here: [applications/application_dependency_mapping/adm-supported-applications.md](applications/application_dependency_mapping/adm-supported-applications.md) .
+After you have performed successful discovery, all discovered Application Dependency data can be viewed under the Applications section in the Device42 main menu. The Application Components section is where discovered infrastructure Application Components are stored. See a complete list of Device42’s supported applications here: [ADM supported applications](apps/enterprise-application-dependency-mapping/adm-supported-applications.md) .
 
 ![](/assets/images/Web_732_1.png)
 
@@ -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](docs/applications/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/...ication_dependency_mapping/_category_.yml → ...ication-dependency-mapping/_category_.yml b/...ication_dependency_mapping/_category_.yml → ...ication-dependency-mapping/_category_.yml
diff --git a/...ncy_mapping/adm-supported-applications.md → ...ncy-mapping/adm-supported-applications.md b/...ncy_mapping/adm-supported-applications.md → ...ncy-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](applications/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/...g/cloud-application-dependency-mapping.md → ...g/cloud-application-dependency-mapping.md b/...g/cloud-application-dependency-mapping.md → ...g/cloud-application-dependency-mapping.md
diff --git a/...nfigure-application-dependency-mapping.md → ...nfigure-application-dependency-mapping.md b/...nfigure-application-dependency-mapping.md → ...nfigure-application-dependency-mapping.md
@@ -5,7 +5,7 @@ sidebar_position: 3
 
 ## Turning on Application Discovery
 
-To turn on Enterprise Application Mapping, simply check the "Discover Applications" checkbox while configuring your discovery job. If you are new to discovery, see [Getting Started with Auto-Discovery](getting_started/getting-started-with-auto-discovery.md) to get acquainted. If you would like to discover config files, they can also be imported into Device42; select the "Store Application Components Config Files" checkbox.
+To turn on Enterprise Application Mapping, simply check the "Discover Applications" checkbox while configuring your discovery job. If you are new to discovery, see [Getting Started with Auto-Discovery](getstarted/getting-started-with-auto-discovery.md) to get acquainted. If you would like to discover config files, they can also be imported into Device42; select the "Store Application Components Config Files" checkbox.
 
 When autodiscovery is run, Application Components will be created based on related services on a server. For instance, a server with Oracle Database running will have a component created that associates all Oracle Database services together on that machine. The Autodiscovery Application will also find the service-to-service connections so you could, for example, see that your Apache service on _Prod-Server1_ is directly dependent on the MySQL service running on _Prod-Database3_.
 
@@ -23,7 +23,7 @@ To see autodiscovered application dependencies, go to Apps>Application Component
 
 ![Application Component View](/assets/images/select_application_component_view.png)
 
-A full list of currently supported applications is available at [Application Dependency Mapping Supported Applications](applications/application_dependency_mapping/adm-supported-applications.md).
+A full list of currently supported applications is available at [Application Dependency Mapping Supported Applications](apps/enterprise-application-dependency-mapping/adm-supported-applications.md).
 
 When you view the details page for an application component, you will see the device it was discovered on as well as any other application components that it depends on. You'll also see any services that have been associated with the application component. From here, you can also edit the application to assign responsible and/or affected departments, describe what's impacted by downtime, and edit any custom fields.
 

diff --git a/docs/applications/index.md → docs/apps/index.md b/docs/applications/index.md → docs/apps/index.md
diff --git a/docs/applications/services/_category_.yml → docs/apps/services/_category_.yml b/docs/applications/services/_category_.yml → docs/apps/services/_category_.yml
diff --git a/...applications/services/ignored-services.md → docs/apps/services/ignored-services.md b/...applications/services/ignored-services.md → docs/apps/services/ignored-services.md
diff --git a/docs/applications/services/network-shares.md → docs/apps/services/network-shares.md b/docs/applications/services/network-shares.md → docs/apps/services/network-shares.md
diff --git a/.../applications/services/scheduled-tasks.md → docs/apps/services/scheduled-tasks.md b/.../applications/services/scheduled-tasks.md → docs/apps/services/scheduled-tasks.md
diff --git a/...ations/services/service-communications.md → docs/apps/services/service-communications.md b/...ations/services/service-communications.md → docs/apps/services/service-communications.md
diff --git a/...pplications/services/service-instances.md → docs/apps/services/service-instances.md b/...pplications/services/service-instances.md → docs/apps/services/service-instances.md
diff --git a/...ations/services/service-listener-ports.md → docs/apps/services/service-listener-ports.md b/...ations/services/service-listener-ports.md → docs/apps/services/service-listener-ports.md
diff --git a/docs/applications/services/services.md → docs/apps/services/services.md b/docs/applications/services/services.md → docs/apps/services/services.md
diff --git a/docs/discovery/_category_.yml → docs/auto-discovery/_category_.yml b/docs/discovery/_category_.yml → docs/auto-discovery/_category_.yml
diff --git a/docs/discovery/active-directory-sync.md → docs/auto-discovery/active-directory-sync.md b/docs/discovery/active-directory-sync.md → docs/auto-discovery/active-directory-sync.md
diff --git a/docs/discovery/agent-based-discovery.md → docs/auto-discovery/agent-based-discovery.md b/docs/discovery/agent-based-discovery.md → docs/auto-discovery/agent-based-discovery.md
diff --git a/...iscovery/agent-based-offline-discovery.md → ...iscovery/agent-based-offline-discovery.md b/...iscovery/agent-based-offline-discovery.md → ...iscovery/agent-based-offline-discovery.md
diff --git a/...ery/auto-discovery-system-requirements.md → ...ery/auto-discovery-system-requirements.md b/...ery/auto-discovery-system-requirements.md → ...ery/auto-discovery-system-requirements.md
@@ -16,8 +16,8 @@ The following are pre-requisites and other general requirements and guidelines f
 
 Detailed permission info:
 
-- Windows & WMI namespace: [Windows & HyperV Discovery](discovery/windows-and-hyper-v-auto-discovery.md) page
-- Linux / sudo usage info: [Linux & Unix Server Discovery](discovery/linux-unix-server-auto-discovery.md) page
+- Windows & WMI namespace: [Windows & HyperV Discovery](auto-discovery/windows-and-hyper-v-auto-discovery.md) page
+- Linux / sudo usage info: [Linux & Unix Server Discovery](auto-discovery/linux-unix-server-auto-discovery.md) page
 
 \*\*Contact [email protected] with any further questions regarding specific privilege level requirements for WMI Namespaces, and \*nix commands run with/without sudo.
 

diff --git a/docs/discovery/autodisc-best-practices.md → ...auto-discovery/autodisc-best-practices.md b/docs/discovery/autodisc-best-practices.md → ...auto-discovery/autodisc-best-practices.md
diff --git a/...discovery/blade-systems-auto-discovery.md → ...discovery/blade-systems-auto-discovery.md b/...discovery/blade-systems-auto-discovery.md → ...discovery/blade-systems-auto-discovery.md
diff --git a/docs/discovery/certificate-auto-discovery.md → ...o-discovery/certificate-auto-discovery.md b/docs/discovery/certificate-auto-discovery.md → ...o-discovery/certificate-auto-discovery.md
@@ -25,6 +25,6 @@ Choosing **"discover cipher suites" can result in a significant slowdown of SSL
 
 ## Certificate Discovery with Multi-tenancy Enabled - Warning
 
-**Note that certificate discovery can fail if [MultiTenancy](administration/role-based_access_control/role-based-permissions-and-access.md) is enabled** and the discovery job targets a VRF group whose subnet doesn't exist within Device42. If you encounter this behavior, simply create the subnet that you are discovering within Device42 (or run a network discovery first, as recommended by the [best practices guide](autodisc-best-practices.md)).
+**Note that certificate discovery can fail if [MultiTenancy](administration/role-based-access-control/role-based-permissions-and-access.md) is enabled** and the discovery job targets a VRF group whose subnet doesn't exist within Device42. If you encounter this behavior, simply create the subnet that you are discovering within Device42 (or run a network discovery first, as recommended by the [best practices guide](autodisc-best-practices.md)).
 
 A note on autodiscovery scheduling behavior: newly created jobs will not run on the first day they are created, to prevent an unintended large amount of jobs from running initially. If you would like to run a job after its initial creation, simply select the "Run Now" button next to the job after creation.
diff --git a/docs/discovery/cisco-ucs-auto-discovery.md → ...uto-discovery/cisco-ucs-auto-discovery.md b/docs/discovery/cisco-ucs-auto-discovery.md → ...uto-discovery/cisco-ucs-auto-discovery.md
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
@@ -160,7 +160,7 @@ Device42 includes an editor you can use to define or edit the AWS Roles displaye
 
 ![](/assets/images/discovery_cloud_platforms_autodiscovery_aws-autodiscovery2.png)
 
-- Device42 displays the AWS Roles list page. Use the _AWS Role_ drop-down to select a role to display or click _Advanced_ to construct more specific searches. See the [Advanced Search Feature](getting_started/advanced-search-feature.md) documentation page for instructions.
+- Device42 displays the AWS Roles list page. Use the _AWS Role_ drop-down to select a role to display or click _Advanced_ to construct more specific searches. See the [Advanced Search Feature](getstarted/advanced-search-feature.md) documentation page for instructions.
 
 ![](/assets/images/Image_9_Cloud_Disc_AWS_Roles_2.png)
 
@@ -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](docs/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](docs/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](docs/discovery/cloud_platforms_autodiscovery/index.md), [Google Cloud](docs/discovery/cloud_platforms_autodiscovery/index.md), and [Microsoft Azure](docs/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/discovery/d42-ping-sweep.md → docs/auto-discovery/d42-ping-sweep.md b/docs/discovery/d42-ping-sweep.md → docs/auto-discovery/d42-ping-sweep.md
diff --git a/...scovery/database_discovery/_category_.yml → ...scovery/database-discovery/_category_.yml b/...scovery/database_discovery/_category_.yml → ...scovery/database-discovery/_category_.yml
diff --git a/...ery/database_discovery/cloud-databases.md → ...ery/database-discovery/cloud-databases.md b/...ery/database_discovery/cloud-databases.md → ...ery/database-discovery/cloud-databases.md
@@ -19,7 +19,7 @@ Device42 displays the cloud databases list page. On this page, you can _Search
 
 You can also click _+More_ to filter by _Vendor Resource Type_, _Role_, _Instance Size_, _In Service, Service Level, and Tags_.
 
-**Note**: The cloud databases list page also includes an _Advanced Search_ option you can use to construct more specific searches. See the [Advanced Search Feature](getting_started/advanced-search-feature.md) documentation page for instructions.
+**Note**: The cloud databases list page also includes an _Advanced Search_ option you can use to construct more specific searches. See the [Advanced Search Feature](getstarted/advanced-search-feature.md) documentation page for instructions.
 
 Click on a cloud database _Name_ to see details about that database. You can use the links in the _Related Resources_ panel on the right to see details about that related resource.
 

diff --git a/...atabase_discovery/on-premise-databases.md → ...atabase-discovery/on-premise-databases.md b/...atabase_discovery/on-premise-databases.md → ...atabase-discovery/on-premise-databases.md
diff --git a/...containers-supported-in-auto-discovery.md → ...containers-supported-in-auto-discovery.md b/...containers-supported-in-auto-discovery.md → ...containers-supported-in-auto-discovery.md
@@ -4,12 +4,12 @@ sidebar_position: 30
 ---
 
 If you were looking for how-to instructions to get started with Hypervisor, Linux (\*nix), or Windows discovery, see either: 
-- the [Windows / Hyper-V Discovery](discovery/windows-and-hyper-v-auto-discovery.md) page 
-- or the [Linux / UNIX server auto-discovery](discovery/linux-unix-server-auto-discovery.md) page.
+- the [Windows / Hyper-V Discovery](auto-discovery/windows-and-hyper-v-auto-discovery.md) page 
+- or the [Linux / UNIX server auto-discovery](auto-discovery/linux-unix-server-auto-discovery.md) page.
 
 ## Supported Hypervisor / Container Platforms
 
-Device42 is constantly expanding its list of hypervisor and container platforms supported by autodiscovery. For instructions on how to configure and run these discovery jobs, please refer to [Hypervisor Autodiscovery](discovery/virtual-machine-auto-discovery.md). The list of supported platforms currently includes:
+Device42 is constantly expanding its list of hypervisor and container platforms supported by autodiscovery. For instructions on how to configure and run these discovery jobs, please refer to [Hypervisor Autodiscovery](auto-discovery/virtual-machine-auto-discovery.md). The list of supported platforms currently includes:
 
 ![](/assets/images/D42-25011_supported-hyperv-platforms.png)
 

diff --git a/docs/discovery/ibm-i-as400.md → docs/auto-discovery/ibm-i-as400.md b/docs/discovery/ibm-i-as400.md → docs/auto-discovery/ibm-i-as400.md