Apply suggestions from code review

Co-authored-by: Gusted <[email protected]>

Author: zeripath

docs/content/doc/help/faq.en-us.md

@@ -356,7 +356,7 @@ Gitea requires the system or browser to have one of the supported Emoji fonts in
 
 ## Stdout logging on SystemD and Docker
 
-Stdout on systemd goes to the journal by default. Try using `journalctl` or `journalctl <path-to-gitea-binary>`.
+Stdout on systemd goes to the journal by default. Try using `journalctl`, `journalctl  -u gitea`, or `journalctl <path-to-gitea-binary>`.
 
 Similarly stdout on docker can be viewed using `docker logs <container>`
 
@@ -385,7 +385,7 @@ These can safely be ignored but you may able to stop these warnings by getting G
 gitea doctor recreate-table user
 ```
 
-This will cause Gitea to recreate these tables and copy the old data into the new table
+This will cause Gitea to recreate the user table and copy the old data into the new table
 with the defaults set appropriately.
 
 You can ask Gitea to recreate multiple tables using:

docs/content/doc/installation/with-docker.en-us.md

@@ -321,7 +321,7 @@ To understand what needs to happen, you first need to understand what happens wi
 8. The SSH server creates a user session for the `git` user, and using the shell for the `git` user runs the `command=`
 9. This runs `gitea serv` which takes over control of the rest of the SSH session and manages gitea authentication & authorization of the git commands.
 
-Now, for SSH passthrough to work we need the host SSH to match the public keys but then run the `gitea serv` on the docker. There are multiple ways of doing this - however, all of these require some information about the docker being passed to the host.
+Now, for the SSH passthrough to work, we need the host SSH to match the public keys and then run the `gitea serv` on the docker. There are multiple ways of doing this. However, all of these require some information about the docker being passed to the host.
 
 ### SSHing Shim (with authorized_keys)