Misc fixes: e.g. -> e.g., and proper case for Home Assistant (#4942)

* e.g. to e.g., and proper case for Home Assistant

* Instructions how to -> Instructions on how to

source/_posts/2015-08-09-mqtt-raspberry-pi-squeezebox-asuswrt-support.markdown

@@ -104,7 +104,7 @@ sensor:
     device: PATH_TO_DEVICE
 ```
 
-The path to your device, e.g. `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0`
+The path to your device, e.g., `/dev/serial/by-id/usb-RFXCOM_RFXtrx433_A1Y0NJGR-if00-port0`
 
 __TEMPer temperature sensor support__
 Support for Temper temperature sensors has been contributed by [@rkabadi](https://github.com/rkabadi).

source/_posts/2016-02-09-Smarter-Smart-Things-with-MQTT-and-Home-Assistant.markdown

@@ -169,7 +169,7 @@ homeassistant:
         - mqtt
 ```
 
-This will start home-assistant, MQTT, and the Bridge, in dependency order. All config can reference the name of the docker container instead of using IP addresses (e.g. mqtt for the broker host in Home Assistant).
+This will start home-assistant, MQTT, and the Bridge, in dependency order. All config can reference the name of the docker container instead of using IP addresses (e.g., mqtt for the broker host in Home Assistant).
 
 ### How it works
 

source/_posts/2016-04-30-ibeacons-part-1-making-presence-detection-work-better.markdown

@@ -26,7 +26,7 @@ Luckily, OwnTracks supports iBeacons so I could use them to make presence detect
 
 ### {% linkable_title Getting Started %}
 
-To do this you first need to set up [MQTT] and [OwnTracks] in Home assistant - and make sure that HA can track your phone.
+To do this you first need to set up [MQTT] and [OwnTracks] in Home Assistant - and make sure that HA can track your phone.
 
 [MQTT]: /components/mqtt/#picking-a-broker
 [OwnTracks]: /components/device_tracker.owntracks/
@@ -57,7 +57,7 @@ Once you’ve created the zone - you need to restart HA. The next step is:-
 1. Go to the OwnTracks app on your phone
 2. Touch the `Regions` menu at the bottom of the screen
 3. Touch the `+` symbol at the top right of the screen
-4. Give the beacon a name e.g. `-drive` ’(start the name with a `-` see below for the reason)
+4. Give the beacon a name e.g., `-drive` ’(start the name with a `-` see below for the reason)
 5. Turn Share to `On`
 6. Skip the `Circular Region` section
 7. Enter the `UUID` of your beacon - this may be written on your beacon - or you can copy it from the management app that came with your iBeacon device. It’s a long number – so it’s easier to copy if you can!

source/_posts/2016-08-16-we-have-apps-now.markdown

@@ -32,7 +32,7 @@ So why `AppDaemon`? `AppDaemon` is not meant to replace Home Assistant Automatio
 
 - New paradigm - some problems require a procedural and/or iterative approach, and `AppDaemon` Apps are a much more natural fit for this. Recent enhancements to Home Assistant scripts and templates have made huge strides, but for the most complex scenarios, Apps can do things that Automations can't
 - Ease of use - `AppDaemon`'s API is full of helper functions that make programming as easy and natural as possible. The functions and their operation are as "Pythonic" as possible, experienced Python programmers should feel right at home.
-- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g. a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file
+- Reuse - write a piece of code once and instantiate it as an app as many times as you need with different parameters e.g., a motion light program that you can use in 5 different places around your home. The code stays the same, you just dynamically add new instances of it in the config file
 - Dynamic - `AppDaemon` has been designed from the start to enable the user to make changes without requiring a restart of Home Assistant, thanks to its loose coupling. However, it is better than that - the user can make changes to code and `AppDaemon` will automatically reload the code, figure out which Apps were using it and restart them to use the new code without the need to restart `AppDaemon` itself. It is also possible to change parameters for an individual or multiple apps and have them picked up dynamically, and for a final trick, removing or adding apps is also picked up dynamically. Testing cycles become a lot more efficient as a result.
 - Complex logic - Python's If/Else constructs are clearer and easier to code for arbitrarily complex nested logic
 - Durable variables and state - variables can be kept between events to keep track of things like the number of times a motion sensor has been activated, or how long it has been since a door opened

source/_posts/2017-11-04-release-57.markdown

@@ -120,7 +120,7 @@ Experiencing issues introduced by this release? Please report them in our [issue
 
   This fixes errors when an entity has an attribute that is not "a string, bytearray, int, float or None" and mqtt_statestream is used. As of now, the attribute is just handed over to paho, and paho can only send the aforementioned types. This patch fixes the issue by just casting everything to string before handing it over to paho.
 
-  There are a number of components / entities which have "other" attributes, e.g. light that have an RGB attribute which is a list. ([@tinloaf] - [#9872]) ([mqtt_statestream docs]) (breaking change)
+  There are a number of components / entities which have "other" attributes, e.g., light that have an RGB attribute which is a list. ([@tinloaf] - [#9872]) ([mqtt_statestream docs]) (breaking change)
 - Generic thermostat: the configuration option `tolerance` has been removed and has been replaced by `cold_tolerance` and `hot_tolerance`. This allows on and off states to have different error bands. ([@biggms] - [#9843]) ([climate.generic_thermostat docs]) (breaking change)
 - Developers only: frontend has been refactored. The method `register_panel` has been turned into a coroutine function called `async_register_panel`. The parameter `url_path` has been renamed to `frontend_url_path`. For frontend, development, you no longer pass `development: 1` to the http component but instead configure the frontend component to be in development mode by pointing it at a local checkout of the Polymer repo: ([@balloob] - [#9915]) (breaking change)