Update Misc Typos (#11597)

* Update providers.markdown

* Update tutorial.markdown

* Update aws.markdown

* Update vera.markdown

source/_docs/authentication/providers.markdown

@@ -118,7 +118,7 @@ homeassistant:
           - group: system-users
 ```
 
-First note, for `trusted_users` configuration you need to use `user id`, which you can find through Configuration -> Users -> View User Detail. The `trusted_users` configuration will not validate the existing of the user, so please make sure you have put in the correct user id by yourself.
+First note, for `trusted_users` configuration you need to use `user id`, which you can find through Configuration -> Users -> View User Detail. The `trusted_users` configuration will not validate the existence of the user, so please make sure you have put in the correct user id by yourself.
 
 Second note, a trusted user with an IPv6 address must put the IPv6 address in quotes as shown.
 

source/_docs/ecosystem/appdaemon/tutorial.markdown

@@ -75,7 +75,7 @@ This is also fairly easy to achieve with Home Assistant automations, but we are
 
 ### Motion Light
 
-Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changesd where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callback function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
+Our next example is to turn on a light when motion is detected and it is dark, and turn it off after a period of time. This time, the `initialize()` function registers a callback on a state change (of the motion sensor) rather than a specific time. We tell AppDaemon that we are only interested in state changes where the motion detector comes on by adding an additional parameter to the callback registration - `new = "on"`. When the motion is detected, the callback function `motion()` is called, and we check whether or not the sun has set using a built-in convenience function: `sun_down()`. Next, we turn the light on with `turn_on()`, then set a timer using `run_in()` to turn the light off after 60 seconds, which is another call to the scheduler to execute in a set time from now, which results in `AppDaemon` calling `light_off()` 60 seconds later using the `turn_off()` call to actually turn the light off. This is still pretty simple in code terms:
 
 ```python
 import appdaemon.appapi as appapi

source/_integrations/aws.markdown

@@ -164,7 +164,7 @@ The SQS event payload will contain everything passed in the service call payload
 ```json
 {
   "title": "Test message!",
-  "target": "https://sqs.us-east-1.amazonaws.com/123456789012/queue2%22,
+  "target": "https://sqs.us-east-1.amazonaws.com/123456789012/queue2%22",
   "data": {
     "test": "okay"
   },

source/_integrations/vera.markdown

@@ -15,7 +15,7 @@ ha_category:
 ha_release: pre 0.7
 ---
 
-The [Vera](https://getvera.com/) hub is a controller mainly connecting to Z-Wave devices.
+The [Vera](https://getvera.com/) hub is a controller mainly for connecting to Z-Wave devices.
 
 There is currently support for the following device types within Home Assistant: