1234: Grammar cleanup (Week 9, 2026)

docs/infrastructure-management/buildings-rooms-and-racks/auditing-racks.mdx

@@ -3,16 +3,43 @@ title: "Auditing Racks"
 sidebar_position: 1
 ---
 
-To create a list of all devices on a number of racks in Device42 to allow easy auditing, we will first browse to the Racks list view in Device42:
+import ThemedImage from '@theme/ThemedImage'
+import useBaseUrl from '@docusaurus/useBaseUrl'
 
-![Browse to Racks](/assets/images/2016-02-26-rack-audit-01.png)
+You can export rack data from Device42 to an Excel spreadsheet and use a barcode reader to audit physical devices against the records in Device42.
 
-From the Racks list view we will pick the racks we would like to audit against the actual equipment, and from the Action dropdown menu, select "Audit Export for Selected Racks":
+1. Navigate to **Infrastructure > DataCenter > Racks**:
 
-![Audit Export Racks](/assets/images/2016-02-26-rack-audit-03.png)
+<ThemedImage
+  alt="Racks menu navigation"
+  sources={{
+    light: useBaseUrl('/assets/images/auditing-racks/racks-menu-light.png'),
+    dark: useBaseUrl('/assets/images/auditing-racks/racks-menu-dark.png'),
+  }}
+/>
 
-Save the spreadsheet when prompted and open in Excel.
+2. Select the racks you want to audit, then choose **Export Selected Items** from the **Actions** menu:
+
+<ThemedImage
+  alt="Export Selected Items action"
+  sources={{
+    light: useBaseUrl('/assets/images/auditing-racks/export-action-light.png'),
+    dark: useBaseUrl('/assets/images/auditing-racks/export-action-dark.png'),
+  }}
+/>
+
+3. Select **Audit Export for Selected Racks** and click **Export**:
+
+<ThemedImage
+  alt="Audit Export for Selected Racks option"
+  sources={{
+    light: useBaseUrl('/assets/images/auditing-racks/audit-export-light.png'),
+    dark: useBaseUrl('/assets/images/auditing-racks/audit-export-dark.png'),
+  }}
+/>
+
+4. Save the spreadsheet when prompted and open it in Excel.
 
 ![Audit Spreadsheet](/assets/images/2016-02-26-rack-audit-04.png)
 
-With this spreadsheet open, you will be able to use a barcode reader and scan the devices in a rack by asset tag and compare to the information you have in Device42, updating to reflect changes as you move through the racks!
+5. With the spreadsheet open, use a barcode reader to scan devices in the rack by asset tag. Compare the scanned data to the records in Device42 and update the spreadsheet to reflect any changes as you move through the racks.

docs/infrastructure-management/buildings-rooms-and-racks/buildings-and-rooms.mdx

@@ -6,9 +6,9 @@ sidebar_position: 2
 import ThemedImage from '@theme/ThemedImage'
 import useBaseUrl from '@docusaurus/useBaseUrl'
 
-From the main menu, navigate to the Buildings list page under **Infrastructure > DataCenter > Buildings** to view and enter information about the buildings that house your data centers. In Device42, a room is part of a building. You can add rooms, racks, and other asset details to a building's information. 
+Device42 lets you model your physical infrastructure by organizing devices and assets into buildings, rooms, and racks. In Device42, a room is part of a building, and racks are part of a room. You can add rooms, racks, and other asset details to a building's record.
 
-Users with the [necessary permissions](/administration/role-based-access-control/index.mdx) can access the [Room Layout View](#room-layout-view) to see how the room layout represents a room and its objects.
+Navigate to **Infrastructure > DataCenter > Buildings** to view and manage buildings. Users with the [necessary permissions](/administration/role-based-access-control/index.mdx) can access the [Room Layout View](#room-layout-view) to see a visual representation of a room and its objects.
 
 ## Buildings List Page
 
@@ -48,7 +48,7 @@ Click the **Impact Chart** button on the view page to open the chart in a new ta
     }}
   />
 
-The Rooms associated with the Building are clickable links in the room layout view. You can click **Edit** to add or remove Rooms from a building.
+Rooms associated with the building are clickable links in the room layout view. Click **Edit** to add or remove rooms from a building.
 
   <ThemedImage
     alt="Buildings with Room links"
