device42 · Nadia-JSch · Apr 30, 2026 · Apr 30, 2026 · Apr 30, 2026 · Apr 30, 2026
diff --git a/...appliance-manager/adding-multiple-network-interface-cardsnic-to-device42-vm.mdx b/...appliance-manager/adding-multiple-network-interface-cardsnic-to-device42-vm.mdx
@@ -1,40 +1,40 @@
 ---
-title: "Adding multiple Network Interface Cards(NIC) to Device42 VM"
+title: "Adding Multiple Network Interface Cards (NICs) to a Device42 VM"
 sidebar_position: 1
 ---
 
-If you need to reach networks that can not be reached from the primary virtual machine network adapter (e.g. for autodiscovery), you can add additional network adapters to your virtual machine as outlined below.
+If you need to reach networks that aren't reachable from the primary virtual machine network adapter — for example, for discovery — you can add additional network adapters to the Device42 VM. This page covers how to add NICs, configure them, and verify the network configuration.
 
 ## Add Multiple NICs to the VM
 
 ![Add multiple NICs to the VM](/assets/images/wpid4810-vmware_nic.png)
 
-First, create an additional network adapter in the virtual machine settings. This is illustrated above for VMWare ESX.
+Create an additional network adapter in the virtual machine settings. The screenshot above shows the process for VMware ESX.
 
-Please note: Some virtualization platforms do not support adding NIC cards to a running instance. If this is the case for your virtualization platform, you will need to shutdown the Device42 instance first.
+:::note
+Some virtualization platforms do not support adding NICs to a running instance. If this is the case for your platform, shut down the Device42 instance before adding the NIC.
+:::
 
-You can add as many NICs as you want.
-
-One of the NICs will be the primary interface and will have default gateway and DNS defined. The other NICs will serve as the direct connection to specific network segments only.
+You can add as many NICs as needed. One NIC will serve as the primary interface with the default gateway and DNS defined. The other NICs will provide direct connections to specific network segments only.
 
 ## Configure the Assigned NICs
 
 ![Configuring the assigned NICs](/assets/images/wpid4809-vmware_console_ip_settings.png)
 
-From the Device42 virtual machine console, select option 1, then choose 'n' at the 'Use DHCP' prompt.
+From the Device42 VM console, select option 1, then choose `n` at the **Use DHCP** prompt.
 
-For each NIC, you will be prompted for the IP Address, Netmask, Gateway, and DNS Server (see below). As displayed above, the console will display the MAC address of the NIC being configured. Please make sure you are assigning the right IPs to each card. To make sure, please compare the displayed MAC address with the one shown in the virtual machine console.
+For each NIC, you will be prompted for the IP Address, Netmask, Gateway, and DNS Server. The console displays the MAC address of the NIC being configured — compare it with the MAC address shown in the virtual machine console to confirm you are assigning the correct IPs to each card.
 
 ### First Interface Vs. Other Interfaces
 
 ![First interface vs. other interfaces](/assets/images/wpid4807-first_vs_rest_interface.png)
 
-As shown in the image above, first add the Gateway and DNS info for the first NIC card. For the rest of the NIC cards, please add the IP Address and Netmask but please do NOT add the Gateway and DNS for any of the additional NIC cards. If you do, it will significantly slow down the boot up process while configuring the network interfaces.
+Add the Gateway and DNS information for the first NIC. For all additional NICs, add only the IP Address and Netmask — do not add the Gateway or DNS, as doing so will significantly slow the boot process while configuring the network interfaces.
 
-You can check your config after from the Device42 appliance manager as discussed in next step.
+You can verify your configuration from the Device42 Appliance Manager, as described in the next section.
 
-## Check Your Network Config
+## Check Your Network Configuration
 
 ![Checking your network config](/assets/images/wpid4626-usage-network-info.png)
 
