diff --git a/source/_integrations/zwave_js.markdown b/source/_integrations/zwave_js.markdown
index a6ed1409279..b061a9db325 100644
--- a/source/_integrations/zwave_js.markdown
+++ b/source/_integrations/zwave_js.markdown
@@ -99,7 +99,7 @@ While your Z-Wave mesh is permanently stored on your dongle, the additional meta
 ### Adding a new device to the Z-Wave network
 
 1. In Home Assistant, go to {% my integrations title="**Settings** > **Devices & Services**" %}.
-1. In the Z-Wave integration, select **Configure**.
+1. In the Z-Wave integration, select the cogwheel, then select **Configure**.
 1. Select **Add device**.
    * The Z-Wave controller is now in inclusion mode.
 1. If your device supports SmartStart (700 series controller), select **Scan QR code** and scan the QR code on your device.
@@ -118,7 +118,7 @@ While your Z-Wave mesh is permanently stored on your dongle, the additional meta
 ### Removing a device from the Z-Wave network
 
 1. In Home Assistant, go to {% my integrations title="**Settings** > **Devices & Services**" %}.
-1. In the Z-Wave integration, select **Configure**.
+1. In the Z-Wave integration, select the cogwheel, then select **Configure**.
 1. Select **Remove device**, then **Start exclusion**.
    * The Z-Wave controller is now in exclusion mode.
 1. Put the device you want to remove in exclusion mode. Refer to its manual how this is done.
@@ -826,9 +826,9 @@ After ensuring you are using an extension cable, perform a network heal.
 
 The combination of these two steps corrects a large number of reported difficulties.
 
-#### I have an Aeotec Gen5 controller, and it isn't detected on my Raspberry Pi 4?
+#### I have an Aeotec Gen5 controller, and it isn't detected on my Raspberry Pi 4?
 
-The first-generation Gen5 controller has a known bug when plugged into a Pi 4 and possibly other systems. Aeotec released the Gen5+ stick to correct this bug. Gen5 users can plug their sticks into a USB 2.0 hub in order to overcome the issue.
+The first-generation Gen5 controller has a known bug when plugged into a Pi 4 and possibly other systems. Aeotec released the Gen5+ stick to correct this bug. Gen5 users can plug their sticks into a USB 2.0 hub in order to overcome the issue.
 
 #### I do not see any entities created for my device in Home Assistant
 
@@ -858,21 +858,24 @@ If the interview is complete, then the device does not yet have a device file fo
 
 #### How do I get a dump of the current network state?
 
-When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow the menu:
+When trying to determine why something isn't working as you expect, or when reporting an issue with the integration, it is helpful to know what Z-Wave JS sees as the current state of your Z-Wave network. To get a dump of your current network state, follow these steps:
 
-{% my integrations title="**Settings** -> **Devices & Services**" %} -> **Z-Wave** -> **...** -> **Download diagnostics**
+1. Go to {% my integrations title="**Settings** > **Devices & Services**" %}.
+1. On the **Z-Wave** integration, select the cogwheel, then select the three dots.
+1. From he dropdown menu, select **Download diagnostics**.
 
 ### Interference issues
 
-Many users have reported issues with interference when the USB stick was directly connected to the machine (proximity). If you are having issues try to use a short USB 2.0 A male to female extension cord.
+Many users have reported issues with interference when the USB stick was directly connected to the machine (proximity). If you are having issues, try to use a short USB 2.0 A (male to female) extension cord.
 
 #### How to access the Z-Wave logs
 
-Z-Wave JS writes details to its logs. To access these logs go to the following.
+Z-Wave JS writes details to its logs. To access these logs, follow these steps:
 
-   **Settings** -> **Devices & Services** -> **Integrations(tab)** -> **Z-Wave (CONFIGURE)** -> **Logs(tab)**
-
-You need to keep this browser tab open for logging to be active.
+1. Go to {% my integrations title="**Settings** > **Devices & Services**" %}.
+1. On the **Z-Wave** integration, select the cogwheel, then select **Configure**.
+1. Open the **Logs** tab.
+1. Make sure to keep this browser tab open. Otherwise the logging is not active.
 
 ## Z-Wave terminology