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/_docs/configuration/group_visibility.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Group Visibility"
-description: "Instructions how to change group visibility using automations."
+description: "Instructions on how to change group visibility using automations."
 date: 2016-10-29 13:00
 sidebar: true
 comments: false

source/_docs/configuration/packages.markdown

@@ -63,7 +63,7 @@ light:
 
 There are some rules for packages that will be merged:
 
-1. Component names may only use the basic form (e.g. `switch`, but not `switch 1` or `switch aa`).
+1. Component names may only use the basic form (e.g., `switch`, but not `switch 1` or `switch aa`).
 2. Platform based components (`light`, `switch`, etc) can always be merged.
 3. Components where entities are identified by a key that will represent the entity_id (`{key: config}`) need to have unique 'keys' between packages and the main configuration file. 
 

source/_docs/configuration/securing.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Securing"
-description: "Instructions how to secure your Home Assistant installation."
+description: "Instructions on how to secure your Home Assistant installation."
 date: 2016-10-06 06:00
 sidebar: true
 comments: false

source/_docs/configuration/templating.markdown

@@ -1,7 +1,7 @@
 ---
 layout: page
 title: "Templating"
-description: "Instructions how to use the templating feature of Home Assistant."
+description: "Instructions on how to use the templating feature of Home Assistant."
 date: 2015-12-12 12:00
 sidebar: true
 comments: false