device42 · Nadia-JSch · Jun 23, 2026 · Jun 23, 2026 · Jun 23, 2026 · Jun 23, 2026
diff --git a/docs/administration/passwords/secrets-reporting.mdx b/docs/administration/passwords/secrets-reporting.mdx
@@ -67,7 +67,7 @@ Device42 displays your Secrets data in a grid view.
 
 - Enter a unique name for the report in order to **Save** it.
 
-### Export and Schedule the Report
+## Export and Schedule the Report
 
 Click **Export** and choose between the **Excel** or **TSV** (Tab-Separated Values) format. You can schedule the report to run at recurring intervals by first toggling the **Report Schedule** to reveal the scheduling options.
 

diff --git a/docs/apps/services/index.mdx b/docs/apps/services/index.mdx
@@ -23,7 +23,7 @@ Use the **All Services** list page to see which services are running across your
 
 For [Application Dependency Mapping (ADM)](/apps/index.mdx), reviewing **All Services** and [**Service Instances**](service-instances.mdx) of the Device42 Main Appliance is particularly useful.
 
-### All Services vs Service Instances
+## All Services Vs. Service Instances
 
 The All Services list page has records of the unique names of the discovered services and the number of **Service Instances** with that name. For example:
 

diff --git a/docs/auto-discovery/microsoft-dhcp-discovery.mdx b/docs/auto-discovery/microsoft-dhcp-discovery.mdx
@@ -38,7 +38,7 @@ If **Discover Using WinRM** is not enabled, pair a WDS with the selected Remote
   }}
 />
 
-### Additional Options
+## Additional Job Options
 
 You can set a schedule to run the job automatically, turn off the default **Create Device from DHCP lease information** option, and set a **Service Level**.
 

diff --git a/docs/auto-discovery/setup-dns-autodiscovery.mdx b/docs/auto-discovery/setup-dns-autodiscovery.mdx
@@ -50,7 +50,7 @@ Fill out the following fields:
 
 Save the discovery job and click **Run Now** to test it. If you see "Success!" in the **Last Status** box, the new zone, IPs, and related details will be available in Device42.
 
-### Run or Schedule the Job
+## Run or Schedule the Job
 
 When creating or editing the job, select **Add another Auto Discovery Schedule** to schedule the job.
 

diff --git a/docs/getstarted/deploy-device42/sizing-recommendations.mdx b/docs/getstarted/deploy-device42/sizing-recommendations.mdx
@@ -13,22 +13,22 @@ Sizing requirements depend on the size of your environment and the Device42 feat
 | Remote Collector(s) (virtual appliance) | **One RC per 1000 workloads:** <br/>- Two vCPU <br/>- 4GB RAM <br/>- 50GB vDisk |
 | Windows Discovery Service (.NET installer) | **One WDS per 1000 workloads:**  <br/> - Two vCPU <br/> - 8GB RAM <br/> - 50GB vDisk (minimum) |
 
-## Recommendations
+## Optimal Setup
 
