Include review comments.

Signed-off-by: Alexander Adam <alphaone23@gmail.com>

Author: AlphaOne1

README.md

@@ -281,9 +281,9 @@ Docker Usage
 docker run -p 8080:8080 ghcr.io/alphaone1/sonicweb:v1.6.0
 ```
 
-and it will show this documentation. The entrypoint of the dockerfile just starts *SonicWeb* without any parameters.
-So `/www` is the default web root directory. Every parameter passed after the image name is appended as a parameter
-to *SonicWeb*. For example, running
+and it will show this documentation. The entrypoint of the Dockerfile just starts *SonicWeb* without any parameters.
+Therefore, `/www` is the default web root directory. Every parameter passed after the image name is appended as a
+parameter to *SonicWeb*. For example, running
 
 ```sh
 docker run -p 8080:8080 ghcr.io/alphaone1/sonicweb:v1.6.0 --log=debug
@@ -296,15 +296,15 @@ is equivalent to running:
 ```
 
 The docker image is prepared to have new web content mounted on `/www` replacing the default content entirely. A new
-web root directory, e.g., `myapp/` could be mounted like this:
+web root directory, e.g., `myapp/`, can be mounted like this:
 
 ```sh
 docker run -p 8080:8080 -v ./myapp:/www:ro ghcr.io/alphaone1/sonicweb:v1.6.0
 ```
 
 Note that without specifying the `:ro` flag, the content will be mounted as read-write. *SonicWeb* does not write into
-the mounted directory. Nevertheless, it poses a potential risk. Also take care that the content of the mounts is
-readable by the non-root user that *SonicWeb* uses (UID 65532).
+the mounted directory. Nevertheless, it poses a potential risk. Ensure that the mounted content is readable by the
+non-root user that *SonicWeb* uses (UID 65532).
 
 If telemetry is needed, port 8081 needs to be exposed additionally: