Minor corrections + add chat

content/post/monitoring-iot-devices-with-MASH.md

@@ -14,7 +14,7 @@ In the end this will enable you to get to something like this:
 
 ![A screenshot of a grafana dashboard. It shows one panel with temperature and humindity values over an hour, one panel showing CO2 data and one showing energy consumption](/uploads/monitoring-iot-devices-with-MASH/grafana_screenshot1.png)
 
-While writing, I decided to split this into two parts. Part 1 will set up our server infrastructure, Part 2 will show inegrate some real sensors.
+While writing, I decided to split this into two parts. Part 1 will set up our server infrastructure, Part 2 will show how to integrate some real sensors.
 
 Let's get started with Part 1 and answer:
 
@@ -33,11 +33,11 @@ MASH includes services like
 and more than 50 others at time of writing this blogpost ([List of all supported services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md)).
 
 The motivation for this playbook is to have all services run in docker, be as configurable as possible, while maintaining easy upgrades and reproducible deployments.
-The documentation IMHO is very good so if people are willing to use ansible this might be a lot easier than writing roles themself.
+The documentation IMHO is very good, so if people are willing to use ansible this might be a lot easier than writing roles themself.
 
 # Architecture
 
-In the end we will have a IoT device that sends data to a MQTT topic on the MQTT broker Mosquitto. Telegraf will listen to this topic and write this into InfluxDB. When you want to have a look at the data, you can access Grafan which will querey InfluxDB.
+In the end we will have a IoT device that sends data to a MQTT topic on the MQTT broker Mosquitto. Telegraf will listen to this topic and write this into InfluxDB. When you want to have a look at the data, you can access Grafan which will query InfluxDB.
 
 # Prerequisits
 
@@ -49,7 +49,7 @@ To have everything it needs to use MASH you should ensure the following things a
 
 **Configure DNS**
 
-In thi playbook we will set up some services wich will be reachable from via web interface (Grafana and InfluxDB) while others will not (Telegraf, Mosquitto). We will set a domain name for the server itself, one for Grafana and one for InfluxDB. This allows you to move services more easily. Feel free to adjust the setup to your needs (but don't forget to change tha `_hostname` variables accordingly later).
+By following this guide we will set up some services which will be reachable from via web interface (Grafana and InfluxDB) while others will not (Telegraf, Mosquitto). We will set a domain name for the server itself, one for Grafana and one for InfluxDB. This allows you to move services more easily. Feel free to adjust the setup to your needs (but don't forget to change tha `_hostname` variables accordingly later).
 
 
 | Service | Domain | Type | Target |
@@ -61,7 +61,7 @@ In thi playbook we will set up some services wich will be reachable from via web
 
 # Set up the services
 
-Setting up the services will require three steps. The first will set up the general server with mosquitto and influxdb. Then we configure mosquitto and influxdb and use this to set up telegraf and grafana.
+Setting up the services will require three steps. The first will set up the general server with Mosquitto and Influxdb. Then we configure mosquitto and influxdb and use this to set up Telegraf and Grafana.
 
 ## Setting up the basis, Mosquitto and InfluxDB
 
@@ -342,7 +342,7 @@ add a nice title (4) and apply to see tha data (5). You should now have a nice d
 
 Please let me know when you follow this guide - wheter sucessful or not! I would love to improve it.
 
-I know this seems like a lot of effort to get a few numbers to display a few numbers nicely. On the other hands, once set up this setup can doa lot of stuff, monitoring, to alerting. Upgrades should be taken care of by MASH, check out how to do that [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/maintenance-upgrading-services.md). Also setting up more services is a breeze. either check the list of existing services, or add a new role to the playbook. If you don't know how, I am happy to help!
+I know this seems like a lot of effort to get a few numbers to display a few numbers nicely. On the other hands, once set up this setup can do a lot of stuff, from monitoring, to alerting. Upgrades should be taken care of by MASH, check out how to do that [here](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/maintenance-upgrading-services.md). Also setting up more services is a breeze. Either check the [list of existing services](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/supported-services.md), or add a new role to the playbook. If you don't know how, I am happy to help!
 
 So make sure to follow my [RSS feed](https://hyteck.de/index.xml) or any of my socials to get notified when Part 2 comes around. 
 
@@ -360,3 +360,6 @@ When something doesn't work feel free to
   + [Grafana](https://github.com/mother-of-all-self-hosting/mash-playbook/blob/main/docs/services/grafana.md)
 
 * **[Message me](https://hyteck.de/about/#contact)**
+
+{{< chat monitoring-with-mash >}}
+