diff --git a/README.md b/README.md
index c1ec897..68dc442 100644
--- a/README.md
+++ b/README.md
@@ -78,14 +78,15 @@ workdir: ""
 
 The `Container` has to be consumed by other functions to actually export it to
 some registry or run it. The same is true for other types like `File` and
-`Directory` which also only expose the actual artifacts through effectful
+`Directory` which also only expose the actual artifacts through 'effectful'
 functions, thus the FP-like feeling. Only 'simple' strings can be exposed on
 the shell. Consequently, pipelining on the shell seems not to be a common
 thing.
 
 Dagger separates the containerized build environment from the host system.
 Unless specifically specified, like with `--source=.`, dagger does not expose
-host resources.
+host resources. This adds to the notion of trying to create reproducible
+actions.
 
 > Camel Case function names in the TS setup are available in Kebab Case on the
 > shell (same applies for Go and Python). This does not only apply to your own
@@ -132,9 +133,6 @@ dagger call security-scan --source=.
 > Python module can be used in a Typescript config. The proper API functions
 > are exposed on the `dag` object.
 
-> Most modules are just thin wrappers around specific images that contain for
-> example some tool and provide convenience functions.
-
 Push the container image to some registry:
 
 ```shell