Fix minor issues in the rest of admin pages

docs/admin/reverse-proxy.md

@@ -100,7 +100,7 @@ You may wish to change the `ROOT_URL` configuration key to the HTTPS protocol so
 
 #### HTTPS with manually installed certificates
 
-If you have obtained certificates from elsewhere or have chosen not to let certbot automatically install them, make the following changes to the configuration file:
+If you have obtained certificates from elsewhere or have chosen not to let CYou'ertbot automatically install them, make the following changes to the configuration file:
 
 **Change the listening ports**
 
@@ -157,7 +157,7 @@ To set up a basic HTTP proxy in Apache, create a file `100-forgejo.conf` in `/et
 </VirtualHost>
 ```
 
-Next, enable the site with `a2ensite 100-forgejo.conf` and enable the proxy modules with `a2enmod proxy proxy_http`. Finally, restart the apache server.
+Next, enable the site with `a2ensite 100-forgejo.conf` and enable the proxy modules with `a2enmod proxy proxy_http`. Finally, restart the Apache server.
 
 ### HTTP with a subpath
 
@@ -178,7 +178,7 @@ Make sure to set the Forgejo `ROOT_URL` configuration key to the URL _with_ the
 
 ### HTTPS
 
-When using a reverse proxy, it's usually easier to let the proxy handle HTTPS. It's easy to set up HTTPS on apache.
+When using a reverse proxy, it's usually easier to let the proxy handle HTTPS. It's easy to set up HTTPS on Apache.
 
 #### HTTPS with Certbot
 
@@ -277,9 +277,9 @@ A Unix socket has lower latency compared to TCP. When combined with HAProxy, it
 
 We assume that:
 
-- Redirection to SSL and the SSL frontend configuration remain unchanged from the TCP setup
-- you are running Forgejo as `git` user and HAProxy as `haproxy` user
-- the chroot environment is set to the directory `/var/lib/haproxy`
+- Redirection to SSL and the SSL frontend configuration remain unchanged from the TCP setup.
+- you are running Forgejo as `git` user and HAProxy as `haproxy` user.
+- the chroot environment is set to the directory `/var/lib/haproxy`.
 - you have included the following settings in the `server` stanza of Forgejo:
 
 ```ini
@@ -296,7 +296,7 @@ Now you need to create a directory which can be acceessed either by the chroot e
 install -o git -g haproxy -m 0770 -d /var/lib/haproxy/forgejo
 ```
 
-Finally you can add these blocks into your `haproxy.cfg`
+Finally, you can add these blocks into your `haproxy.cfg`.
 
 #### chroot
 

docs/admin/search-engines-indexation.md

@@ -6,7 +6,7 @@ origin_url: 'https://github.com/go-gitea/gitea/blob/e865de1e9d65dc09797d165a51c8
 
 ## Search engines indexation of your Forgejo installation
 
-By default your Forgejo installation will be indexed by search engines.
+By default, your Forgejo installation will be indexed by search engines.
 If you don't want your repository to be visible for search engines read further.
 
 ### Block search engines indexation using robots.txt

docs/admin/seek-assistance.md

@@ -43,6 +43,6 @@ origin_url: 'https://github.com/go-gitea/gitea/blob/e865de1e9d65dc09797d165a51c8
       ENABLE_PPROF = true
       ```
 
-   2. Trigger the bug, when Forgejo gets stuck, use curl or browser to visit: `http://127.0.0.1:6060/debug/pprof/goroutine?debug=1` (IP must be `127.0.0.1` and port must be `6060`).
+   2. Trigger the bug, and when Forgejo gets stuck, use curl or browser to visit: `http://127.0.0.1:6060/debug/pprof/goroutine?debug=1` (IP must be `127.0.0.1` and port must be `6060`).
    3. If you are using Docker, please use `docker exec -it <container-name> curl "http://127.0.0.1:6060/debug/pprof/goroutine?debug=1"`.
    4. Report the output (the stack trace doesn't contain sensitive data).

docs/admin/signing.md

@@ -52,8 +52,8 @@ MERGES = pubkey, twofa, basesigned, commitssigned
 
 There are three main options:
 
-- `none` - this prevents Forgejo from signing any commits
-- `default` - Forgejo will default to the key configured within `git config`
+- `none` - this prevents Forgejo from signing any commits.
+- `default` - Forgejo will default to the key configured within `git config`.
 - `KEYID` - Forgejo will sign commits with the GPG key with the ID
   `KEYID`. In this case you should provide a `SIGNING_NAME` and
   `SIGNING_EMAIL` to be displayed for this key.

docs/admin/storage.md

@@ -182,7 +182,7 @@ connect to a S3 compatible server:
 - `MINIO_LOCATION`: **us-east-1**: S3 location to create bucket.
 - `MINIO_USE_SSL`: **false**: S3 enabled ssl.
 - `MINIO_INSECURE_SKIP_VERIFY`: **false**: S3 skip SSL verification.
-- `MINIO_CHECKSUM_ALGORITHM`: Minio checksum algorithm: **default** (for MinIO, garage or AWS S3) or **md5** (for Cloudflare or Backblaze)
+- `MINIO_CHECKSUM_ALGORITHM`: Minio checksum algorithm: **default** (for MinIO, garage or AWS S3) or **md5** (for Cloudflare or Backblaze).
 
 When used in the `[storage]` section they apply to all
 subsystems. When used in the section specific to a subsystem (see the table in the introduction), they