Merge branch 'main' into 19.07.05

Author: sixhobbits

docs/apps/business-services/building-business-services-in-device42.mdx

@@ -116,7 +116,7 @@ Applications Groups are enabled by default in Device42, but you can disable the
     />
 
 
-### (Legacy) Pinning, Starring, and Hiding Services
+### For versions prior to 19.05: Pinning, Starring, and Hiding Services
 
 Now that we have enabled Application Groups, we must identify which services we want to Pin, Star, and Hide to continue to build out our Application Groups.  
 
@@ -172,7 +172,7 @@ Hovering over the timeline above the view will allow you to identify changes to
 
 ![](/assets/images/WEB-519_bus-apps-13-Affinity-Group-Chart-Timeline.png)
 
-### (Legacy) Refactoring Application Groups
+### For versions prior to 19.05: Refactoring Application Groups
 
 - There are times when choosing a different query to generate your Application Groups may be better suited for your environment. Navigate to **Tools > Integrations > Saved DOQL Queries**.
 

docs/auto-discovery/linux-unix-server-auto-discovery.mdx

@@ -179,11 +179,11 @@ Specify the timeout range between 10 to 600 seconds in the **Timeout** field to
     }}
 />
 
-When discovery switches between *nix users, the triggered banner text messages may disrupt database discovery and Application Component creation, resulting in discovery errors or incomplete data collection. 
+If you experience unexplainable issues during discovery that you suspect are due to banner text interfering with parsing, enable the **Check for Banner** option for discovery to detect and remove banner messages. The **Check for Banner** option is also available via API.
 
-To ensure full data collection when switching users, enable the **Check for Banner** option for discovery to detect and remove banner messages.
+When discovery switches between *nix users, the triggered banner text messages may disrupt database discovery and Application Component creation, resulting in discovery errors or incomplete data collection. 
 
-The **Check for Banner** option is also available via API.
+Note that banner text interference can't be directly determined from Device42. You require a power user with system access to the target machine to detect interference by switching users. Device42 support may advise you to select the banner option if they suspect banner text interference.  
 
 <ThemedImage
     alt="Check for Banner option"

docs/getstarted/discovery-hub.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Discovery Hub: scoping and onboarding"
+title: "Discovery Hub: Scoping and Onboarding"
 sidebar_position: 3.5
 ---
 
@@ -31,7 +31,7 @@ Log in to the Device42 UI and navigate to **Discovery > Discovery Hub**.
 
 To set up a Discovery Hub scan, name the scan and select the [Remote Collector](getstarted/installation/remote-collector-rc-installation.mdx) to use. You need to know the IPs, IP ranges, or CIDR blocks for your target environment.
 
-Enter the IP information in the box highlighted in the image below and click on the **+** button. You can enter as many targets as you like but the more targets included, the longer the scan will likely take. 
+Enter the IP information in the box highlighted in the image below and click on the **up arrow** button. You can enter as many targets as you like, but the more targets you include, the longer the scan will likely take. 
 
 <ThemedImage
   alt="Discovery Hub menu"
@@ -42,7 +42,7 @@ Enter the IP information in the box highlighted in the image below and click on
 />
 <br/><br/>
 
-After you have entered the information, click the bright green **Start** button. 
+After you have entered the IP address, named the scan, and selected at least one RC, click the green **Start** button. 
 
 The scan will start immediately. You'll see the green start notification, a percentage ticker showing your completion status, and information on the six categories of assets: **Windows**, **Nix**, **Network Devices**, **Hypervisors**, **Other/Unknown**, and **Unreachable**.
 
@@ -104,8 +104,8 @@ The scans you have created will be displayed in the left-hand column. Once start
 <ThemedImage
   alt="Scan results with settings button"
   sources={{
-    light: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-outcome-light.png'),
-    dark: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-outcome-dark.png'),
+    light: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-settings-button-light.png'),
+    dark: useBaseUrl('/assets/images/discovery-hub-onboarding/scan-settings-button-dark.png'),
   }}
 />
 <br/><br/>
@@ -162,7 +162,9 @@ The **One-time discovery** and **Continuous discovery** options are recommended
     light: useBaseUrl('/assets/images/discovery-hub-onboarding/discovery-job-window-cidr-light.png'),
     dark: useBaseUrl('/assets/images/discovery-hub-onboarding/discovery-job-window-cidr-dark.png'),
   }}
+  style={{ width: '70%' }} 
 />
