fixing README.md spelling (#899)

* Update README.md

fix spelling

* Update README.md

change 'time zone' to 'timezone'

README.md

@@ -45,7 +45,7 @@
 
 This is a custom component that is emerging from the
 [community discussion][community-discussion] of a need to be able to retrieve
-local google assistant device (like Google Home/Nest etc) authentication
+local Google Assistant device (like Google Home/Nest etc) authentication
 tokens and use those tokens making API calls to Google Home devices.
 
 ## IMPORTANT
@@ -85,7 +85,7 @@ Each of the alarms has the following keys:
 | `label` | Name | Name of the alarm, this can be set when making the alarm |
 | `recurrence` | List of integers | Days of the week when the alarm will go off. Please note, respecting Google set standard, the week starts from Sunday, therefore is denoted by 0. Correspondingly, Monday is 1, Saturday is 6 and so on |
 
-The state value shows the next alarm as a timestring (i.e.: `2021-03-07T15:26:17+01:00`) if there is at least one alarm set, otherwise it is set to `unavailable`.
+The state value shows the next alarm as a time string (i.e.: `2021-03-07T15:26:17+01:00`) if there is at least one alarm set, otherwise it is set to `unavailable`.
 This matches state format of [standard next alarm sensor](https://companion.home-assistant.io/docs/core/sensors/#next-alarm-sensor) provided by `mobile_app`.
 
 This sensor is formatted to be compatible with the mobile app sensor, e.g. `sensor.phone_next_alarm`.
@@ -294,7 +294,7 @@ Make sure that you have your Home Assistant Container network set to `host`, as
 
 ### ARM Docker Container Dependencies Workaround
 
-If you are installing this integration on an ARM based device (Like Raspberry Pi, Synology, etc), you may need to do the following if you get this error:
+If you are installing this integration on an ARM based device (Like Raspberry Pi, Synology, etc.), you may need to do the following if you get this error:
 
 ```
 ERROR: Cannot install glocaltokens==0.3.1