Slight grammar and consistency improvements for Z-wave Device settings (home-assistant#1188)

philhawthorne · Landrash · commit d0317e222607 · 2016-10-09T10:07:01.000+02:00
Just some slight wording and consistency changes to make the Z-Wave
device specific page easier to read..
diff --git a/source/getting-started/z-wave-device-specific.markdown b/source/getting-started/z-wave-device-specific.markdown
@@ -11,7 +11,7 @@ footer: true
 
 ##### {% linkable_title Motion or alarm sensors %}
 
-In order for Home Assistant to recognize well the sensor, you will need to change its configuration from `Basic Set (default)` to `Binary Sensor report` or `Alarm report`.
+In order for Home Assistant to recognize some sensors, you will need to change its configuration from `Basic Set (default)` to `Binary Sensor report` or `Alarm report`.
 These devices will either show as a binary sensor or a sensor called `Alarm xxxx` and will report a numeric value. Test to see what value is what. Sometimes this is noted in the device manual.
 
 As of version 0.30 you can set the settings of a Z-Wave device through the dev_service page of Home Assistant with the service: `zwave/set_config_parameter`.
@@ -21,8 +21,8 @@ The following parameters can be entered:
 - **parameter** (*Required*): The index number of the parameter to be set. Refer to device manual or zwcfg_[home_id].xml
 - **value** (*Required*): The value to set the parameter to. Refer to device manual or zwcfg_[home_id].xml
 - **size** (*Optional*): The size of the value. It is normally not needed to specify this parameter, but in some cases it's needed. Check OZW.log for details on this.
-You should check OZW.log to see if setting has been set
-Example entry in dev-service, setting binary report for Aeotec multisensor 6:
+You should check OZW.log to see if your new setting has been set
+Example entry in dev-service, setting binary reports for an Aeotec Multisensor 6:
 ```yaml
 # Example entry in dev-service
 {"entity_id": "sensor.aetoec_multisensor_6_luminance_5",
@@ -33,10 +33,10 @@ Example entry in dev-service, setting binary report for Aeotec multisensor 6:
 
 ##### {% linkable_title Locks and other secure devices %}
 
-These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZwave's `options.xml` which is located in OpenZWave's directory. This should also be the same directory as `config_path:` in your `configuration.yaml`. If it's not, make sure you have the same values in all the files you are using.
+These devices require a network key to be set for the Z-Wave network before they are paired. This key is set in OpenZWave's `options.xml` which is located in OpenZWave's directory. This should also be the same directory as `config_path:` in your `configuration.yaml`. If it's not, make sure you have the same values in all the files you are using.
 The option is commented out by default in `options.xml` and is a default key. Make your own unique key. The key is in Hexadecimals.
-It is best to pair these devices in OpenZWave Control Panel or other Z-wave tool that can show you logs while pairing. Home Assistant show logs from zwave too and it is `OZW.log` in the Home Assistant config directory. 
-You should see communication from the node with lines starting with `info: NONCES` in `OZW.log` when the device is paired secure successfully. If you use Open Zwave Control Panel to pair, test the device before you save the configuration.
+It is best to pair these devices in OpenZWave Control Panel or another Z-Wave tool that can show you logs while pairing. Home Assistant stores logs from Z-Wave in `OZW.log` in the Home Assistant config directory. 
+You should see communication from the node with lines starting with `info: NONCES` in `OZW.log` when the device is paired successfully with a secure connection. If you use OpenZWave Control Panel to pair, test the device before you save the configuration.
 Make sure you copy the newly saved `zwcfg_[home_id].xml`into your Home Assistant configuration directory.
 
 
