Update z-wave.markdown

sgauche · web-flow · commit 150566a43421 · 2016-09-12T12:44:02.000-04:00
changed last 2 sentences based on @Landrash suggestion.
diff --git a/source/getting-started/z-wave.markdown b/source/getting-started/z-wave.markdown
@@ -199,7 +199,7 @@ The Z-Wave component exposes seven services to help maintain the network.
 | test_network | Tells the controller to send no-op commands to each node and measure the time for a response. In theory, this can also bring back nodes which have been marked "presumed dead".|
 | rename_node | Sets a node's name. Requires an `entity_id` and `name` field. |
 
-The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a zwave network running reliably as shown in the example below.  By default, Home Assistant will run a `heal_network` at midnight.  This is a configuration option for the zwave component, the option defaults to `true` but can be disabled by setting `auto_heal` to false.  Soft resetting some zwave controllers can cause the network to hang, so the below automation should only be used if there are issues with your zwave network.
+The `soft_reset` and `heal_network` commands can be used as part of an automation script to help keep a zwave network running reliably as shown in the example below.  By default, Home Assistant will run a `heal_network` at midnight.  This is a configuration option for the zwave component, the option defaults to `true` but can be disabled by setting `auto_heal` to false.  Using the `soft_reset` function with some z-wave controllers can cause the z-wave network to hang. If you're having issues with your z-wave network try disabling this automation.
 
 ```yaml
 # Example configuration.yaml automation entry
