diff --git a/source/_docs/configuration/basic.markdown b/source/_docs/configuration/basic.markdown
index ff2bf2c2943..3cfa87fc8a1 100644
--- a/source/_docs/configuration/basic.markdown
+++ b/source/_docs/configuration/basic.markdown
@@ -4,7 +4,7 @@ description: "Setting up the basic info of Home Assistant."
 redirect_from: /getting-started/basic/
 ---
 
-As part of the default onboarding proccess, Home Assistant can detect your location from IP address geolocation. Home Assistant will automatically select a temperature unit and time zone based on this location. You may adjust this during onboarding, or afterwards at Configuration -> General. 
+As part of the default onboarding process, Home Assistant can detect your location from IP address geolocation. Home Assistant will automatically select a temperature unit and time zone based on this location. You may adjust this during onboarding, or afterwards at Configuration -> General. 
 
 If you prefer YAML, you can add the following information to your `configuration.yaml`:
 
diff --git a/source/_docs/configuration/packages.markdown b/source/_docs/configuration/packages.markdown
index 880dce51a88..d3ba7e9dba0 100644
--- a/source/_docs/configuration/packages.markdown
+++ b/source/_docs/configuration/packages.markdown
@@ -82,7 +82,7 @@ homeassistant:
 ```
 
 This uses the concept splitting the configuration and will include all files in a directory with the keys representing the filenames.
-See the documentation about [splitting the configuration](/docs/configuration/splitting_configuration/) for more information about `!include_dir_named` and other include statements that might be helpful. The benefit of this approach is to pull all configurations required to integrate a system, into one file, rather than accross several.
+See the documentation about [splitting the configuration](/docs/configuration/splitting_configuration/) for more information about `!include_dir_named` and other include statements that might be helpful. The benefit of this approach is to pull all configurations required to integrate a system, into one file, rather than across several.
 
 ### Customizing entities with packages
 
diff --git a/source/_docs/ecosystem/synology.markdown b/source/_docs/ecosystem/synology.markdown
index bfb3986552f..d9df9e24cf4 100644
--- a/source/_docs/ecosystem/synology.markdown
+++ b/source/_docs/ecosystem/synology.markdown
@@ -11,7 +11,7 @@ Synology NAS are the perfect companion to running Home Assistant. But by default
 Starting with DSM 6.2.1+, you can create "custom headers" in the Application Portal:
 * Go to Application Portal and edit your entry
 * Click on "custom headers" tab and click the dropdon on the "Create" button
-* Select "Websocket". This will automaticly add the required headers for websocket to this reverse proxy.
+* Select "Websocket". This will automatically add the required headers for websocket to this reverse proxy.
 * Click "OK". Home Assistant should work now with the reverse proxy.
 
 It's not necessary anymore to change the template anymore since Version DSM 6.2.1. Changing the `Portal.mustache` is not recommended! You should use the following part only if you're using a Version before DSM 6.2.1. on your Synology.
diff --git a/source/_docs/security.markdown b/source/_docs/security.markdown
index bdb36dd7582..d06d22e1a37 100644
--- a/source/_docs/security.markdown
+++ b/source/_docs/security.markdown
@@ -21,7 +21,7 @@ See the [open ports](/docs/security/porosity/) of a Hass.io instance with variou
 
 ## HTTP SSL/TLS
 
-Home Assistant is following the [Mozilla's Operations Security team recommendations](https://wiki.mozilla.org/Security/Server_Side_TLS) for Server side SSL/TLS settings. Home Assistant uses **Modern compatibility** by default. If an user wishes to use **Intermediate compatibilty**, this is configurable in the [`http` integration](/integrations/http/).
+Home Assistant is following the [Mozilla's Operations Security team recommendations](https://wiki.mozilla.org/Security/Server_Side_TLS) for Server side SSL/TLS settings. Home Assistant uses **Modern compatibility** by default. If an user wishes to use **Intermediate compatibility**, this is configurable in the [`http` integration](/integrations/http/).
 
 ## SSH
 
diff --git a/source/_docs/z-wave/device-specific.markdown b/source/_docs/z-wave/device-specific.markdown
index 6ed30e45d2c..f58e205f810 100644
--- a/source/_docs/z-wave/device-specific.markdown
+++ b/source/_docs/z-wave/device-specific.markdown
@@ -195,7 +195,7 @@ Triple tap on|2|4
 
 Many Zooz Zen26/27 switches that have been sold do not have firmware 2.0+. Contact Zooz to obtain the over the air firmware update instructions and new user manual for the switches.
 
-Once the firmware is updated, the the new configuration paramters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options (depending on your model of switch):
+Once the firmware is updated, the the new configuration parameters will have to be added to the `zwcfg` file. Replace the existing `COMMAND_CLASS_CONFIGURATION` with the one of the following options (depending on your model of switch):
 
 Zen26 (On/Off Switch):
 ```xml
