diff --git a/bitwarden_rs/readme.md b/bitwarden_rs/readme.md
index 4e9f8fe..bcbac1d 100644
--- a/bitwarden_rs/readme.md
+++ b/bitwarden_rs/readme.md
@@ -100,7 +100,7 @@ passwd.{$MY_DOMAIN} {
 # Forward port 3012 TCP on your router
 
 [WebSocket](https://youtu.be/2Nt-ZrNP22A) protocol is used for notifications,
-so that all web based clients can immediatly sync when a change happens on server.
+so that all web based clients can immediatly sync when a change happens on the server.
 
 * Enviromental variable `WEBSOCKET_ENABLED=true` needs to be set.</br>
 * Reverse proxy needs to route `/notifications/hub` to port 3012.</br>
diff --git a/ddclient/readme.md b/ddclient/readme.md
index 477556b..e4b6200 100644
--- a/ddclient/readme.md
+++ b/ddclient/readme.md
@@ -59,8 +59,10 @@ PGID=1000
 # Configuration
 
 Official ddclient config example
-[here](https://github.com/ddclient/ddclient/blob/master/sample-etc_ddclient.conf).</br>
-Make sure A-records exist on cloudflare.
+[here](https://github.com/ddclient/ddclient/blob/master/sample-etc_ddclient.conf).
+
+This setup assumes the DNS are managed Cloudflare.
+Make sure all subdomains in the config have A-records on Cloudflare.
 
 `ddclient.conf`
 
diff --git a/nextcloud/readme.md b/nextcloud/readme.md
index 1f49d04..0f2a061 100644
--- a/nextcloud/readme.md
+++ b/nextcloud/readme.md
@@ -30,11 +30,15 @@ File share & sync.
 
 Official examples [here](https://github.com/nextcloud/docker/tree/master/.examples/docker-compose)
 
-Four containers are spin up
-  - `nextcloud` - nextcloud app with apache web server with php as a module 
-  - `nextcloud-db` - mariadb database where files-metadata and users-metadata are stored
-  - `nextcloud-redis` - in memory file caching and more reliable transactional file locking
-  - `nextcloud-cron` - for being able to run maintenance cronjobs
+Four containers to spin up
+
+* **nextcloud** - nextcloud app that stores uploaded files and runs
+  apache web server with php as a module.
+* **nextcloud-db** - mariadb database where files-metadata
+  and users-metadata are stored
+* **nextcloud-redis** - in memory file caching
+  and more reliable transactional file locking
+* **nextcloud-cron** - for being able to run maintenance cronjobs
 
 `docker-compose.yml`
 ```yml
@@ -132,7 +136,8 @@ If one does not exist yet: `docker network create caddy_net`
 # Reverse proxy
 
 [Nextcloud official documentation](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/reverse_proxy_configuration.html)
-regarding reverse proxy.</br>
+regarding reverse proxy.
+
 Caddy v2 is used,
 details [here](https://github.com/DoTheEvo/Caddy-v2-docker-example-setup).</br>
 There are few extra directives here to fix some nextcloud warnings.
@@ -161,7 +166,7 @@ Editing config.php and adding the new domain will fix it.
 
 # Security & setup warnings
 
-Nextcloud has status check in *Settings > Administration > Overview*</br>
+Nextcloud has a status check in *Settings > Administration > Overview*</br>
 There are likely several warnings on a freshly spun container.
 
 ##### The database is missing some indexes
diff --git a/portainer/readme.md b/portainer/readme.md
index 4675675..31cb688 100644
--- a/portainer/readme.md
+++ b/portainer/readme.md
@@ -6,7 +6,8 @@
 
 # Purpose
 
-User friendly overview of running containers.
+User friendly overview and managment of the running containers,
+networks, volumes, images,...
 
 # Files and directory structure
 
diff --git a/prometheus_grafana/readme.md b/prometheus_grafana/readme.md
index c6f24c8..b1a37d1 100644
--- a/prometheus_grafana/readme.md
+++ b/prometheus_grafana/readme.md
@@ -15,19 +15,6 @@ Monitoring of the host and the running cointaners.
 Everything here is based on the magnificent
 [stefanprodan/dockprom](https://github.com/stefanprodan/dockprom)
 
-# Containers
-
-* **Prometheus** - monitoring system that pulls and stores data from exporters
-  and then exposes them for visualization.
-  Can also alert if a metric fails preset rule.
-* **Grafana** - web based visualization of the collected metrics
-  in nice graphs, gauges, tables,...
-* **NodeExporter** - exporter for linux machines,
-  in this case gathering docker host metrics,
-  like uptime, cpu load, memory use, network bandwidth use, disk space,...
-* **cAdvisor** - exporter for gathering docker containers metrics,
-  showing cpu, memory, network use of each container
-
 # Files and directory structure
 
 ```
@@ -57,6 +44,21 @@ Everything here is based on the magnificent
 
 # docker-compose
 
+Four containers to spin up.</br>
+While the illustrious [stefanprodan/dockprom](https://github.com/stefanprodan/dockprom)
+also got alertmanager and pushgateway, this is a simpler setup for now.
+
+* **Prometheus** - monitoring system that pulls and stores data from exporters
+  and then exposes them for visualization.
+  Can also alert if a metric fails preset rule.
+* **Grafana** - web based visualization of the collected metrics
+  in nice graphs, gauges, tables,...
+* **NodeExporter** - exporter for linux machines,
+  in this case gathering docker host metrics,
+  like uptime, cpu load, memory use, network bandwidth use, disk space,...
+* **cAdvisor** - exporter for gathering docker containers metrics,
+  showing cpu, memory, network use of each container
+
 `docker-compose.yml`
 ```yml
 version: '3'
diff --git a/watchtower/readme.md b/watchtower/readme.md
index 73c2c5c..6671544 100644
--- a/watchtower/readme.md
+++ b/watchtower/readme.md
@@ -23,9 +23,9 @@ Automatic updates of containers.
 
 # docker-compose
 
-[scheduled](https://pkg.go.dev/github.com/robfig/cron@v1.2.0?tab=doc#hdr-CRON_Expression_Format)
-to run every saturday at midnight</br>
-Heads up that it's not a typical cron format, seconds are the first digit.
+Scheduled to run every saturday at midnight</br>
+Heads up that not a typical cron format is used,
+[seconds are the first digit](https://pkg.go.dev/github.com/robfig/cron@v1.2.0?tab=doc#hdr-CRON_Expression_Format).
 
 `docker-compose.yml`
 ```yml