-The following are general recommendations, but the optimal setup depends on your specific infrastructure. [Contact support](https://support.device42.com/hc/en-us) for more guidance.
+These are general recommendations. The optimal setup depends on your specific infrastructure. [Contact support](https://support.device42.com/hc/en-us) for guidance tailored to your environment.
 
-### RC for Large Workloads
+## RC for Large Workloads
 
 First, increase the CPU and RAM when adding more workloads (> 1000) to the Remote Collector. If the Remote Collector is still performing slowly, add more Remote Collectors.
 
-### Dedicated Resource Pool
+## Dedicated Resource Pool
 
 Depending on your environment, a dedicated resource pool for the virtual appliance may be necessary to ensure there is no resource contention.
 
-### Database Storage
+## Database Storage
 
 Device42 uses a database within the virtual appliance. Solid-state storage, or similar storage optimized for database operations is recommended.
 
-### WDS Installation
+## WDS Installation
 
 For Windows infrastructure, Device42 requires a WDS to be installed on one machine per discovery segment or Remote Collector.
diff --git a/docs/getstarted/deploy-device42/windows-service-installation.mdx b/docs/getstarted/deploy-device42/windows-service-installation.mdx
@@ -18,7 +18,7 @@ You will need three separate files to install the service.
 
 There are multiple ways to install and start the service. For your convenience, we have added a PowerShell script (option 1). Below that we include detailed steps for installing with `sc` if needed (option 2).
 
-### Option 1: Using the PowerShell Script
+## Option 1: Using the PowerShell Script
 
 - Download the combined zip file and extract it to your local file system.
 - Ensure that PowerShell remote execution is enabled (`Set-ExecutionPolicy RemoteSigned`).
@@ -34,7 +34,7 @@ There are multiple ways to install and start the service. For your convenience,
 
 - **Optional:** Revert the execution policy.
 
-### Option 2: Using `sc` Commands
+## Option 2: Using `sc` Commands
 
 - By default, the service wrapper looks for an agent named `d42winagent.exe` under `C:\Program Files\Device42` on the end machine. Check that you've saved the agent using the correct name and location.
 
@@ -98,15 +98,15 @@ On Windows, `sc create` and `sc start`  read from `%windir%/system32` by default
 If you don't have `C:` or don't want to use `C:\ProgramData\Device42`, you can place `d42config.json` in the `system32` directory.
 :::
 
-### Arguments for the Config Files
+## Arguments for the Config Files
 
 As shown in the example above, each argument should be enclosed in double quotes and separated by a comma.
 
-### Log Output
+## Log Output
 
 The `agent_local.log` file will be created under the current working directory.
 
-### Handling Errors
+## Handling Errors
 
 ![Windows service wrapper error](/assets/images/windows-service-wrapper-error.png)
 

diff --git a/docs/infrastructure-management/connectivity/creating-wall-jacks.mdx b/docs/infrastructure-management/connectivity/creating-wall-jacks.mdx
@@ -8,6 +8,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 One method for documenting the connection path from a patch panel to a wall jack to a switch and its devices is to create a **patch panel model** for the wall jack.
 
+## Create the Wall Jack Model and Asset
+
 Navigate to **Resources > Assets > Patch Panel Models** and create a model with the appropriate **Port Type** and desired **Number of ports** on the panel of the wall jack.
 
 <ThemedImage
@@ -21,12 +23,16 @@ Navigate to **Resources > Assets > Patch Panel Models** and create a model with
 
 Once you've created the model, create assets for the wall jacks via **Resources > All Assets > Create**. When creating the asset, select the type **Patch Panel**, then select the wall jack model as the patch panel model. Set the **Back connection** type to either **Patch Panel** or **Switch**, depending on whether it connects to the patch panel or the unmanaged switch you are documenting.
 
+## Create an Unmanaged Switch
+
 Next, create an unmanaged switch:
 
 - Navigate to **Tools > Templates & Bulk Operations > Switch Templates** and create a template that reflects your switches. Select a switch type and add a ports switch template with the desired ports prefix, type, and number of ports.
 
 - Once you've created the switch template, select the template and click the **Create/Edit** option under the **Ellipsis menu** in the top right corner of the template's details page. Here, you can add the desired amount of unmanaged switches needed.
 
+## Create the Connections
+
 Once you've created assets for the wall jacks and created switches from the template, you can start creating the connections:
 
 - Open the wall jack asset and go to its edit details page. The page includes a patch panel ports section with a line for each port on the wall jack panel, as defined by the patch panel model you created earlier.

diff --git a/...vity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx b/...vity/patch-panels/creating-patch-panels-from-scratch-in-device42-an-example.mdx
@@ -19,7 +19,7 @@ The end goal is:
 
 This provides devices with connectivity to switch ports.
 
-### Create Patch Panel Models
+## Create Patch Panel Models
 
 <ThemedImage
   alt="Creating Patch Panel Models"
@@ -35,7 +35,7 @@ Before adding the patch panel, create the model template. In this example, this
 - Enter the details for the model, including a name, port type, and number of ports.
 - **Save** the patch panel model.
 
-### Create Patch Panels
+## Create Patch Panels
 
 <ThemedImage
   alt="Creating Patch Panels - Step 1"
@@ -77,7 +77,7 @@ Repeat the same steps for `Panel B`, changing only the name to `Panel B` in Step
 
 You can also specify the building and storage room, and add tags and images of the front and back.
 
-### Add the Back Connections or Termination
+## Add the Back Connections or Termination
 
 <ThemedImage
   alt="Adding the Back Connections or Termination"
@@ -101,7 +101,7 @@ Now, `Panel A` and `Panel B` are connected to each other.
   }}
 />
 
-### Patch Switch Ports to Panel A
+## Patch Switch Ports to Panel A
 
 - Go to **Tools > Templates & Bulk Operations > Import/Export (xls)**.
 
@@ -145,7 +145,7 @@ You could add each switch port to each panel port manually, but the recommended
 
 Upon import, you can see the switch ports' connections on Panel A.
 
-### Patch Devices to Panel B
+## Patch Devices to Panel B
 
 ![wpid3704-patch_panel_device_excel.png](/assets/images/wpid3704-patch_panel_device_excel.png)
 