-You can check your network config from the appliance manager under System > Usage/Network Info.
+In the Appliance Manager, navigate to **System > Usage/Network Info** to view your network configuration.
diff --git a/docs/administration/appliance-manager/api-limits.mdx b/docs/administration/appliance-manager/api-limits.mdx
@@ -3,8 +3,12 @@ title: "API Limits"
 sidebar_position: 2
 ---
 
-From the Appliance Manager, you can set a limit on the number of remote agents that can attempt to update at once. This option is intended for administrators who have hundreds of agents and need to prevent those agents from simultaneously attempting to update, possibly causing the Main Appliance to become overloaded.
+The API Limits setting in the Appliance Manager lets you cap the number of remote agents that can update concurrently. This page explains how the limit works and how to configure it.
 
-The default setting for the API limit is 16 concurrent agent updates. You can configure this number to best suit your needs, choosing a value between `8` and `128`.
+This setting is useful for administrators with hundreds of agents who need to prevent simultaneous updates from overloading the Main Appliance.
 
-![](/assets/images/api-limits/api-limits.png)
+## Configure the API Limit
+
+The default API limit is 16 concurrent agent updates. You can set this to any value between `8` and `128`.
+
+![API Limits setting in the Appliance Manager](/assets/images/api-limits/api-limits.png)
diff --git a/docs/administration/appliance-manager/changing-device42-appliance-hostname.mdx b/docs/administration/appliance-manager/changing-device42-appliance-hostname.mdx
@@ -3,32 +3,30 @@ title: "Changing Device42 Appliance Hostname"
 sidebar_position: 3
 ---
 
-You can change the Device42 Appliance hostname from the Appliance Manager or the VM console.
+You can change the Device42 Appliance hostname from either the Appliance Manager or the VM console. This page covers both methods.
 
-## Change Hostname in the Appliance Manager
+## Change the Hostname in the Appliance Manager
 
-[Log in to the Appliance Manager](device42-appliance-manager-login.mdx). 
+[Log in to the Appliance Manager](administration/appliance-manager/device42-appliance-manager-login.mdx).
 
-From the left panel, go to **System > Appliance Hostname**, enter the new hostname you would like to use, and click **Save**. You should see a success message.
+From the left panel, go to **System > Appliance Hostname**, enter the new hostname, and click **Save**. A success message will appear.
 
-![Change appliance name](/assets/images/changing-device42-appliance-hostname/appliance-hostname-change.png)
+![Change appliance hostname](/assets/images/changing-device42-appliance-hostname/appliance-hostname-change.png)
 
-You need to restart the Device42 application. Go to **Application > Restart Application** in the Appliance Manager. 
+Restart the Device42 application by navigating to **Application > Restart Application** in the Appliance Manager.
 
-![Change appliance name](/assets/images/changing-device42-appliance-hostname/restart-application.png)
+![Restart the application](/assets/images/changing-device42-appliance-hostname/restart-application.png)
 
-## Change Hostname in the VM Console
+## Change the Hostname in the VM Console
 
-Log in to the VM console. 
+Log in to the VM console and select **Server Settings** from the main menu.
 
-- Select **Server Settings** from the main menu. 
+![Server Settings option in the console](/assets/images/changing-device42-appliance-hostname/console-server-settings.png)
 
-    ![Change appliance name](/assets/images/changing-device42-appliance-hostname/console-server-settings.png)
+Enter the new hostname and select **Save**.
 
-- Enter the new hostname and select **Save**.
+![Enter new hostname](/assets/images/changing-device42-appliance-hostname/console-hostname.png)
 
-    ![Change appliance name](/assets/images/changing-device42-appliance-hostname/console-hostname.png)
+Select **Reboot Server** from the main menu and select **Reboot** to restart the server.
 
-- Select **Reboot Server** from the main menu and select **Reboot** to restart the server.
-
-    ![Change appliance name](/assets/images/changing-device42-appliance-hostname/console-reboot-server.png)
+![Reboot Server option in the console](/assets/images/changing-device42-appliance-hostname/console-reboot-server.png)
diff --git a/...nistration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx b/...nistration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx
@@ -3,46 +3,48 @@ title: "Collecting SNMP Walk Output"
 sidebar_position: 4
 ---
 