@@ -85,7 +85,7 @@ You'll see the following buttons:
 - **Impact Chart:** View a chart of devices, assets, and applications that rely on this room.
 - **Room Layout:** View a logical representation of the room. The [Room Layout View](#room-layout-view) section below provides more information.
 
-The right **Object List** panel displays the rooms that were included in the Rooms list view – the previous screen you were on when you clicked the room name - with whichever filters were applied. If your user account does not have permission to view buildings, you won't see "@ - Building" next to the room name.
+The right **Object List** panel displays the rooms from the Rooms list view you navigated from, with any filters that were applied. If your user account does not have permission to view buildings, you won't see "@ - Building" next to the room name.
 
 <ThemedImage
   alt="Rooms List View"
@@ -101,7 +101,7 @@ Navigate between sections, including the following, using the left **Breakdown**
 - **Devices:** View basic info about devices (like CRAC and UPS), click a device name to access the device details, or add a new device.
 - **Assets:** View basic info about assets (like breaker panels and DMARC locations), click an asset name to access the asset details, or add a new asset.
 
-The room view has clickable links to the Racks associated with it. You can click **Edit** to add or remove racks from a room.
+Racks associated with the room are linked in the room view. Click **Edit** to add or remove racks from a room.
 
 <ThemedImage
   alt="Rooms List View"
@@ -220,17 +220,17 @@ You can add racks and objects to the layout, move them around, resize and rotate
 
 - You can reposition and rotate multiple objects at once. Select multiple objects by dragging your cursor over them. Reposition multiple selected objects by dragging them. Rotate multiple selected objects using the rotate buttons in the popup.
 
-### Adding Objects to a Layout
+### Add Objects to a Layout
 
 Ensure that editing mode is enabled. Navigate to **Infrastructure > DataCenter > Rooms**, click the **Show** link under the **Layout** column, and select **Turn ON** from the layout view.
 
 You can add any asset type to the room and are not confined to the template objects available in the left panel, as shown above. You can even create your own asset types.
 
 Racks and other objects can be added via the API or from the **Tools > Imports/Exports** menu.
 
-### Mouse-Over Options
+### Hover Options
 
-If you hover over an object, you will see a popup with detailed information about the object.
+Hover over an object to see a popup with detailed information about the object.
 
 <ThemedImage
   alt="Object details"
@@ -247,9 +247,9 @@ For racks, you'll see the following information:
 - **Vendor**
 - **Available (Us)**
 - **Number of Devices**
-- **Total Power Ports** The total number of ports for all PDUs in the rack.
-- **Open Power Ports** The number of available power ports by connector type.
-- **Tags** Any tags added to the rack for labeling and classification purposes.
+- **Total Power Ports:** The total number of ports for all PDUs in the rack.
+- **Open Power Ports:** The number of available power ports by connector type.
+- **Tags:** Any tags added to the rack for labeling and classification purposes.
 - **Notes**
 
 If you have [Power and Environmental Monitoring](/infrastructure-management/power-and-environmental-monitoring/index.mdx) enabled, you will also see the following information:
@@ -269,7 +269,7 @@ The popup also has links to several additional views.
     }}
     />
 
-- **View [name] Power Unit Map:**
+- **View [name] Power Unit Map:** Click this link to display a map of the power units in the rack.
 
     <ThemedImage
     alt="Power Unit map"
@@ -282,16 +282,16 @@ The popup also has links to several additional views.
 - **View [name] details:** Click this link to go to the **Rack Details** page for the rack.
 
     <ThemedImage
-    alt="Power Unit map"
+    alt="Rack detail view"
     sources={{
         light: useBaseUrl('/assets/images/buildings-and-rooms/rack-detail-view-light.png'),
         dark: useBaseUrl('/assets/images/buildings-and-rooms/rack-detail-view-dark.png'),
     }}
-    />  
+    />
 
 - **Power/Utilization Charts:** Click this link to display the power history for each input and output. Note that this link is only available if you have the Power Monitoring option.
 
-- **View Connections:** Mouse over the rack displayed in the object popup panel to find this link. Click the link to display a visualization of the PDU connections in the rack. 
+- **View Connections:** Hover over the rack in the object popup panel to find this link. Click the link to display a visualization of the PDU connections in the rack.
 
     <ThemedImage
     alt="View connections link"
@@ -313,7 +313,7 @@ You can set the object colors to denote usage or temperature information. Choose
   }}
 />
 