@@ -163,7 +163,7 @@ Once you've added the values to Excel and imported the sheet, `Panel B` will sho
   }}
 />
 
-### Patch Panel Layout
+## Patch Panel Layout
 
 <ThemedImage
   alt="Patch Panel Visual Layout"
@@ -175,7 +175,7 @@ Once you've added the values to Excel and imported the sheet, `Panel B` will sho
 
 In `Panel B`'s patch panel layout, hover over any port or device to see the full visual path for that port.
 
-### Switch Port Level Connectivity
+## Switch Port Level Connectivity
 
 <ThemedImage
   alt="Switch Port Level Connectivity"
@@ -187,7 +187,7 @@ In `Panel B`'s patch panel layout, hover over any port or device to see the full
 
 Patch panel connectivity is also visible from each switch port view.
 
-### Device Level Connectivity
+## Device Level Connectivity
 
 <ThemedImage
   alt="Device Level Connectivity"

diff --git a/docs/infrastructure-management/devices/device-lifecycle-tab.mdx b/docs/infrastructure-management/devices/device-lifecycle-tab.mdx
@@ -40,7 +40,7 @@ Some of the predefined **Events** have logic built in. For example, you cannot c
 
 To add logic to asset lifecycle **Events**, navigate to **Tools > Lifecycle Event Actions**.
 
-### Add a New Lifecycle Event
+## Add a New Lifecycle Event
 
 Define a custom lifecycle **Event** by clicking the **plus icon** near the **Events** dropdown and then clicking **Create** on the pop-up window.
 
@@ -72,7 +72,7 @@ The options are:
   - **Remove blade device from the host**
   - **No longer count OS or software on this device in licensing**
 
-### Asset QR/Barcode
+## Asset QR/Barcode
 
 Add a QR code or barcode to the device for inventory management.
 
@@ -89,7 +89,7 @@ Add a QR code or barcode to the device for inventory management.
 
 See [QR Asset Tags](/infrastructure-management/mobile-inventory/understanding-qr-and-bar-codes-in-device42.mdx) for more information.
 
-### Purchase/Support Info
+## Purchase/Support Info
 
 Enter purchase information for the device under **Purchase/Support Info**. You can add one-time purchases and record contracts related to the device.
 

diff --git a/docs/infrastructure-management/devices/what-if-scenarios.mdx b/docs/infrastructure-management/devices/what-if-scenarios.mdx
@@ -8,9 +8,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'
 
 What If scenarios help you plan the deployment or migration of devices into racks. You define the devices you need to place, select the target racks or rooms, and Device42 calculates where the devices fit based on available space. If you use the power monitoring add-on, the calculation also accounts for amps and power supplies.
 
-## Create a What If Scenario
-
-Navigate to **Tools > Templates and Bulk Operations > What If**.
+To create a What If scenario, navigate to **Tools > Templates and Bulk Operations > What If**.
 
 1. Enter the number of devices and their size, amps, and number of power supplies. To add devices of different sizes, click **Add** to create a new line.
 

diff --git a/docs/infrastructure-management/mobile-inventory/auto-assign-asset-numbers.mdx b/docs/infrastructure-management/mobile-inventory/auto-assign-asset-numbers.mdx
@@ -34,7 +34,7 @@ All the fields labeled with bolded text in the UI are required.
 
 **Last used:** Do not change this value except in the special case discussed. The system will display the last asset number used and use this value to determine the next value to be generated. That is, if the last asset number generated were `0156`, this field would automatically change to `0156`. Change this only if you want to change the value that the asset number counter automatically starts from.
 
-### Assign the Asset Number Profile 
+## Assign the Asset Number Profile 
 
 - If the **Asset #** field is empty for a device or asset, you can select an Asset Number Profile under the **Profile to auto assign asset #** field when editing an object. 
 
@@ -56,7 +56,7 @@ All the fields labeled with bolded text in the UI are required.
     }}
     />
 
-### Bulk Asset Number Assignment
+## Bulk Asset Number Assignment
 
 - From **Resources > All Devices** or **Resources > All Assets**, you can search and filter the listed objects, make your selection of objects using the checkboxes, and select **Assign asset # to selected items** from the **Actions** dropdown.
 

diff --git a/...ructure-management/power-and-environmental-monitoring/unit-display-settings.mdx b/...ructure-management/power-and-environmental-monitoring/unit-display-settings.mdx
@@ -8,8 +8,6 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
 
 You can customize how units are displayed in Device42's Power and Environmental Monitoring module. This applies to both **Power** units and **Temperature** units, and these settings are controlled separately.
 