-You can collect SNMP walk output for a network device or PDU right from the GUI. Then, you can download the output and send it to us for further troubleshooting.
+You can collect SNMP walk output for a network device or PDU directly from the Appliance Manager and send the output to support for troubleshooting. This page covers the simple walk and MIB browser-based walk options, plus how to generate SNMP output from the terminal.
 
-From the Appliance Manager, go to **Application > Generate SNMP Output**. 
+From the Appliance Manager, go to **Application > Generate SNMP Output**.
 
 ## Simple SNMP Walk Output
 
-If this is not a new device, select the **No: Simple walk** option.
+If the target is not a new device, select **No: Simple walk**.
 
-Add your target switch or other SNMP target device info, click **Submit**, and please be patient as it might take a few minutes. Download the generated file and send it to support.
+Enter the target switch or SNMP device details, click **Submit**, and wait — generation may take a few minutes. Download the generated file and send it to support.
 
-    ![Collect SNMP walk Appliance Manager](/assets/images/collecting-snmpwalk-output-for-troubleshooting/simple-walk.png)
+![Simple SNMP walk in the Appliance Manager](/assets/images/collecting-snmpwalk-output-for-troubleshooting/simple-walk.png)
 
 ## MIB Browser-Based Walk
 
-For new devices, select **Yes: MIB browser based walk**. 
+For new devices, select **Yes: MIB browser based walk**.
 
-- Select your **RC** and enter the required fields: **FQDN or IP Address**, **Community String**, and MIB file upload.
+Select your **RC** and enter the required fields: **FQDN or IP Address**, **Community String**, and MIB file upload.
 
-    ![MIB file upload](/assets/images/collecting-snmpwalk-output-for-troubleshooting/browser-based-walk.png)
+![MIB file upload](/assets/images/collecting-snmpwalk-output-for-troubleshooting/browser-based-walk.png)
 
-- Select the data to generate for the new device and **Submit**.
+Select the data to generate for the new device and click **Submit**.
 
-    ![Generation options](/assets/images/collecting-snmpwalk-output-for-troubleshooting/generate-snmp.png)
+![SNMP generation options](/assets/images/collecting-snmpwalk-output-for-troubleshooting/generate-snmp.png)
 