-In addition, you can choose to **Show temperature bubbles** or turn it off.
+You can also toggle the **Show temperature bubbles** option on or off.
 
 <ThemedImage
   alt="Display heatmap bubbles"
@@ -324,7 +324,7 @@ In addition, you can choose to **Show temperature bubbles** or turn it off.
   style={{ width: '60%' }}
 />
 
-These options are saved in cookies, so you don't have to reselect the combination of options that works best for you when revisiting the page.
+These options are saved in cookies, so your preferred settings are restored when you revisit the page.
 
 **Usage Heatmap Legend**
 
@@ -354,9 +354,9 @@ In rooms that have temperature information, halo temperature shading around rack
 
 The default color value is based on the maximum temperature of the rack and corresponds to the following temperatures:
 
-- **Green:** \<\= 75°F (23.88°C)
-- **Yellow:** Between > 75°F (23.88°C) and \<\= 90°F (32.22°C)
-- **Red:** > 90°F (32.22°C)
+- **Green:** \<\= 75°F (23.88°C)
+- **Yellow:** Between > 75°F (23.88°C) and \<\= 90°F (32.22°C)
+- **Red:** > 90°F (32.22°C)
 
 You can update the high and moderate temperature values from the Racks section under **Tools > Settings > Global Settings**. The room rack view updates accordingly.
 
@@ -370,7 +370,7 @@ You can update the high and moderate temperature values from the Racks section u
 
 ### PDU Power Monitoring
 
-If you have the Power Monitoring option, you will see a rectangular bar for each input of every PDU in the rack. These bars are color-coded for power usage and represent the amount of power currently in use divided by the power capacity of the input. Green is high, and red is low. You can change the percentages in **Tools > Settings > Global Settings**.
+If you have the Power Monitoring option, you will see a rectangular bar for each input of every PDU in the rack. These bars are color-coded for power usage and represent the amount of power currently in use divided by the power capacity of the input. Green indicates high available capacity, and red indicates low available capacity. You can change the percentages in **Tools > Settings > Global Settings**.
 
 ![Heat Maps](/assets/images/wpid6004-media_1424515509781.png)
 
@@ -398,4 +398,3 @@ The following operations are available from the **Actions** dropdown menu on the
 - **Add Groups**: Select and add a permission group to the selected buildings or rooms.
 - **Delete Groups**: Select and remove a permission group from the selected buildings or rooms.
 - **Set Custom Field Value**: Add a populated custom field parameter to the selected buildings or rooms.
-

docs/infrastructure-management/buildings-rooms-and-racks/impact-charts.mdx

@@ -18,7 +18,9 @@ Click the **Impact Chart** button at the top of the screen:
   }}
 />
 
-Device42's powerful, agentless autodiscovery uses native WMI and SSH in combination with other platform-dependent technologies to identify the details of running services and listening ports, and the relationships between those services and ports or executables and ports. This provides a clear picture of exactly which services or executables are listening on which ports on a machine. Device42 also goes on to capture a point-in-time snapshot of the IP addresses that are connected to each listening port. Should these communicating IP addresses already exist in Device42 and be mapped to a device, the system automatically shows that device when drawing the dynamic impact charts.
+Device42's agentless discovery uses native WMI and SSH, along with other platform-dependent technologies, to identify running services, listening ports, and the relationships between them. This provides a clear picture of which services or executables are listening on which ports on a machine.
+
+Device42 also captures a point-in-time snapshot of the IP addresses connected to each listening port. If those IP addresses already exist in Device42 and are mapped to a device, the system automatically includes that device when drawing impact charts.
 
 ## Impact Charts for Buildings, Rooms, and Racks
 
@@ -46,7 +48,7 @@ The following is a sample room impact chart:
 
 Looking at the impact chart for a room, from left to right, you see the room itself, the list of racks (with one rack selected), and all the servers that are located in the selected rack. You can view a legend via the **Legend** button above.
 
-Now, let's gather more information about one of the servers. You can do this easily by hovering over it (or any item in the chart) as such:
+To get more information about a server, hover over it (or any item in the chart):
 
 <ThemedImage
   alt="Hover over server for details demonstration"
