Merge pull request #492 from ritza-co/fix-heading-hierarchy-2

1210: Fix heading hierarchies + 1212  Change headings to imperative title case (Week 4, 2026)

Author: sixhobbits

.gitignore

@@ -16,6 +16,8 @@
 .env.production.local
 *.swp
 .vscode/
+CLAUDE.md
+/scripts
 .claude
 
 npm-debug.log*

docs/administration/appliance-manager/adding-multiple-network-interface-cardsnic-to-device42-vm.mdx

@@ -5,7 +5,7 @@ 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.
 
-### Add multiple NICs to the VM
+## Add Multiple NICs to the VM
 
 ![Add multiple NICs to the VM](/assets/images/wpid4810-vmware_nic.png)
 
@@ -17,23 +17,23 @@ 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.
 
-### Configuring the assigned NICs
+## 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.
 
 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.
 
-### First interface vs. other interfaces
+### 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.
 
 You can check your config after from the Device42 appliance manager as discussed in next step.
 
-### Checking your network config
+## Check Your Network Config
 
 ![Checking your network config](/assets/images/wpid4626-usage-network-info.png)
 

docs/administration/appliance-manager/changing-device42-appliance-hostname.mdx

@@ -5,7 +5,7 @@ sidebar_position: 3
 
 You can change the Device42 Appliance hostname from the Appliance Manager or the VM console.
 
-### Change Hostname in the Appliance Manager
+## Change Hostname in the Appliance Manager
 
 [Log in to the Appliance Manager](device42-appliance-manager-login.mdx). 
 
@@ -17,7 +17,7 @@ You need to restart the Device42 application. Go to **Application > Restart Appl
 
 ![Change appliance name](/assets/images/changing-device42-appliance-hostname/restart-application.png)
 
-### Change Hostname in the VM Console
+## Change Hostname in the VM Console
 
 Log in to the VM console. 
 

docs/administration/appliance-manager/collecting-snmpwalk-output-for-troubleshooting.mdx

@@ -7,15 +7,15 @@ You can collect SNMP walk output for a network device or PDU right from the GUI.
 
 From the Appliance Manager, go to **Application > Generate SNMP Output**. 
 
-### Simple SNMP Walk Output
+## Simple SNMP Walk Output
 
 If this is not a new device, select the **No: Simple walk** option.
 
 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.
 
     ![Collect SNMP walk Appliance Manager](/assets/images/collecting-snmpwalk-output-for-troubleshooting/simple-walk.png)
 
-### MIB Browser-Based Walk
+## MIB Browser-Based Walk
 
 For new devices, select **Yes: MIB browser based walk**. 
 

docs/administration/appliance-manager/device42-restore.mdx

