Tiny README tweak

README.md

@@ -9,7 +9,7 @@ git clone https://github.com/patschi/parsedmarc-dockerized.git /opt/parsedmarc-d
 cd /opt/parsedmarc-dockerized/ && cp data/conf/parsedmarc/config.sample.ini data/conf/parsedmarc/config.ini
 ```
 
-1. Next we change the `parsedmarc` config (see [docs](https://domainaware.github.io/parsedmarc/#configuration-file). You can set `Test` to `True` for testing purposes.)
+2. Next we change the `parsedmarc` config (see [docs](https://domainaware.github.io/parsedmarc/#configuration-file). You can set `Test` to `True` for testing purposes.)
 ```
 nano data/conf/parsedmarc/config.ini
 ```
@@ -30,7 +30,7 @@ docker-compose up -d
 
 ### What's happening then?
 
-1. First, the all containers of the stack are created and started. Please notice that this might take a while, as several containers have dependencies on others being in a healthy state (meaning that the service must be fully operating).
+1. First, containers of the stack are created and started. This might take a while, as several containers have dependencies on others being in a healthy state (meaning that its service must be fully started).
 2. During the startup of the `parsedmarc-init` container, all required steps and preparations are being taken care of - like generating a self-signed certificate for the included `nginx` webserver.
 3. Once the Kibana container - where you can view the dashboards - is started up, the corresponding parsedmarc dashboards are automatically imported into Kibana by the `parsedmarc-init` container.
 4. After some while, when everything is up and running, you can then access Kibana and its dashboards under the shipped reverse proxy at `https://HOST_IP:9999`. (Make sure to use HTTPS!)