+
 <br/><br/>
 
 When the job is created successfully, you will see the screen below. You can close the window and go back to your scans or click the link to be taken to the job page to edit the job settings.
@@ -176,9 +178,7 @@ When the job is created successfully, you will see the screen below. You can clo
 />
 <br/><br/>
 
-From the **Settings** tab of completed Discovery Hub scans, you can see the linked jobs that were created based on those results. 
-
-Click on the **+ Add schedule button** to schedule the scan.
+From the **Settings** tab of completed Discovery Hub scans, you can see the linked jobs that were created based on those results. Click on the **+ Add schedule button** to schedule the scan.
 
 <ThemedImage
   alt="Network scan settings"

docs/getstarted/faqs/index.mdx

@@ -18,12 +18,7 @@ With a default configuration, visit `https://IP_or_fqdn_for_device42_vm` in your
 
 ## Which Browser Should I Use?
 
-Device42 recommends using the web browsers (or more recent versions) listed below.
-
-- Chrome — 88.0.4324.150
-- Edge — 88.0.705.63
-- Firefox — 72.0.1
-- Safari — 13.1.2 (13609.3.5.1.5)
+Device42 recommends using the latest version of Chrome, Firefox, Edge, or Safari.
 
 ## How Do I Get My Current Data Into Device42?
 