@@ -82,7 +84,7 @@ Topology charts provide a full picture of all the services, executables, and app
 
 For example, if the device is a blade chassis or a virtual host, all the blades or virtual machines would be dependent on the device, and you would see those dependencies. Similarly, if Device42 discovers that a remote device is connecting to a port on the device, you would see the remote device (and its services, executables, and application components) in the topology chart. You can also manually define which application components depend on which other application component (see below), and those custom dependencies will display in the chart as well.
 
-Below is the topology chart for a device. (Don't try to read the details. We'll zoom in below.)
+Below is the topology chart for a device (details are shown in the sections below):
 
 <ThemedImage
   alt="Device topology chart"
@@ -92,7 +94,7 @@ Below is the topology chart for a device. (Don't try to read the details. We'll
   }}
 />
 
-### Topology Element Overview:
+### Topology Element Overview
 
 **Global View** is a simplified view of device-to-device directionality in relationship. No details of the relationship are viewable here, except the hostnames that have interactions with each other. Any type of device can be visible here. If there is any relationship of services, applications, hypervisor, or virtual, it will be represented in the **Global View**.
 
@@ -139,7 +141,7 @@ The device topology chart has its own legend:
   style={{ width: '50%' }} 
 />
 
-The **Display Options** are used to manipulate current in-view objects based on the below criteria:
+Use the **Display Options** to filter the objects currently shown in the topology:
 
 - **Hide services without connections:** This shows any service objects that have been discovered on an in-view and associated device, but with no connections yet discovered or added. (By default, this box is checked.)
 - **Hide client IP addresses with no Device/Managed Resources:** This shows IP addresses for any remote connections that were found in the netstat table of the in-view discovered devices. These are not yet considered **Device** objects in the database and are classified as clients or remote connections of the service objects. (By default, this box is checked).
@@ -230,7 +232,7 @@ Most impact and topology screens have a **Create Image** button that allows you
   }}
 />
 
-The **Create Image** button allows you to choose from two layout options: You may choose the Global or the Local view pane, and can also choose either **PNG** format or **SVG** (vector) image format. Simply click the **Download** button to choose your save location, and save the file wherever is convenient for you.
+The **Create Image** button lets you choose between the Global and Local view panes, and either **PNG** or **SVG** (vector) image format. Click the **Download** button to save the file.
 
 **Service Dependencies Report Download**
 
@@ -260,7 +262,7 @@ An impact list is simply a list version of an impact graph. Impact lists are typ
   }}
 />
 
-The full impact list for a device. Sometimes, it is useful to hide services without connections, which significantly reduces clutter by hiding services you may not be concerned with (many services that fit this criteria are standard operating-system components). See the example following the full list for more details:
+The full impact list for a device is shown below. You can hide services without connections to reduce clutter — many such services are standard operating system components.
 
 <ThemedImage
   alt="Device Impact List Full"
@@ -330,11 +332,11 @@ A dependency chart _(previously a 'dependency graph')_ can also be generated for
 
 ## How Are Dependencies Created in Device42?
 
-One question that comes up in almost every demo is, "How are all these dependencies created?" Nearly all the dependencies you saw in the above charts were _automatically created by autodiscovery_ in combination with internal Device42 correlation processes.
+Nearly all the dependencies shown in the charts above are automatically created by discovery in combination with internal Device42 correlation processes.
 
 It should be fairly obvious how all the physical dependencies are created: buildings have rooms, which have racks, which have devices. The blades in a chassis are dependent on their blade host, while virtual machines (VMs) are dependent on their virtual host(s).
 
-Software and services that are discovered on a virtual or physical machine are dependent on that machine. Many of the service-to-service dependencies or software are autodiscovered.
+Software and services that are discovered on a virtual or physical machine are dependent on that machine. Many service-to-service dependencies and software relationships are discovered automatically.
 
 Only some application components need to be manually entered. If a service is defined to be an application component, then the application component dependencies are all known.
 

docs/infrastructure-management/buildings-rooms-and-racks/index.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Buildings Rooms and Racks"
+title: "Buildings, Rooms, and Racks"
 ---
 
-This section covers the management of buildings, rooms, and racks in Device42. Use the sidebar to navigate to specific topics.
+Device42 models your physical data center infrastructure as a hierarchy of buildings, rooms, and racks. You can visualize room layouts with heatmaps and drag-and-drop rack placement, audit rack contents against physical inventory using barcode scanners, and use impact charts to trace dependencies from a building down to individual devices and services. Use the sidebar to navigate to specific topics.