@@ -329,7 +329,7 @@ For Zooz switches, you'll need to update (or possibly add) the `COMMAND_CLASS_CE
 </CommandClass>
 ```
 
-Go to the Z-Wave Network Management section in the Home Assistant Configuration, select the node which has just been updated and enable the scene support configuration paramter.
+Go to the Z-Wave Network Management section in the Home Assistant Configuration, select the node which has just been updated and enable the scene support configuration parameter.
 
 Once this is complete, you should see the following `zwave.scene_activated` events:
 
diff --git a/source/_integrations/alexa.smart_home.markdown b/source/_integrations/alexa.smart_home.markdown
index 2cac5ce2454..416a4e947da 100644
--- a/source/_integrations/alexa.smart_home.markdown
+++ b/source/_integrations/alexa.smart_home.markdown
@@ -20,7 +20,7 @@ Amazon provides a Smart Home API for richer home automation control. It takes
 considerable effort to configure. The easy solution is to use
 [Home Assistant Cloud](/integrations/cloud/).
 
-However, config Amazon Alexa Smart Home Skill is not a easy job, you have to allow
+However, config Amazon Alexa Smart Home Skill is not an easy job, you have to allow
 your Home Assistant accessible from Internet, and you need to create Amazon Developer
 account and an Amazon Web Service account. 
 
diff --git a/source/_integrations/aws.markdown b/source/_integrations/aws.markdown
index 259f8053a2f..8325a46dc5a 100644
--- a/source/_integrations/aws.markdown
+++ b/source/_integrations/aws.markdown
@@ -72,7 +72,7 @@ region_name:
   required: true
   type: string
 credential_name:
-  description: A reference to a `aws` credential. Notify platform will use the `default profile` defined in `~/.aws` if none of `credential_name`, `aws_access_key_id`, or `profile_name` was given.
+  description: A reference to an `aws` credential. Notify platform will use the `default profile` defined in `~/.aws` if none of `credential_name`, `aws_access_key_id`, or `profile_name` was given.
   required: false
   type: string
 aws_access_key_id:
diff --git a/source/_integrations/binary_sensor.template.markdown b/source/_integrations/binary_sensor.template.markdown
index 381493deffb..b8fa12ad0bb 100644
--- a/source/_integrations/binary_sensor.template.markdown
+++ b/source/_integrations/binary_sensor.template.markdown
@@ -238,7 +238,7 @@ binary_sensor:
 
 ### Device Tracker sensor with Latitude and Longitude Attributes
 
-This example shows how to combine an non-GPS (e.g. NMAP) and GPS device tracker while still including latitude and longitude attributes
+This example shows how to combine a non-GPS (e.g. NMAP) and GPS device tracker while still including latitude and longitude attributes
 
 {% raw %}
 ```yaml
diff --git a/source/_integrations/hyperion.markdown b/source/_integrations/hyperion.markdown
index 5b85e62de74..1d6424fdfe0 100644
--- a/source/_integrations/hyperion.markdown
+++ b/source/_integrations/hyperion.markdown
@@ -76,7 +76,7 @@ automation:
         effect: "Full color mood blobs"
 ```
 
-To have the lights playing a effect when pausing, idle or turn off a media player like plex you can use this example:
+To have the lights playing an effect when pausing, idle or turn off a media player like plex you can use this example:
 
 ```yaml
 - alias: Set hyperion effect after playback
diff --git a/source/_integrations/rejseplanen.markdown b/source/_integrations/rejseplanen.markdown
index f985da9a4f3..8d54e29a1d6 100644
--- a/source/_integrations/rejseplanen.markdown
+++ b/source/_integrations/rejseplanen.markdown
@@ -23,7 +23,7 @@ If you don't know the name of the stop follow this guide:
 - Now insert the coordinates for the location in the url, in this example it will be: [http://xmlopen.rejseplanen.dk/bin/rest.exe/stopsNearby?coordX=56.15756&coordY=10.20674&](http://xmlopen.rejseplanen.dk/bin/rest.exe/stopsNearby?coordX=56.15756&coordY=10.20674&)
 - You will now see the 30 stops closest to your location.
 
-You will se a output like this:
+You will see an output like this:
 
 ```text
 "StopLocation":[{
diff --git a/source/_integrations/waze_travel_time.markdown b/source/_integrations/waze_travel_time.markdown
index ef0b7186647..2f65bb76550 100644
--- a/source/_integrations/waze_travel_time.markdown
+++ b/source/_integrations/waze_travel_time.markdown
@@ -27,11 +27,11 @@ sensor:
 
 {% configuration %}
 origin:
-  description: Enter the starting address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, a entity id with latitude and longitude attributes, or zone friendly name.
+  description: Enter the starting address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name.
   required: true
   type: string
 destination:
-  description: Enter the destination address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, a entity id with latitude and longitude attributes, or zone friendly name.
+  description: Enter the destination address or the GPS coordinates of the location (GPS coordinates has to be separated by a comma). You can also enter an entity id which provides this information in its state, an entity id with latitude and longitude attributes, or zone friendly name.
   required: true
   type: string
 region:
diff --git a/source/_integrations/yessssms.markdown b/source/_integrations/yessssms.markdown
index 06b79c0be0c..322cde2d07f 100644
--- a/source/_integrations/yessssms.markdown
+++ b/source/_integrations/yessssms.markdown
@@ -9,7 +9,7 @@ ha_release: 0.57
 
 The `yessssms` platform is using the Austrian mobile operator [Yesss.at](https://yesss.at) and others to send SMS via their web-site.
 
-Currenty some MVNOs (mobile virtual network operators), in the A1 network, that use the kontomanager.at interface work. These are currently  (as of version 0.4.0 of [YesssSMS](https://pypi.org/project/YesssSMS/)): 
+Currently some MVNOs (mobile virtual network operators), in the A1 network, that use the kontomanager.at interface work. These are currently  (as of version 0.4.0 of [YesssSMS](https://pypi.org/project/YesssSMS/)): 
 * YESSS
 * billitel
 * EDUCOM