-- Click **Download Archive File** and save the file to attach to an existing support ticket. If needed, [create a new ticket](https://support.device42.com/hc/en-us/requests/new) or [email support](mailto:support@device42.com).
+Click **Download Archive File** and save the file to attach to an existing support ticket. If needed, [create a new ticket](https://support.device42.com/hc/en-us/requests/new) or [email support](mailto:support@device42.com).
 
-    ![Download Archive file](/assets/images/collecting-snmpwalk-output-for-troubleshooting/download-archive-file.png)
+![Download Archive file](/assets/images/collecting-snmpwalk-output-for-troubleshooting/download-archive-file.png)
 
 ## Alternative SNMP Walk Generation
 
-If there is an issue, the network is not reachable, or you simply prefer using the terminal, you can instead run the following from any machine that has 'snmpwalk' installed for SNMP v2:
+If the network is not reachable from the Appliance Manager or you prefer the terminal, run the following from any machine with `snmpwalk` installed.
 
-```
+For SNMP v2:
+
+```bash
 snmpbulkwalk -Cc -ObentU -v2c -c COMMUNITY DEVICE > output_file_name
 snmpbulkwalk -ObentU -v 2c -c COMMUNITY DEVICE .1.3.6.1.4.1 >> output_file_name
 ```
 
-You can use the following for any system using SNMP v3:
+For SNMP v3:
 
-```
+```bash
 snmpbulkwalk -Cc -ObentU -v 3 -u user_name -l authNoPriv -a MD5 -A auth_pass DEVICE > output_file_name
 snmpbulkwalk -Cc -ObentU -v 3 -u user_name -l authNoPriv -a MD5 -A auth_pass DEVICE .1.3.6.1.4.1 >> output_file_name
-```
+```
diff --git a/docs/administration/appliance-manager/delete-history-logs.mdx b/docs/administration/appliance-manager/delete-history-logs.mdx
@@ -3,6 +3,6 @@ title: "Delete History Logs"
 sidebar_position: 5
 ---
 
-You can delete older history (audit logs) and trending data for performance gains and to clean up old data.
+You can delete older history (audit logs) and trending data from the Appliance Manager for performance gains and to clean up old data.
 
-![](/assets/images/media_1414488371177.png)
+![Delete history logs option in the Appliance Manager](/assets/images/media_1414488371177.png)
diff --git a/docs/administration/appliance-manager/device42-appliance-manager-login.mdx b/docs/administration/appliance-manager/device42-appliance-manager-login.mdx
@@ -6,14 +6,16 @@ sidebar_position: 6
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-Use the Device42 Appliance Manager to back up your data, update the Main Appliance, generate a log bundle [for uploading to the Device42 Support Portal](https://upload.device42.com/), restart the application, and configure **System** and **Global Settings**.
+The Device42 Appliance Manager is a web interface for backing up data, updating the Main Appliance, generating log bundles for the [Device42 Support Portal](https://upload.device42.com/), restarting the application, and configuring **System** and **Global Settings**. This page covers how to access the Appliance Manager, log in, and change your password.
 
 ## Access the Appliance Manager
 
-![Device42 Appliance Manager Home Screen v19](/assets/images/device42-appliance-manager-login/ap-home-view.png)
+![Appliance Manager home screen](/assets/images/device42-appliance-manager-login/ap-home-view.png)
 
-- For HTTP, access the Appliance Manager using port 4242: `http://your-ip-address-or-FQDN:4242`
-- For HTTPS, use port 4343: `https://your-ip-address-or-FQDN:4343`
+Access the Appliance Manager at one of the following URLs:
+
+- HTTP on port 4242: `http://<your-ip-or-FQDN>:4242`
+- HTTPS on port 4343: `https://<your-ip-or-FQDN>:4343`
 
 Alternatively, go to your Main Appliance login page and click the **Appliance Manager** link.
 
@@ -27,7 +29,7 @@ Alternatively, go to your Main Appliance login page and click the **Appliance Ma
 
 ## Login Credentials
 
-The default username and password are `d42admin` and `default`. Please [change the password](#change-your-password) as soon as you log in.
+The default username and password are `d42admin` and `default`. [Change the password](#change-your-password) as soon as you log in.
 
 ![Appliance Manager login screen](/assets/images/device42-appliance-manager-login/ap-login-screen.png)
 
@@ -37,8 +39,8 @@ Click your username at the top of the left sidebar and select **Change password*
 
 ![Change Password screen in Appliance Manager](/assets/images/device42-appliance-manager-login/change-password.png)
 
-## AWS Login 
+## AWS Login
 
-For **marketplace** AWS installations, use `d42admin` as the username and your **AWS Instance ID** as the default password. See [the AWS installation instructions](https://docs.device42.com/getstarted/deploy-device42/installation-amazon-web-services/#accessing-the-d42-appliance-manager---aws-marketplace-installs) for more information.
+For **marketplace** AWS installations, use `d42admin` as the username and your **AWS Instance ID** as the default password. See the [AWS installation instructions](getstarted/deploy-device42/installation-guides/installation-amazon-web-services.mdx#accessing-the-d42-appliance-manager---aws-marketplace-installs) for details.
 
-If you **manually** installed AWS using a downloaded image, use the default Device42 username, `d42admin`, and password, `default`, to log in to the Appliance Manager.
+For **manual** AWS installations using a downloaded image, log in with the default Device42 username `d42admin` and password `default`.