auto discovery

docs/auto-discovery/cloud_platforms_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](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
 

docs/auto-discovery/cloud_platforms_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.
 
 ```

docs/auto-discovery/cloud_platforms_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)
 

docs/infrastructure-management/ipam/ip-addresses.md

@@ -31,7 +31,7 @@ Click on an IP address to view its page.
 
 The view IP page shows the details for an IP and you can see the history of changes for that IP from the _History (Audit Logs)_ button (similar to all other view pages in the application). If you have appropriate permissions, you will see the _Edit_ button to edit. All DNS records that use this IP are shown in the view page as well.
 
-**Note**: Entries in the _Configuration Resource_ and _Configuration Resource Item_ fields make sense only in the context of a Kubernetes cloud discovery job ([cloud platforms autodiscovery](docs/discovery/cloud_platforms_autodiscovery/index.md)) and are filled in automatically. These field should not be populated for a regular IP address.
+**Note**: Entries in the _Configuration Resource_ and _Configuration Resource Item_ fields make sense only in the context of a Kubernetes cloud discovery job ([cloud platforms autodiscovery](auto-discovery/cloud_platforms_autodiscovery/index.md)) and are filled in automatically. These field should not be populated for a regular IP address.
 
 In the example above, the _Configuration Resource_ link will take you to the K8s cluster that is currently holding that IP, and _Configuation Resource Item_ contains the name and type of resource. In this case, the name is **Tiller-….jkfpl** and the resource type is a **p****od**.