@@ -10,13 +10,13 @@ Please take note of the following before you proceed with the restore process:
 - The restore process will delete all current data in the appliance. You can do a [test restore](#test-restore-options) first to verify that the restore works as you expect.
 :::
 
-### Active Directory Settings 
+## Active Directory Settings 
 
 Active Directory settings are crucial for logging back in. Otherwise, you can use local accounts to log back in after the restore and add Active Directory settings later.
 
 If you are doing a restore and have only Active Directory users (no Device42-only users), you will need to manually add the Active Directory settings prior to the restore.
 
-## Restoring the MA and RC Backup Files
+## Restore the MA and RC Backup Files
 
 From the [Appliance Manager](/administration/appliance-manager/device42-appliance-manager-login.mdx), navigate to **Backup/Restore > Restore**. 
 

docs/administration/appliance-manager/enable-or-disable-tls-versions-from-appliance-manager.mdx

@@ -3,16 +3,14 @@ title: "Enable or Disable TLS Versions from Appliance Manager"
 sidebar_position: 8
 ---
 
-# Disabling or Enabling TLS Versions From the Appliance Manager
-
 Device42 allows you to restrict TLS versions for Appliance Manager Access. The radio buttons shown below control this feature.
 
-:::note
-The Appliance Manager now defaults to **Enable TLS v1.2 only**. You can change the TLS settings in the Appliance Manager to **Enable TLS v.1.1 and v1.2** or **Enable All TLS**.
-:::
-
-- To apply TLS version restrictions, log in to the Device42 Appliance Manager. See [Device42 Appliance Manager Login](device42-appliance-manager-login.mdx) for more details about accessing and logging in to the Appliance Manager.
+To apply TLS version restrictions, log in to the Device42 Appliance Manager. See [Device42 Appliance Manager Login](device42-appliance-manager-login.mdx) for more details about accessing and logging in to the Appliance Manager.
 - From the main menu on the left side of the Appliance Manager, select **Global Settings** and then **TLS versions for Web Console** or **TLS versions for Appliance Manager**.
 - Select the appropriate radio button and click **Submit** to apply your changes.
 
     ![](/assets/images/enable-or-disable-tls-versions-from-appliance-manager/main-appliance-tls-options.png)
+
+:::note
+The Appliance Manager now defaults to **Enable TLS v1.2 only**. You can change the TLS settings in the Appliance Manager to **Enable TLS v.1.1 and v1.2** or **Enable All TLS**.
+:::

docs/administration/appliance-manager/generate-log-bundle.mdx

@@ -26,7 +26,7 @@ If you are experiencing issues with discovery, you can generate a log bundle and
 
 5. Upload the generated log file at [upload.device42.com](https://upload.device42.com/).
 
-### Remote Collector Log Bundle
+## Remote Collector Log Bundle
 
 If you were also using the Remote Collector (RC) for the job, please get and upload the RC logs using the [same upload link](https://upload.device42.com/) above. 
 

docs/administration/appliance-manager/set-up-https-cert.mdx

@@ -5,23 +5,23 @@ sidebar_position: 17
 
 You can add your own https cert and key in apache style cert files to use a secure web console for Device42 and the Remote Collectors. You can generate a self-signed certificate with a CA using OpenSSL or Microsoft certificate server and upload it here, or you can also have one issued from a trusted certificate authority.
 
-### Upload the cert and key files.
+## Upload the Cert and Key Files
 
 ![](/assets/images/WEB_815_1.jpg)
 
 Upload both files: cert and key. The software will validate the certs before applying them.
 
-### Adding the intermediate and the CA Root
+### Add the Intermediate and the CA Root
 
 You'll need to concatenate all the certificates, starting with the server certificate, and going deeper in the chain, running through all the intermediate certificates. This can be done with "cat chain.crt >> mysite.com.crt" on the command line. (or via copy-paste via a text editor)
 
-### Restart the Application
+## Restart the Application
 
 ![](/assets/images/WEB_815_2.jpg)
 
 You will need to restart the application to see the new cert.
 
-### Creating your own cert
+## Create Your Own Cert
 
 If you create your own certs, these can be uploaded via the Appliance Manager. Device42 is unable to assist in the creation and signing of certificates, please use a CA like Thawte for creation and signing.
 

docs/administration/appliance-manager/update-device42.mdx

@@ -18,7 +18,7 @@ The URL option automates the process of downloading and uploading the upgrade pa
 
 In both cases, a green status message will appear instructing you to complete the upgrade from the VM console.
 
-### Apply the Update
+## Apply the Update
 
 From the VM console, enter option **(a) Apply Update**:
 

docs/administration/appliance-manager/warm-ha-setup-failover-and-automated-backups.mdx

@@ -3,9 +3,11 @@ title: "Warm HA Setup, Failover, and Automated Backups"
 sidebar_position: 19
 ---
 
+The Device42 Warm High Availability (HA) configuration allows you to put a second appliance on standby mode and do periodic restorations to the device for use as a failover. 
+
 ## Automate Restores to Back Up Your Main Appliance for Warm HA
 
-The Device42 Warm High Availability (HA) configuration allows you to put a second appliance on standby mode and do periodic restorations to the device for use as a failover. This process consists of two steps:
+This process consists of two steps:
 
 - Setting up the automated restores
 - Setting the backup appliance to production mode in the event of a device failure
@@ -50,7 +52,7 @@ A backup file without metadata can still be used for an on-demand **Restore**.
 
 Refer to the Device42 docs to find additional details about [backup metadata](administration/appliance-manager/setting-up-backup-device42-appliance-manager.mdx#backing-up-metadata) and [scheduling the backup](administration/appliance-manager/setting-up-backup-device42-appliance-manager.mdx#scheduling-the-backup).
 
-## Setting Appliance Mode via API
+## Set Appliance Mode via API
 
 With automated restores in place on your backup appliance, you're ready to set the backup appliance to production mode in the event of a device failure. You can send a POST call to `/api/1.0/appliancemode/` with the payload `appliance_mode=production` or `appliance_mode=standby` to set the appliance to production or standby mode. This is intended to be triggered from the monitoring software of your choice (see the example below). After switching, a simple update to the DNS settings to point your domain to the new production instance IP will facilitate continuous use of Device42 without downtime.