@@ -37,7 +32,7 @@ You can use any of the following tools to import your data to Device42:
 
 - [**Microsoft Excel / CSV (spreadsheet) import**](integration/imports/index.mdx): The **Tools > Imports/Exports (xls)** page outlines your options for importing MS Excel spreadsheets to Device42 and provides sample Excel sheets to help you format your existing spreadsheets so that uploading your existing data is as easy as possible.
 - [**Device42 generic import tool**](https://www.device42.com/blog/2018/06/19/new-features-added-to-the-generic-import-tool/): You can use the Device42 generic import tool to add and map fields for existing data from most spreadsheet formats. Learn more about formatting best practices in the Device42 walkthrough for manually [Importing Data From Existing Spreadsheets](getstarted/importing-data-from-existing-spreadsheets.mdx).
-- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as single source of truth for systems such as provisioning and monitoring.
+- [**RESTful APIs**](https://api.device42.com): These enable you to programatically automate your network documentation and leverage your asset data for scripts and automation. Simply add RESTful APIs to your regular workflow to leverage Device42 as a single source of truth for systems such as provisioning and monitoring.
 - **Device42 web UI**: You can use the Device42 web interface to import your data.
 - **Templates/bulk operations**: Certain object types are easier to add using templates or models. For example, it is easier to use [PDU models](infrastructure-management/power-units/defining-pdu-models.mdx) to create PDUs, [switch port templates](infrastructure-management/ipam/switch-templates.mdx) to create switches and ports, and [patch panel models](infrastructure-management/power-units/defining-pdu-models.mdx) to create patch panel ports and bulk backport connectivity for patch panels.
 
@@ -65,7 +60,7 @@ Current releases of Device42 support **all** discovery jobs, including WMI and P
 
 :::note
 RCs will only automatically update when an RC update coincides with an MA update.
-::
+:::
 
 ## How Do I Migrate Existing Power Appliance Jobs to a Remote Collector?
 
@@ -109,7 +104,7 @@ Data can be exported in Excel or CSV format by downloading current data from the
 
 ## How Do I Back Up My Data?
 
-Log in to the Device42 appliance manager at `https://your\_device42\_ip\_or\_FQDN:4242/` using the following default credentials:
+Log in to the Device42 appliance manager at `https://your_device42_ip_or_FQDN:4242/` using the following default credentials:
 
 - Username:`d42admin`
 - Password: `default`

docs/getstarted/getting-started-with-auto-discovery.mdx

@@ -6,27 +6,27 @@ sidebar_position: 2
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-The following how-to runs down quickly enumerating network objects with Device42 Autodiscovery.
+The following guide briefly walks you through creating various network objects with Device42 Autodiscovery.
 
 ## Getting Started with Device42 Videos
 
-**If you're new to Device42**, begin with our [**getting started videos**](https://www.youtube.com/playlist?list=PLJ9je_qSNumJ-rMzIXUufY-XsbrwWfeCR). In under 5 minutes, you'll learn how to set up your Remote Collector (RC), connect a Windows Discovery Service (WDS) instance to it, and run your first discovery job. Watch them now and you'll be an expert in no time!
+If you're new to Device42, begin with our [**Getting Started videos**](https://www.youtube.com/playlist?list=PLJ9je_qSNumJ-rMzIXUufY-XsbrwWfeCR). In under five minutes, you'll learn how to set up your Remote Collector (RC), connect a Windows Discovery Service (WDS) instance to it, and run your first discovery job. [Watch them now](https://www.youtube.com/watch?v=ClkvR9zLQUU&t=0s&list=PLJ9je_qSNumJ-rMzIXUufY-XsbrwWfeCR&index=2) and you'll be an expert in no time!
 
-Ready to learn more? If you prefer videos, visit our [Device42 "How-To" playlist on YouTube](https://www.youtube.com/playlist?list=PLJ9je_qSNumJ4HuNVS75wzRgBRrtCh6_q) or go to the [How-To video section](how-to-videos/index.mdx) in the docs. 
+Ready to learn more? If you prefer videos, visit the [Device42 **How To** playlist on YouTube](https://www.youtube.com/playlist?list=PLJ9je_qSNumJ4HuNVS75wzRgBRrtCh6_q) or the [How-To Videos](how-to-videos/index.mdx) in the documentation. 
 
-If you can't find the answer you're looking for, please email support@device42 and let us know. There's a good chance other people are wondering the same thing, and we'll be happy to create a new video.
+If you can't find the answer you're looking for, please email [support@device42](mailto:support@device42) and let us know. There's a good chance other people are wondering the same thing, and we'll be happy to create a new video.
 
 ## Autodiscovery Account Notice
 
 :::caution
-Please do **not** set up an autodiscovery scan using critical production account credentials. Please create a separate, dedicated account to use only for discovery.
+Please **do not** set up an autodiscovery scan using critical production account credentials. Instead, create a separate, dedicated account to use only for discovery.
 :::
 
-Depending on permissions granted and your configured password policies, account lock-out could result in an otherwise completely avoidable outage. You, the customer, are responsible for any such behavior that might result.
+Depending on the permissions granted and your configured password policies, account lockout could result in an otherwise completely avoidable outage. You, the customer, are responsible for any such behavior that might result.
 
 ## Creating Subnets
 
-Go to **Resources > Networks > All Subnets** and click **Create** on the top right corner.
+Go to **Resources > Networks > All Subnets** and click **Create** in the top-right corner.
 
 <ThemedImage
 alt="View or edit existing subnets"
@@ -36,7 +36,7 @@ sources={{
 }}
 />
 
-The required fields are **Network**, **Mask Bits**, and **Service Level**. The other fields are optional. If left empty, **Range Begin** and **Range End** are automatically calculated based on network and bits.
+The required fields are **Network**, **Mask Bits**, and **Service Level**. The other fields are optional. If left empty, **Range Begin** and **Range End** are automatically calculated based on the **Network** and **Mask Bits**.
 
 <ThemedImage
 alt="Create a new subnet"
@@ -46,24 +46,26 @@ sources={{
 }}
 />
 
-If subnets have been pre-defined, all discovered IP addresses will be placed in their respective subnets. Otherwise, the IPs will end up in an "undefined" subnet.
+If subnets have been predefined, all discovered IP addresses will be placed in their respective subnets. Otherwise, the IPs will end up in an **undefined** subnet.
 
-## Set Up Autodiscovery
+## Setting Up Autodiscovery
 
-### Set Up WDS (Windows Discovery Service)
+### Setting Up Windows Discovery Service (WDS)
 
 Now is a good time to set up a [Remote Collector](auto-discovery/remote-collector-rc.mdx), as RCs are dedicated to discovery and can handle larger network ranges than your Main Appliance (MA). 
 
-If you’ll be discovering any Microsoft Windows OS-based servers or guests, go ahead and set up an instance of WDS. Note that your WDS instance can be connected to either your Main Appliance OR to a Remote Collector. If you do have an RC set up, it’s recommended to connect to WDS rather than connecting it to your MA.
+If you’ll be discovering any Microsoft Windows OS-based servers or guests, go ahead and set up an instance of WDS. Note that your WDS instance can be connected to either your MA **or** to an RC. If you have an RC set up, we recommend connecting the instance to the RC instead of your MA.
 
-### Create Your First Discovery Job
+### Creating Your First Discovery Job
 
-If you're discovering any Microsoft- or Windows-based products, install the [WDS](installation/windows-discovery-service-installation.mdx) first.
+If you're discovering any Microsoft- or Windows-based products, first install the [WDS](installation/windows-discovery-service-installation.mdx).
 
-Start by discovering your network. Navigate to **Discovery > SNMP** and click **Create** to create a [SNMP/Network discovery job](auto-discovery/network-auto-discovery.mdx). This will build out a base for the rest of your network. Then move on to vServer discovery, followed by Windows/Linux servers, etc.
+Next, discover your network. Navigate to **Discovery > SNMP** and click **Create** to create a [SNMP/Network discovery job](auto-discovery/network-auto-discovery.mdx). This will build out a base for the rest of your network.
+
+Then, move on to vServer discovery, followed by Windows/Linux server discovery, and more.
 
 :::info
-See [auto-discovery best practices](auto-discovery/autodisc-best-practices.mdx) for recommendations on the order in which to run initial discoveries. If you're familiar, jump right into [SNMP/Network discovery](auto-discovery/network-auto-discovery.mdx).
+See the [Autodiscovery Best Practices](auto-discovery/autodisc-best-practices.mdx) for recommendations on the order in which to run initial discoveries. If you're already familiar with these practices, jump right into [SNMP/Network discovery](auto-discovery/network-auto-discovery.mdx).
 :::
 
 <ThemedImage
@@ -74,32 +76,30 @@ sources={{
 }}
 />
 
-## The "unknown" Device Type 
-
-Any devices that are not virtual will come over as device type "unknown" initially. This is because the appliance has not been told whether the hardware belongs to the physical, blade, or other category.
+## The Unknown Device Type 
 
-The following device types have a hardware model. Each hardware model can be one of three types: regular, blade, or other.
+All non-virtual devices will initially be assigned the **unknown** device type during discovery. These devices have a hardware model. The appliance categorizes them as **unknown** because it has not yet been instructed which of the following types the hardware models belong to:
 
-- **Regular:** Represents physical devices
-- **Blade:** Represents blade devices
-- **Other:** Represents "other" devices like laptops, workstations, network printers, etc. that are not rack-mounted
+- **Regular:** Represents physical devices.
+- **Blade:** Represents blade devices.
+- **Other:** Represents "other" devices, like laptops, workstations, and network printers, that aren't rack-mounted.
 
-Once you change a hardware type, all the corresponding devices that refer to that hardware and are of the type "unknown" will automatically be categorized accordingly.
+Once you change a hardware type, all the corresponding devices that refer to that hardware and have been assigned the **unknown** type will automatically be categorized accordingly.
 
-The hardware bulk edit feature allows changing hardware properties in bulk for all undefined hardware types and it will automatically categorize all devices belonging to the category. See the [bulk edit YouTube videos](how-to-videos/add-and-bulk-edit-hardware-models-how-to.mdx) or [bulk edit documentation](infrastructure-management/devices/hardware-models-templates.mdx) for more information.
+The hardware bulk edit feature allows you to change hardware properties in bulk for all undefined hardware types. It automatically categorizes all devices belonging to a specific category. See the [Bulk Edit video](how-to-videos/add-and-bulk-edit-hardware-models-how-to.mdx) or [Bulk Edit documentation](infrastructure-management/devices/hardware-models-templates.mdx) for more information.
 
-Also, once a hardware type is defined, any newly imported or discovered devices will go into the right category.
+Once a hardware type has been defined, any newly imported or discovered devices will go into the correct category.
 
-## View Details of Discovered Items
+## Viewing the Details of Discovered Items
 
-To view the details of discovered items, navigate to that item's list page and select an item from the table. 
+To view the details of a discovered item type, navigate to that item type's list page and select an item from the table. 
 
-For example, go to **Resources > All Devices** and click on a device name to view device details. Depending on the device and information available, fields like **Hardware**, **Serial #**, **Total CPUs**, **RAM**, **OS**, and **IP Addresses** can be populated.
+For example, you can go to **Resources > All Devices** and click on a device name to view that device's details. Depending on the device and information available, fields like **Hardware**, **Serial #**, **Total CPUs**, **RAM**, **OS**, and **IP Addresses** may be populated.
 
 <ThemedImage
 alt="View device details"
 sources={{
     light: useBaseUrl('/assets/images/getting-started-with-auto-discovery/view-ci-details-19.06-light.png'),
     dark: useBaseUrl('/assets/images/getting-started-with-auto-discovery/view-ci-details-19.06-dark.png'),
 }}
-/>
+/>