diff --git a/README.md b/README.md
index d56961e..6065ee4 100644
--- a/README.md
+++ b/README.md
@@ -35,7 +35,7 @@ __Includes__:
 
 - [Gamification](https://en.wikipedia.org/wiki/Gamification#Criticism) of the platform:
   - Two different levels of ranking with unique icons
-  - Exclusive obtainable badges for source code contributors and donator
+  - Exclusive obtainable badges for source code contributors and donators
 
 ![Dashboard contributors](./screenshots/dashboard-contributors2.png)
 ![Dashboard contributors2](./screenshots/dashboard-contributors3.png)
@@ -126,7 +126,7 @@ Just before running ./server.py do:
 ```
 export FLASK_DEBUG=1
 export FLASK_APP=server.py
-flask run --host=0.0.0.0 --port=8001 # <- Be careful here, this exposes it on ALL ip addresses. Ideally if run locally --host=127.0.0.1
+flask run --host=0.0.0.0 --port=8001 # <- Be careful here, this exposes the listening server on ALL IP addresses. Ideally if run locally --host=127.0.0.1
 ```
 
 OR, just toggle the debug flag in start_all.sh or config.cfg.
@@ -150,7 +150,7 @@ optional arguments:
 ## Notes about ZMQ
 The misp-dashboard being stateless in regards to MISP, it can only process data that it received. Meaning that if your MISP is not publishing all notifications to its ZMQ, the misp-dashboard will not have them.
 
-The most revelant example could be the user login punchcard. If your MISP doesn't have the option ``Plugin.ZeroMQ_audit_notifications_enable`` set to ``true``, the punchcard will be empty.
+The most relevant example could be the user login punchcard. If your MISP doesn't have the option ``Plugin.ZeroMQ_audit_notifications_enable`` set to ``true``, the punchcard will be empty.
 
 ## Dashboard not showing results - No module named zmq
 When the misp-dashboard does not show results then first check if the zmq module within MISP is properly installed.