-## Power Global Settings
-
 To access the options, navigate to the **Power** options in the **Global Settings** menu, under **Tools > Settings > Global Settings**.
 
 <ThemedImage
@@ -22,19 +20,19 @@ To access the options, navigate to the **Power** options in the **Global Setting
 
 The two categories that control unit display are the **Power Conversion Options** dropdown and the **Display temperature values as Centigrade** checkbox.
 
-### Power Unit Conversion Options
+## Power Unit Conversion Options
 
 The **Power Conversion Options** dropdown controls how power consumption values are displayed. The available options are:
 
 - **Do not convert:** Default. Displays power values exactly as returned via SNMP, without conversion.
 - **Convert Amps to Watts:** Converts and displays all power values in Watts.
 - **Convert Watts to Amps:** Converts and displays all power values in Amps.
 
-### Default Voltage
+## Default Voltage
 
 The **Default Voltage (integer required)** setting lets you specify the default voltage for Device42 to use in calculations, only if a value is not returned via SNMP.
 
-### Display Temperature Values as Centigrade
+## Display Temperature Values as Centigrade
 
 The **Display temperature values as Centigrade** checkbox controls the temperature display:
 

diff --git a/docs/integration/external-integrations/jenkins-integration.mdx b/docs/integration/external-integrations/jenkins-integration.mdx
@@ -15,7 +15,7 @@ If you like this integration, check out the [Device42 integration page](https://
 
 ![Jenkins](/assets/images/Jenkins-logo-butler-transparent.png)
 
-### Build he Jenkins plugin from source (optional)
+## Build the Jenkins Plugin From Source (Optional)
 
 _Note: **Maven** is required to build the plugin._
 
@@ -24,7 +24,7 @@ _Note: **Maven** is required to build the plugin._
 3. Call Maven install to build the plugin: `mvn install -DskipTests`
 4. Follow "Configuring Jenkins" section below to install the plugin you just built into Jenkins.
 
-### Configuring Jenkins
+## Configuring Jenkins
 
 1. Login to your Jenkins instance.
 2. Select the 'Manage Jenkins' Gear icon from the menu on the left, and then choose ‘Manage Plugins’ (green puzzle piece) --> 'Advanced' tab.
@@ -33,15 +33,15 @@ _Note: **Maven** is required to build the plugin._
 
 
 
-### Configuring Device42
+## Configuring Device42
 
 Device42 doesn't require any specific configuration for the integration other than having your D42 Main appliance up and running & its API accessible.
 
 New passwords and Secrets are created & managed within Device42 (no changes from your usual workflow), and those secrets are read by the integration via the Device42 API each time Jenkins automation runs.
 
 
 
-### Using the Device42-Jenkins credentials integration
+## Using the Device42-Jenkins Credentials Integration
 
 The Device42-Jenkins credentials integration allows you to use passwords/secrets stored in Device42 within Jenkins automations by pulling them via the Device42 API when Jenkins automations run. Credentials stored within Device42 are made available in Jenkins as _variables_, the names of which are user-customizable. Each D42 credential variable may be referenced as many times as desired within a Jenkins automation.
 

diff --git a/docs/reports/reports/cloud-endure-device42.mdx b/docs/reports/reports/cloud-endure-device42.mdx
@@ -40,7 +40,7 @@ After ensuring the workloads in scope have the CloudEndure agent installed, down
     }}
   />
 
-### What Happens Next?
+## What Happens Next?
 
 Once you have generated the CloudEndure **CSV** file from **Advanced Reporting**, you must make sure to download the [Mass Blueprint Setter](https://docs.cloudendure.com/Content/Scripts/CloudEndure%20mass%20blueprints%20setter.zip) script.
 
@@ -77,7 +77,7 @@ When ready to run, supply all of the above parameters. If there are any issues w
 
 Once completed, all the machines in the CSV file that match machines in CloudEndure will have their respective blueprints updated.
 
-### Reference Links
+## Reference Links
 
 CE API Docs available with Sample Scripts - [https://docs.cloudendure.com/Content/Getting\_Started\_with\_CloudEndure/API/API.htm](https://docs.cloudendure.com/Content/Getting_Started_with_CloudEndure/API/API.htm)
-Original file line number
+Diff line change
@@ Expand Up @@
       }}
     />
-    ### Additional Options
+    ## Additional Job Options
     You can set a schedule to run the job automatically, turn off the default **Create Device from DHCP lease information** option, and set a **Service Level**.
@@ Expand Down @@