Add markdownlint (#20512)

Add `markdownlint` linter and fix issues. Config is based on the one
from electron's repo with a few rules relaxed.

59 files changed, 833 insertions, 743 deletions

diff --git a/docs/content/doc/advanced/clone-filter.en-us.md b/docs/content/doc/advanced/clone-filter.en-us.md
index ba2fdf104c..58675d2e94 100644
--- a/docs/content/doc/advanced/clone-filter.en-us.md
+++ b/docs/content/doc/advanced/clone-filter.en-us.md
@@ -30,7 +30,6 @@ see Git version of the server.
 By default, clone filters are enabled, unless `DISABLE_PARTIAL_CLONE` under
 `[git]` is set to `true`.
 
-
 See [GitHub blog post: Get up to speed with partial clone](https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/)
 for common use cases of clone filters (blobless and treeless clones), and
 [GitLab docs for partial clone](https://docs.gitlab.com/ee/topics/git/partial_clone.html)
diff --git a/docs/content/doc/advanced/config-cheat-sheet.en-us.md b/docs/content/doc/advanced/config-cheat-sheet.en-us.md
index 4df104419a..31a294e1c9 100644
--- a/docs/content/doc/advanced/config-cheat-sheet.en-us.md
+++ b/docs/content/doc/advanced/config-cheat-sheet.en-us.md
@@ -130,9 +130,9 @@ Values containing `#` or `;` must be quoted using `` ` `` or `"""`.
   - `always`: Always sign
   - Options other than `never` and `always` can be combined as a comma separated list.
 - `DEFAULT_TRUST_MODEL`: **collaborator**: \[collaborator, committer, collaboratorcommitter\]: The default trust model used for verifying commits.
-   - `collaborator`: Trust signatures signed by keys of collaborators.
-   - `committer`: Trust signatures that match committers (This matches GitHub and will force Gitea signed commits to have Gitea as the committer).
-   - `collaboratorcommitter`: Trust signatures signed by keys of collaborators which match the committer.
+  - `collaborator`: Trust signatures signed by keys of collaborators.
+  - `committer`: Trust signatures that match committers (This matches GitHub and will force Gitea signed commits to have Gitea as the committer).
+  - `collaboratorcommitter`: Trust signatures signed by keys of collaborators which match the committer.
 - `WIKI`: **never**: \[never, pubkey, twofa, always, parentsigned\]: Sign commits to wiki.
 - `CRUD_ACTIONS`: **pubkey, twofa, parentsigned**: \[never, pubkey, twofa, parentsigned, always\]: Sign CRUD actions.
   - Options as above, with the addition of:
@@ -152,6 +152,7 @@ Values containing `#` or `;` must be quoted using `` ` `` or `"""`.
 Configuration for set the expected MIME type based on file extensions of downloadable files. Configuration presents in key-value pairs and file extensions starts with leading `.`.
 
 The following configuration set `Content-Type: application/vnd.android.package-archive` header when downloading files with `.apk` file extension.
+
 ```ini
 .apk=application/vnd.android.package-archive
 ```
@@ -248,11 +249,11 @@ The following configuration set `Content-Type: application/vnd.android.package-a
    Requests are then made as `%(ROOT_URL)s/static/css/index.css` and `https://cdn.example.com/css/index.css` respective.
    The static files are located in the `public/` directory of the Gitea source repository.
 - `HTTP_ADDR`: **0.0.0.0**: HTTP listen address.
-   - If `PROTOCOL` is set to `fcgi`, Gitea will listen for FastCGI requests on TCP socket
+  - If `PROTOCOL` is set to `fcgi`, Gitea will listen for FastCGI requests on TCP socket
      defined by `HTTP_ADDR` and `HTTP_PORT` configuration settings.
-   - If `PROTOCOL` is set to `http+unix` or `fcgi+unix`, this should be the name of the Unix socket file to use. Relative paths will be made absolute against the AppWorkPath.
+  - If `PROTOCOL` is set to `http+unix` or `fcgi+unix`, this should be the name of the Unix socket file to use. Relative paths will be made absolute against the AppWorkPath.
 - `HTTP_PORT`: **3000**: HTTP listen port.
-   - If `PROTOCOL` is set to `fcgi`, Gitea will listen for FastCGI requests on TCP socket
+  - If `PROTOCOL` is set to `fcgi`, Gitea will listen for FastCGI requests on TCP socket
      defined by `HTTP_ADDR` and `HTTP_PORT` configuration settings.
 - `UNIX_SOCKET_PERMISSION`: **666**: Permissions for the Unix socket.
 - `LOCAL_ROOT_URL`: **%(PROTOCOL)s://%(HTTP_ADDR)s:%(HTTP_PORT)s/**: Local
@@ -370,16 +371,16 @@ The following configuration set `Content-Type: application/vnd.android.package-a
   (e.g. `ALTER USER user SET SEARCH_PATH = schema_name,"$user",public;`).
 - `SSL_MODE`: **disable**: SSL/TLS encryption mode for connecting to the database. This option is only applied for PostgreSQL and MySQL.
   - Valid values for MySQL:
-     - `true`: Enable TLS with verification of the database server certificate against its root certificate. When selecting this option make sure that the root certificate required to validate the database server certificate (e.g. the CA certificate) is on the system certificate store of both the database and Gitea servers. See your system documentation for instructions on how to add a CA certificate to the certificate store.
-     - `false`: Disable TLS.
-     - `disable`: Alias for `false`, for compatibility with PostgreSQL.
-     - `skip-verify`: Enable TLS without database server certificate verification. Use this option if you have self-signed or invalid certificate on the database server.
-     - `prefer`: Enable TLS with fallback to non-TLS connection.
+    - `true`: Enable TLS with verification of the database server certificate against its root certificate. When selecting this option make sure that the root certificate required to validate the database server certificate (e.g. the CA certificate) is on the system certificate store of both the database and Gitea servers. See your system documentation for instructions on how to add a CA certificate to the certificate store.
+    - `false`: Disable TLS.
+    - `disable`: Alias for `false`, for compatibility with PostgreSQL.
+    - `skip-verify`: Enable TLS without database server certificate verification. Use this option if you have self-signed or invalid certificate on the database server.
+    - `prefer`: Enable TLS with fallback to non-TLS connection.
   - Valid values for PostgreSQL:
-     - `disable`: Disable TLS.
-     - `require`: Enable TLS without any verifications.
-     - `verify-ca`: Enable TLS with verification of the database server certificate against its root certificate.
-     - `verify-full`: Enable TLS and verify the database server name matches the given certificate in either the `Common Name` or `Subject Alternative Name` fields.
+    - `disable`: Disable TLS.
+    - `require`: Enable TLS without any verifications.
+    - `verify-ca`: Enable TLS with verification of the database server certificate against its root certificate.
+    - `verify-full`: Enable TLS and verify the database server name matches the given certificate in either the `Common Name` or `Subject Alternative Name` fields.
 - `SQLITE_TIMEOUT`: **500**: Query timeout for SQLite3 only.
 - `ITERATE_BUFFER_SIZE`: **50**: Internal buffer size for iterating.
 - `CHARSET`: **utf8mb4**: For MySQL only, either "utf8" or "utf8mb4". NOTICE: for "utf8mb4" you must use MySQL InnoDB > 5.6. Gitea is unable to check this.
@@ -509,11 +510,11 @@ Certain queues have defaults that override the defaults set in `[queue]` (this o
 - `CSRF_COOKIE_HTTP_ONLY`: **true**: Set false to allow JavaScript to read CSRF cookie.
 - `MIN_PASSWORD_LENGTH`: **6**: Minimum password length for new users.
 - `PASSWORD_COMPLEXITY`: **off**: Comma separated list of character classes required to pass minimum complexity. If left empty or no valid values are specified, checking is disabled (off):
-    - lower - use one or more lower latin characters
-    - upper - use one or more upper latin characters
-    - digit - use one or more digits
-    - spec - use one or more special characters as ``!"#$%&'()*+,-./:;<=>?@[\\]^_`{|}~``
-    - off - do not check password complexity
+  - lower - use one or more lower latin characters
+  - upper - use one or more upper latin characters
+  - digit - use one or more digits
+  - spec - use one or more special characters as ``!"#$%&'()*+,-./:;<=>?@[\\]^_`{|}~``
+  - off - do not check password complexity
 - `PASSWORD_CHECK_PWN`: **false**: Check [HaveIBeenPwned](https://haveibeenpwned.com/Passwords) to see if a password has been exposed.
 - `SUCCESSFUL_TOKENS_CACHE_SIZE`: **20**: Cache successful token hashes. API tokens are stored in the DB as pbkdf2 hashes however, this means that there is a potentially significant hashing load when there are multiple API operations. This cache will store the successfully hashed tokens in a LRU cache as a balance between performance and security.
 
@@ -535,18 +536,18 @@ Certain queues have defaults that override the defaults set in `[queue]` (this o
 
 ## OAuth2 Client (`oauth2_client`)
 
-- `REGISTER_EMAIL_CONFIRM`: *[service]* **REGISTER\_EMAIL\_CONFIRM**: Set this to enable or disable email confirmation of OAuth2 auto-registration. (Overwrites the REGISTER\_EMAIL\_CONFIRM setting of the `[service]` section)
+- `REGISTER_EMAIL_CONFIRM`: _[service]_ **REGISTER\_EMAIL\_CONFIRM**: Set this to enable or disable email confirmation of OAuth2 auto-registration. (Overwrites the REGISTER\_EMAIL\_CONFIRM setting of the `[service]` section)
 - `OPENID_CONNECT_SCOPES`: **\<empty\>**: List of additional openid connect scopes. (`openid` is implicitly added)
 - `ENABLE_AUTO_REGISTRATION`: **false**: Automatically create user accounts for new oauth2 users.
 - `USERNAME`: **nickname**: The source of the username for new oauth2 accounts:
-    - userid - use the userid / sub attribute
-    - nickname - use the nickname attribute
-    - email - use the username part of the email attribute
+  - userid - use the userid / sub attribute
+  - nickname - use the nickname attribute
+  - email - use the username part of the email attribute
 - `UPDATE_AVATAR`: **false**: Update avatar if available from oauth2 provider. Update will be performed on each login.
 - `ACCOUNT_LINKING`: **login**: How to handle if an account / email already exists:
-    - disabled - show an error
-    - login - show an account linking login
-    - auto - automatically link with the account (Please be aware that this will grant access to an existing account just because the same username or email is provided. You must make sure that this does not cause issues with your authentication providers.)
+  - disabled - show an error
+  - login - show an account linking login
+  - auto - automatically link with the account (Please be aware that this will grant access to an existing account just because the same username or email is provided. You must make sure that this does not cause issues with your authentication providers.)
 
 ## Service (`service`)
 
@@ -656,23 +657,23 @@ Define allowed algorithms and their minimum key length (use -1 to disable a type
 - `ENVELOPE_FROM`: **\<empty\>**: Address set as the From address on the SMTP mail envelope. Set to `<>` to send an empty address.
 - `USER`: **\<empty\>**: Username of mailing user (usually the sender's e-mail address).
 - `PASSWD`: **\<empty\>**: Password of mailing user.  Use \`your password\` for quoting if you use special characters in the password.
-   - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or `HOST=localhost`. See [Email Setup]({{< relref "doc/usage/email-setup.en-us.md" >}}) for more information.
+  - Please note: authentication is only supported when the SMTP server communication is encrypted with TLS (this can be via `STARTTLS`) or `HOST=localhost`. See [Email Setup]({{< relref "doc/usage/email-setup.en-us.md" >}}) for more information.
 - `SEND_AS_PLAIN_TEXT`: **false**: Send mails as plain text.
 - `SKIP_VERIFY`: **false**: Whether or not to skip verification of certificates; `true` to disable verification.
-   - **Warning:** This option is unsafe. Consider adding the certificate to the system trust store instead.
-   - **Note:** Gitea only supports SMTP with STARTTLS.
+  - **Warning:** This option is unsafe. Consider adding the certificate to the system trust store instead.
+  - **Note:** Gitea only supports SMTP with STARTTLS.
 - `USE_CERTIFICATE`: **false**: Use client certificate.
 - `CERT_FILE`: **custom/mailer/cert.pem**
 - `KEY_FILE`: **custom/mailer/key.pem**
 - `SUBJECT_PREFIX`: **\<empty\>**: Prefix to be placed before e-mail subject lines.
 - `MAILER_TYPE`: **smtp**: \[smtp, sendmail, dummy\]
-   - **smtp** Use SMTP to send mail
-   - **sendmail** Use the operating system's `sendmail` command instead of SMTP.
+  - **smtp** Use SMTP to send mail
+  - **sendmail** Use the operating system's `sendmail` command instead of SMTP.
    This is common on Linux systems.
-   - **dummy** Send email messages to the log as a testing phase.
-   - Note that enabling sendmail will ignore all other `mailer` settings except `ENABLED`,
+  - **dummy** Send email messages to the log as a testing phase.
+  - Note that enabling sendmail will ignore all other `mailer` settings except `ENABLED`,
      `FROM`, `SUBJECT_PREFIX` and `SENDMAIL_PATH`.
-   - Enabling dummy will ignore all settings except `ENABLED`, `SUBJECT_PREFIX` and `FROM`.
+  - Enabling dummy will ignore all settings except `ENABLED`, `SUBJECT_PREFIX` and `FROM`.
 - `SENDMAIL_PATH`: **sendmail**: The location of sendmail on the operating system (can be
    command or full path).
 - `SENDMAIL_ARGS`: **_empty_**: Specify any extra sendmail arguments. (NOTE: you should be aware that email addresses can look like options - if your `sendmail` command takes options you must set the option terminator `--`)
@@ -686,9 +687,9 @@ Define allowed algorithms and their minimum key length (use -1 to disable a type
 - `ADAPTER`: **memory**: Cache engine adapter, either `memory`, `redis`, `twoqueue` or `memcache`. (`twoqueue` represents a size limited LRU cache.)
 - `INTERVAL`: **60**: Garbage Collection interval (sec), for memory and twoqueue cache only.
 - `HOST`: **\<empty\>**: Connection string for `redis` and `memcache`. For `twoqueue` sets configuration for the queue.
-   - Redis: `redis://:macaron@127.0.0.1:6379/0?pool_size=100&idle_timeout=180s`
-   - Memcache: `127.0.0.1:9090;127.0.0.1:9091`
-   - TwoQueue LRU cache: `{"size":50000,"recent_ratio":0.25,"ghost_ratio":0.5}` or `50000` representing the maximum number of objects stored in the cache.
+  - Redis: `redis://:macaron@127.0.0.1:6379/0?pool_size=100&idle_timeout=180s`
+  - Memcache: `127.0.0.1:9090;127.0.0.1:9091`
+  - TwoQueue LRU cache: `{"size":50000,"recent_ratio":0.25,"ghost_ratio":0.5}` or `50000` representing the maximum number of objects stored in the cache.
 - `ITEM_TTL`: **16h**: Time to keep items in cache if not used, Setting it to -1 disables caching.
 
 ## Cache - LastCommitCache settings (`cache.last_commit`)
@@ -731,7 +732,6 @@ Define allowed algorithms and their minimum key length (use -1 to disable a type
   - image = default image will be used (which is set in `REPOSITORY_AVATAR_FALLBACK_IMAGE`)
 - `REPOSITORY_AVATAR_FALLBACK_IMAGE`: **/img/repo_default.png**: Image used as default repository avatar (if `REPOSITORY_AVATAR_FALLBACK` is set to image and none was uploaded)
 
-
 ## Project (`project`)
 
 Default templates for project boards:
@@ -766,11 +766,13 @@ Default templates for project boards:
 - `ENABLE_XORM_LOG`: **true**: Set whether to perform XORM logging. Please note SQL statement logging can be disabled by setting `LOG_SQL` to false in the `[database]` section.
 
 ### Router Log (`log`)
+
 - `DISABLE_ROUTER_LOG`: **false**: Mute printing of the router log.
 - `ROUTER`: **console**: The mode or name of the log the router should log to. (If you set this to `,` it will log to default Gitea logger.)
   NB: You must have `DISABLE_ROUTER_LOG` set to `false` for this option to take effect. Configure each mode in per mode log subsections `\[log.modename.router\]`.
 
 ### Access Log (`log`)
+
 - `ENABLE_ACCESS_LOG`: **false**: Creates an access.log in NCSA common log format, or as per the following template
 - `ACCESS`: **file**: Logging mode for the access logger, use a comma to separate values. Configure each mode in per mode log subsections `\[log.modename.access\]`. By default the file mode will log to `$ROOT_PATH/access.log`. (If you set this to `,` it will log to the default Gitea logger.)
 - `ACCESS_LOG_TEMPLATE`: **`{{.Ctx.RemoteAddr}} - {{.Identity}} {{.Start.Format "[02/Jan/2006:15:04:05 -0700]" }} "{{.Ctx.Req.Method}} {{.Ctx.Req.URL.RequestURI}} {{.Ctx.Req.Proto}}" {{.ResponseWriter.Status}} {{.ResponseWriter.Size}} "{{.Ctx.Req.Referer}}\" \"{{.Ctx.Req.UserAgent}}"`**: Sets the template used to create the access log.
@@ -828,9 +830,9 @@ Default templates for project boards:
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
 
 - `SCHEDULE` accept formats
-   - Full crontab specs, e.g. `* * * * * ?`
-   - Descriptors, e.g. `@midnight`, `@every 1h30m` ...
-   - See more: [cron decument](https://pkg.go.dev/github.com/gogs/cron@v0.0.0-20171120032916-9f6c956d3e14)
+  - Full crontab specs, e.g. `* * * * * ?`
+  - Descriptors, e.g. `@midnight`, `@every 1h30m` ...
+  - See more: [cron decument](https://pkg.go.dev/github.com/gogs/cron@v0.0.0-20171120032916-9f6c956d3e14)
 
 ### Basic cron tasks - enabled by default
 
@@ -887,6 +889,7 @@ Default templates for project boards:
 ### Extended cron tasks (not enabled by default)
 
 #### Cron - Garbage collect all repositories ('cron.git_gc_repos')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
@@ -895,36 +898,42 @@ Default templates for project boards:
 - `ARGS`: **\<empty\>**: Arguments for command `git gc`, e.g. `--aggressive --auto`. The default value is same with [git] -> GC_ARGS
 
 #### Cron - Update the '.ssh/authorized_keys' file with Gitea SSH keys ('cron.resync_all_sshkeys')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
 - `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
 
 #### Cron - Resynchronize pre-receive, update and post-receive hooks of all repositories ('cron.resync_all_hooks')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
 - `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
 
 #### Cron - Reinitialize all missing Git repositories for which records exist ('cron.reinit_missing_repos')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
 - `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
 
 #### Cron - Delete all repositories missing their Git files ('cron.delete_missing_repos')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
 - `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
 
 #### Cron -  Delete generated repository avatars ('cron.delete_generated_repository_avatars')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
 - `SCHEDULE`: **@every 72h**: Cron syntax for scheduling repository archive cleanup, e.g. `@every 1h`.
 
 #### Cron -  Delete all old actions from database ('cron.delete_old_actions')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NOTICE_ON_SUCCESS`: **false**: Set to true to switch on success notices.
@@ -932,6 +941,7 @@ Default templates for project boards:
 - `OLDER_THAN`: **@every 8760h**: any action older than this expression will be deleted from database, suggest using `8760h` (1 year) because that's the max length of heatmap.
 
 #### Cron -  Check for new Gitea versions ('cron.update_checker')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `ENABLE_SUCCESS_NOTICE`: **true**: Set to false to switch off success notices.
@@ -939,6 +949,7 @@ Default templates for project boards:
 - `HTTP_ENDPOINT`: **https://dl.gitea.io/gitea/version.json**: the endpoint that Gitea will check for newer versions
 
 #### Cron -  Delete all old system notices from database ('cron.delete_old_system_notices')
+
 - `ENABLED`: **false**: Enable service.
 - `RUN_AT_START`: **false**: Run tasks at start up time (if ENABLED).
 - `NO_SUCCESS_NOTICE`: **false**: Set to true to switch off success notices.
@@ -949,7 +960,7 @@ Default templates for project boards:
 
 - `PATH`: **""**: The path of Git executable. If empty, Gitea searches through the PATH environment.
 - `HOME_PATH`: **%(APP_DATA_PATH)/home**: The HOME directory for Git.
-	  This directory will be used to contain the `.gitconfig` and possible `.gnupg` directories that Gitea's git calls will use. If you can confirm Gitea is the only application running in this environment, you can set it to the normal home directory for Gitea user.
+   This directory will be used to contain the `.gitconfig` and possible `.gnupg` directories that Gitea's git calls will use. If you can confirm Gitea is the only application running in this environment, you can set it to the normal home directory for Gitea user.
 - `DISABLE_DIFF_HIGHLIGHT`: **false**: Disables highlight of added and removed changes.
 - `MAX_GIT_DIFF_LINES`: **1000**: Max number of lines allowed of a single file in diff view.
 - `MAX_GIT_DIFF_LINE_CHARACTERS`: **5000**: Max character count per line highlighted in diff view.
@@ -966,6 +977,7 @@ Default templates for project boards:
 - `DISABLE_PARTIAL_CLONE`: **false** Disable the usage of using partial clones for git.
 
 ## Git - Timeout settings (`git.timeout`)
+
 - `DEFAUlT`: **360**: Git operations default timeout seconds.
 - `MIGRATE`: **600**: Migrate external repositories timeout seconds.
 - `MIRROR`: **300**: Mirror external repositories timeout seconds.
@@ -1032,6 +1044,7 @@ IS_INPUT_FILE = false
   - iframe: Render the content in a separate standalone page and embed it into current page by iframe. The iframe is in sandbox mode with same-origin disabled, and the JS code are safely isolated from parent page.
 
 Two special environment variables are passed to the render command:
+
 - `GITEA_PREFIX_SRC`, which contains the current URL prefix in the `src` path tree. To be used as prefix for links.
 - `GITEA_PREFIX_RAW`, which contains the current URL prefix in the `raw` path tree. To be used as prefix for image paths.
 
@@ -1047,10 +1060,10 @@ REGEXP = ^\s*((math(\s+|$)|inline(\s+|$)|display(\s+|$)))+
 ALLOW_DATA_URI_IMAGES = true
 ```
 
- - `ELEMENT`: The element this policy applies to. Must be non-empty.
- - `ALLOW_ATTR`: The attribute this policy allows. Must be non-empty.
- - `REGEXP`: A regex to match the contents of the attribute against. Must be present but may be empty for unconditional whitelisting of this attribute.
- - `ALLOW_DATA_URI_IMAGES`: **false** Allow data uri images (`<img src="data:image/png;base64,..."/>`).
+- `ELEMENT`: The element this policy applies to. Must be non-empty.
+- `ALLOW_ATTR`: The attribute this policy allows. Must be non-empty.
+- `REGEXP`: A regex to match the contents of the attribute against. Must be present but may be empty for unconditional whitelisting of this attribute.
+- `ALLOW_DATA_URI_IMAGES`: **false** Allow data uri images (`<img src="data:image/png;base64,..."/>`).
 
 Multiple sanitisation rules can be defined by adding unique subsections, e.g. `[markup.sanitizer.TeX-2]`.
 To apply a sanitisation rules only for a specify external renderer they must use the renderer name, e.g. `[markup.sanitizer.asciidoc.rule-1]`.
@@ -1186,6 +1199,7 @@ is `data/repo-archive` and the default of `MINIO_BASE_PATH` is `repo-archive/`.
 - `PROXY_HOSTS`: **\<empty\>**: Comma separated list of host names requiring proxy. Glob patterns (*) are accepted; use ** to match all hosts.
 
 i.e.
+
 ```ini
 PROXY_ENABLED = true
 PROXY_URL = socks://127.0.0.1:1080
diff --git a/docs/content/doc/advanced/config-cheat-sheet.zh-cn.md b/docs/content/doc/advanced/config-cheat-sheet.zh-cn.md
index 33c693083d..c2dff2aeca 100644
--- a/docs/content/doc/advanced/config-cheat-sheet.zh-cn.md
+++ b/docs/content/doc/advanced/config-cheat-sheet.zh-cn.md
@@ -173,8 +173,8 @@ menu:
 - `ADAPTER`: **memory**: 缓存引擎，可以为 `memory`, `redis` 或 `memcache`。
 - `INTERVAL`: **60**: 只对内存缓存有效，GC间隔，单位秒。
 - `HOST`: **\<empty\>**: 针对redis和memcache有效，主机地址和端口。
-    - Redis: `network=tcp,addr=127.0.0.1:6379,password=macaron,db=0,pool_size=100,idle_timeout=180`
-    - Memache: `127.0.0.1:9090;127.0.0.1:9091`
+  - Redis: `network=tcp,addr=127.0.0.1:6379,password=macaron,db=0,pool_size=100,idle_timeout=180`
+  - Memache: `127.0.0.1:9090;127.0.0.1:9091`
 - `ITEM_TTL`: **16h**: 缓存项目失效时间，设置为 -1 则禁用缓存。
 
 ## Cache - LastCommitCache settings (`cache.last_commit`)
@@ -239,7 +239,6 @@ file -I test01.xls
 test01.xls: application/vnd.ms-excel; charset=binary
 ```
 
-
 ## Log (`log`)
 
 - `ROOT_PATH`: 日志文件根目录。
@@ -251,10 +250,9 @@ test01.xls: application/vnd.ms-excel; charset=binary
 - `ENABLED`: 是否在后台运行定期任务。
 - `RUN_AT_START`: 是否启动时自动运行。
 - `SCHEDULE` 所接受的格式
-   - 完整 crontab 控制, 例如 `* * * * * ?`
-   - 描述符, 例如 `@midnight`, `@every 1h30m` ...
-   - 更多细节参见 [cron api文档](https://pkg.go.dev/github.com/gogs/cron@v0.0.0-20171120032916-9f6c956d3e14)
-
+  - 完整 crontab 控制, 例如 `* * * * * ?`
+  - 描述符, 例如 `@midnight`, `@every 1h30m` ...
+  - 更多细节参见 [cron api文档](https://pkg.go.dev/github.com/gogs/cron@v0.0.0-20171120032916-9f6c956d3e14)
 
 ### Cron - Update Mirrors (`cron.update_mirrors`)
 
@@ -440,6 +438,7 @@ Repository archive 的存储配置。 如果 `STORAGE_TYPE` 为空，则此配�
 - `PROXY_HOSTS`: **\<empty\>**: 逗号分隔的多个需要代理的网址，支持 * 号匹配符号， ** 表示匹配所有网站
 
 i.e.
+
 ```ini
 PROXY_ENABLED = true
 PROXY_URL = socks://127.0.0.1:1080
diff --git a/docs/content/doc/advanced/customizing-gitea.en-us.md b/docs/content/doc/advanced/customizing-gitea.en-us.md
index 8f23fc3346..038ce16a8d 100644
--- a/docs/content/doc/advanced/customizing-gitea.en-us.md
+++ b/docs/content/doc/advanced/customizing-gitea.en-us.md
@@ -149,13 +149,13 @@ copy javascript files from https://gitea.com/davidsvantesson/plantuml-code-highl
 
 You can then add blocks like the following to your markdown:
 
-    ```plantuml
-        Alice -> Bob: Authentication Request
-        Bob --> Alice: Authentication Response
+```plantuml
+Alice -> Bob: Authentication Request
+Bob --> Alice: Authentication Response
 
-        Alice -> Bob: Another authentication Request
-        Alice <-- Bob: Another authentication Response
-    ```
+Alice -> Bob: Another authentication Request
+Alice <-- Bob: Another authentication Response
+```
 
 The script will detect tags with `class="language-plantuml"`, but you can change this by providing a second argument to `parsePlantumlCodeBlocks`.
 
diff --git a/docs/content/doc/advanced/environment-variables.zh-cn.md b/docs/content/doc/advanced/environment-variables.zh-cn.md
index 63ee4c6935..3de8dcfbc7 100644
--- a/docs/content/doc/advanced/environment-variables.zh-cn.md
+++ b/docs/content/doc/advanced/environment-variables.zh-cn.md
@@ -25,31 +25,31 @@ GITEA_CUSTOM=/home/gitea/custom ./gitea web
 
 因为 Gitea 使用 Go 语言编写，因此它使用了一些相关的 Go 的配置参数：
 
-  * `GOOS`
-  * `GOARCH`
-  * [`GOPATH`](https://golang.org/cmd/go/#hdr-GOPATH_environment_variable)
+* `GOOS`
+* `GOARCH`
+* [`GOPATH`](https://golang.org/cmd/go/#hdr-GOPATH_environment_variable)
 
 您可以在[官方文档](https://golang.org/cmd/go/#hdr-Environment_variables)中查阅这些配置参数的详细信息。
 
 ## Gitea 的文件目录
 
-  * `GITEA_WORK_DIR`：工作目录的绝对路径
-  * `GITEA_CUSTOM`：默认情况下 Gitea 使用默认目录 `GITEA_WORK_DIR`/custom，您可以使用这个参数来配置 *custom* 目录
-  * `GOGS_WORK_DIR`： 已废弃，请使用 `GITEA_WORK_DIR` 替代
-  * `GOGS_CUSTOM`： 已废弃，请使用 `GITEA_CUSTOM` 替代
+* `GITEA_WORK_DIR`：工作目录的绝对路径
+* `GITEA_CUSTOM`：默认情况下 Gitea 使用默认目录 `GITEA_WORK_DIR`/custom，您可以使用这个参数来配置 *custom* 目录
+* `GOGS_WORK_DIR`： 已废弃，请使用 `GITEA_WORK_DIR` 替代
+* `GOGS_CUSTOM`： 已废弃，请使用 `GITEA_CUSTOM` 替代
 
 ## 操作系统配置
 
-  * `USER`：Gitea 运行时使用的系统用户，它将作为一些 repository 的访问地址的一部分
-  * `USERNAME`： 如果没有配置 `USER`， Gitea 将使用 `USERNAME`
-  * `HOME`： 用户的 home 目录，在 Windows 中会使用 `USERPROFILE` 环境变量
+* `USER`：Gitea 运行时使用的系统用户，它将作为一些 repository 的访问地址的一部分
+* `USERNAME`： 如果没有配置 `USER`， Gitea 将使用 `USERNAME`
+* `HOME`： 用户的 home 目录，在 Windows 中会使用 `USERPROFILE` 环境变量
 
 ### 仅限于 Windows 的配置
 
-  * `USERPROFILE`： 用户的主目录，如果未配置则会使用 `HOMEDRIVE` + `HOMEPATH`
-  * `HOMEDRIVE`: 用于访问 home 目录的主驱动器路径（C盘）
-  * `HOMEPATH`：在指定主驱动器下的 home 目录相对路径
+* `USERPROFILE`： 用户的主目录，如果未配置则会使用 `HOMEDRIVE` + `HOMEPATH`
+* `HOMEDRIVE`: 用于访问 home 目录的主驱动器路径（C盘）
+* `HOMEPATH`：在指定主驱动器下的 home 目录相对路径
 
 ## Miscellaneous
 
-  * `SKIP_MINWINSVC`：如果设置为 1，在 Windows 上不会以 service 的形式运行。
+* `SKIP_MINWINSVC`：如果设置为 1，在 Windows 上不会以 service 的形式运行。
diff --git a/docs/content/doc/advanced/external-renderers.en-us.md b/docs/content/doc/advanced/external-renderers.en-us.md
index 34329408a1..4e5e72554d 100644
--- a/docs/content/doc/advanced/external-renderers.en-us.md
+++ b/docs/content/doc/advanced/external-renderers.en-us.md
@@ -127,6 +127,7 @@ ALLOW_ATTR = class
 ### Example: Office DOCX
 
 Display Office DOCX files with [`pandoc`](https://pandoc.org/):
+
 ```ini
 [markup.docx]
 ENABLED = true
@@ -138,6 +139,7 @@ ALLOW_DATA_URI_IMAGES = true
 ```
 
 The template file has the following content:
+
 ```
 $body$
 ```
@@ -145,6 +147,7 @@ $body$
 ### Example: Jupyter Notebook
 
 Display Jupyter Notebook files with [`nbconvert`](https://github.com/jupyter/nbconvert):
+
 ```ini
 [markup.jupyter]
 ENABLED = true
@@ -156,9 +159,11 @@ ALLOW_DATA_URI_IMAGES = true
 ```
 
 ## Customizing CSS
-The external renderer is specified in the .ini in the format `[markup.XXXXX]` and the HTML supplied by your external renderer will be wrapped in a `<div>` with classes `markup` and `XXXXX`. The `markup` class provides out of the box styling (as does `markdown` if `XXXXX` is `markdown`). Otherwise you can use these classes to specifically target the contents of your rendered HTML. 
+
+The external renderer is specified in the .ini in the format `[markup.XXXXX]` and the HTML supplied by your external renderer will be wrapped in a `<div>` with classes `markup` and `XXXXX`. The `markup` class provides out of the box styling (as does `markdown` if `XXXXX` is `markdown`). Otherwise you can use these classes to specifically target the contents of your rendered HTML.
 
 And so you could write some CSS:
+
 ```css
 .markup.XXXXX html {
   font-size: 100%;
@@ -184,6 +189,7 @@ And so you could write some CSS:
 ```
 
 Add your stylesheet to your custom directory e.g `custom/public/css/my-style-XXXXX.css` and import it using a custom header file `custom/templates/custom/header.tmpl`:
+
 ```html
 <link type="text/css" href="{{AppSubUrl}}/assets/css/my-style-XXXXX.css" />
 ```
diff --git a/docs/content/doc/advanced/mail-templates-us.md b/docs/content/doc/advanced/mail-templates-us.md
index e73bb01e29..bd419a617b 100644
--- a/docs/content/doc/advanced/mail-templates-us.md
+++ b/docs/content/doc/advanced/mail-templates-us.md
@@ -251,7 +251,7 @@ This template produces something along these lines:
 >
 > \_********************************\_********************************
 >
-> Mike, I think we should tone down the blues a little.  
+> Mike, I think we should tone down the blues a little.
 > \_********************************\_********************************
 >
 > [View it on Gitea](#).
diff --git a/docs/content/doc/advanced/protected-tags.en-us.md b/docs/content/doc/advanced/protected-tags.en-us.md
index 0ddbedd9a1..8ed2afc418 100644
--- a/docs/content/doc/advanced/protected-tags.en-us.md
+++ b/docs/content/doc/advanced/protected-tags.en-us.md
@@ -15,7 +15,7 @@ menu:
 
 # Protected tags
 
-Protected tags allow control over who has permission to create or update Git tags. Each rule allows you to match either an individual tag name, or use an appropriate pattern to control multiple tags at once. 
+Protected tags allow control over who has permission to create or update Git tags. Each rule allows you to match either an individual tag name, or use an appropriate pattern to control multiple tags at once.
 
 **Table of Contents**
 
diff --git a/docs/content/doc/advanced/repo-mirror.en-us.md b/docs/content/doc/advanced/repo-mirror.en-us.md
index bda5b0fa55..c1d794762a 100644
--- a/docs/content/doc/advanced/repo-mirror.en-us.md
+++ b/docs/content/doc/advanced/repo-mirror.en-us.md
@@ -37,7 +37,7 @@ For an existing remote repository, you can set up pull mirroring as follows:
 3. Enter a repository URL.
 4. If the repository needs authentication fill in your authentication information.
 5. Check the box **This repository will be a mirror**.
-5. Select **Migrate repository** to save the configuration.
+6. Select **Migrate repository** to save the configuration.
 
 The repository now gets mirrored periodically from the remote repository. You can force a sync by selecting **Synchronize Now** in the repository settings.
 
diff --git a/docs/content/doc/advanced/search-engines-indexation.en-us.md b/docs/content/doc/advanced/search-engines-indexation.en-us.md
index 5d5e4dab5a..ec367b74de 100644
--- a/docs/content/doc/advanced/search-engines-indexation.en-us.md
+++ b/docs/content/doc/advanced/search-engines-indexation.en-us.md
@@ -25,7 +25,6 @@ create a file called `robots.txt` in the [`custom` folder or `CustomPath`]({{< r
 
 Examples on how to configure the `robots.txt` can be found at [https://moz.com/learn/seo/robotstxt](https://moz.com/learn/seo/robotstxt).
 
-
 ```txt
 User-agent: *
 Disallow: /
diff --git a/docs/content/doc/advanced/third-party-tools.zh-cn.md b/docs/content/doc/advanced/third-party-tools.zh-cn.md
index d25bc400e4..e961e9ec1f 100644
--- a/docs/content/doc/advanced/third-party-tools.zh-cn.md
+++ b/docs/content/doc/advanced/third-party-tools.zh-cn.md
@@ -14,23 +14,26 @@ menu:
 ---
 
 # 第三方工具列表
+
 **注意:** 这些工具并没有经过Gitea的检验，在这里列出它们只是为了便捷.
 
 *此列表并不是完整的列表，可以随时咨询如何添加!*
 
 ### 持续集成
-[BuildKite 连接器](https://github.com/techknowlogick/gitea-buildkite-connector)  
-[Jenkins 插件](https://github.com/jenkinsci/gitea-plugin)  
-[Gitea搭配Drone](https://docs.drone.io/installation/gitea)
 
+[BuildKite 连接器](https://github.com/techknowlogick/gitea-buildkite-connector)
+[Jenkins 插件](https://github.com/jenkinsci/gitea-plugin)
+[Gitea搭配Drone](https://docs.drone.io/installation/gitea)
 
 ### 迁移
-[Gitea安装脚本](https://git.coolaj86.com/coolaj86/gitea-installer.sh)  
-[GitHub迁移](https://gitea.com/gitea/migrator)
 
+[Gitea安装脚本](https://git.coolaj86.com/coolaj86/gitea-installer.sh)
+[GitHub迁移](https://gitea.com/gitea/migrator)
 
 ### 移动端
+
 [安卓客户端GitNex](https://gitlab.com/mmarif4u/gitnex)
 
-###  编辑器扩展
- - [Gitea的Visual Studio扩展](https://github.com/maikebing/Gitea.VisualStudio)    从   [Visual Studio 扩展市场](https://marketplace.visualstudio.com/items?itemName=MysticBoy.GiteaExtensionforVisualStudio) 下载
+### 编辑器扩展
+
+- [Gitea的Visual Studio扩展](https://github.com/maikebing/Gitea.VisualStudio)    从   [Visual Studio 扩展市场](https://marketplace.visualstudio.com/items?itemName=MysticBoy.GiteaExtensionforVisualStudio) 下载
diff --git a/docs/content/doc/developers/api-usage.en-us.md b/docs/content/doc/developers/api-usage.en-us.md
index 57702a6ee8..dd2822e9f1 100644
--- a/docs/content/doc/developers/api-usage.en-us.md
+++ b/docs/content/doc/developers/api-usage.en-us.md
@@ -48,7 +48,6 @@ A new token can be generated with a `POST` request to
 Note that `/users/:name/tokens` is a special endpoint and requires you
 to authenticate using `BasicAuth` and a password, as follows:
 
-
 ```sh
 $ curl -XPOST -H "Content-Type: application/json"  -k -d '{"name":"test"}' -u username:password https://gitea.your.host/api/v1/users/<username>/tokens
 {"id":1,"name":"test","sha1":"9fcb1158165773dd010fca5f0cf7174316c3e37d","token_last_eight":"16c3e37d"}
diff --git a/docs/content/doc/developers/guidelines-backend.md b/docs/content/doc/developers/guidelines-backend.md
index 1248d41432..4280aa80fb 100644
--- a/docs/content/doc/developers/guidelines-backend.md
+++ b/docs/content/doc/developers/guidelines-backend.md
@@ -21,8 +21,8 @@ menu:
 
 ## Background
 
-Gitea uses Golang as the backend programming language. It uses many third-party packages and also write some itself. 
-For example, Gitea uses [Chi](https://github.com/go-chi/chi) as basic web framework. [Xorm](https://xorm.io) is an ORM framework that is used to interact with the database. 
+Gitea uses Golang as the backend programming language. It uses many third-party packages and also write some itself.
+For example, Gitea uses [Chi](https://github.com/go-chi/chi) as basic web framework. [Xorm](https://xorm.io) is an ORM framework that is used to interact with the database.
 So it's very important to manage these packages. Please take the below guidelines before you start to write backend code.
 
 ## Package Design Guideline
@@ -43,9 +43,9 @@ To maintain understandable code and avoid circular dependencies it is important
   - `modules/git`: Package to interactive with `Git` command line or Gogit package.
 - `public`: Compiled frontend files (javascript, images, css, etc.)
 - `routers`: Handling of server requests. As it uses other Gitea packages to serve the request, other packages (models, modules or services) must not depend on routers.
-  - `routers/api` Contains routers for `/api/v1` aims to handle RESTful API requests. 
-  - `routers/install` Could only respond when system is in INSTALL mode (INSTALL_LOCK=false). 
-  - `routers/private` will only be invoked by internal sub commands, especially `serv` and `hooks`. 
+  - `routers/api` Contains routers for `/api/v1` aims to handle RESTful API requests.
+  - `routers/install` Could only respond when system is in INSTALL mode (INSTALL_LOCK=false).
+  - `routers/private` will only be invoked by internal sub commands, especially `serv` and `hooks`.
   - `routers/web` will handle HTTP requests from web browsers or Git SMART HTTP protocols.
 - `services`: Support functions for common routing operations or command executions. Uses `models` and `modules` to handle the requests.
 - `templates`: Golang templates for generating the html output.
@@ -61,7 +61,7 @@ From left to right, left packages could depend on right packages, but right pack
 **NOTICE**
 
 Why do we need database transactions outside of `models`? And how?
-Some actions should allow for rollback when database record insertion/update/deletion failed. 
+Some actions should allow for rollback when database record insertion/update/deletion failed.
 So services must be allowed to create a database transaction. Here is some example,
 
 ```go
@@ -84,7 +84,7 @@ func CreateXXXX() error {\
 }
 ```
 
-You should **not** use `db.GetEngine(ctx)` in `services` directly, but just write a function under `models/`. 
+You should **not** use `db.GetEngine(ctx)` in `services` directly, but just write a function under `models/`.
 If the function will be used in the transaction, just let `context.Context` as the function's first parameter.
 
 ```go
diff --git a/docs/content/doc/developers/guidelines-frontend.md b/docs/content/doc/developers/guidelines-frontend.md
index 0fced64b14..87272d023f 100644
--- a/docs/content/doc/developers/guidelines-frontend.md
+++ b/docs/content/doc/developers/guidelines-frontend.md
@@ -26,6 +26,7 @@ Gitea uses [Less CSS](https://lesscss.org), [Fomantic-UI](https://fomantic-ui.co
 The HTML pages are rendered by [Go HTML Template](https://pkg.go.dev/html/template).
 
 The source files can be found in the following directories:
+
 * **Less styles:** `web_src/less/`
 * **JavaScript files:** `web_src/js/`
 * **Vue components:** `web_src/js/components/`
@@ -41,36 +42,37 @@ We recommend [Google HTML/CSS Style Guide](https://google.github.io/styleguide/h
 2. HTML ids and classes should use kebab-case.
 3. HTML ids and classes used in JavaScript should be unique for the whole project, and should contain 2-3 feature related keywords. We recommend to use the `js-` prefix for classes that are only used in JavaScript.
 4. jQuery events across different features could use their own namespaces if there are potential conflicts.
-5. CSS styling for classes provided by frameworks should not be overwritten. Always use new class-names with 2-3 feature related keywords to overwrite framework styles.  
+5. CSS styling for classes provided by frameworks should not be overwritten. Always use new class-names with 2-3 feature related keywords to overwrite framework styles.
 6. The backend can pass complex data to the frontend by using `ctx.PageData["myModuleData"] = map[]{}`
 7. Simple pages and SEO-related pages use Go HTML Template render to generate static Fomantic-UI HTML output. Complex pages can use Vue2 (or Vue3 in future).
 
-
 ### Framework Usage
 
 Mixing different frameworks together is discouraged, it makes the code difficult to be maintained.
 A JavaScript module should follow one major framework and follow the framework's best practice.
 
 Recommended implementations:
+
 * Vue + Vanilla JS
 * Fomantic-UI (jQuery)
 * Vanilla JS
 
 Discouraged implementations:
+
 * Vue + Fomantic-UI (jQuery)
 * jQuery + Vanilla JS
 
 To make UI consistent, Vue components can use Fomantic-UI CSS classes.
-Although mixing different frameworks is discouraged, 
-it should also work if the mixing is necessary and the code is well-designed and maintainable. 
+Although mixing different frameworks is discouraged,
+it should also work if the mixing is necessary and the code is well-designed and maintainable.
 
 ### `async` Functions
 
-Only mark a function as `async` if and only if there are `await` calls 
+Only mark a function as `async` if and only if there are `await` calls
 or `Promise` returns inside the function.
 
 It's not recommended to use `async` event listeners, which may lead to problems.
-The reason is that the code after await is executed outside the event dispatch. 
+The reason is that the code after await is executed outside the event dispatch.
 Reference: https://github.com/github/eslint-plugin-github/blob/main/docs/rules/async-preventdefault.md
 
 If we want to call an `async` function in a non-async context,
@@ -88,10 +90,9 @@ However, there are still some special cases, so the current guideline is:
   * `$.data()` can be used to bind some non-string data to elements in rare cases, but it is highly discouraged.
 
 * For new code:
-  * `node.dataset` should not be used, use `node.getAttribute` instead. 
+  * `node.dataset` should not be used, use `node.getAttribute` instead.
   * never bind any user data to a DOM node, use a suitable design pattern to describe the relation between node and data.
 
-
 ### Legacy Code
 
 A lot of legacy code already existed before this document's written. It's recommended to refactor legacy code to follow the guidelines.
diff --git a/docs/content/doc/developers/hacking-on-gitea.en-us.md b/docs/content/doc/developers/hacking-on-gitea.en-us.md
index 9d15f66dac..abefb1ca96 100644
--- a/docs/content/doc/developers/hacking-on-gitea.en-us.md
+++ b/docs/content/doc/developers/hacking-on-gitea.en-us.md
@@ -35,7 +35,7 @@ on the executable path. If you don't add the go bin directory to the
 executable path you will have to manage this yourself.
 
 **Note 2**: Go version {{< min-go-version >}} or higher is required.
-Gitea uses `gofmt` to format source code. However, the results of 
+Gitea uses `gofmt` to format source code. However, the results of
 `gofmt` can differ by the version of `go`. Therefore it is
 recommended to install the version of Go that our continuous integration is
 running. As of last update, the Go version should be {{< go-version >}}.
@@ -69,7 +69,7 @@ One of these three distributions of Make will run on Windows:
   - [32-bits version](http://www.equation.com/ftpdir/make/32/make.exe)
   - [64-bits version](http://www.equation.com/ftpdir/make/64/make.exe)
 - [MinGW-w64](https://www.mingw-w64.org) / [MSYS2](https://www.msys2.org/).
-  - MSYS2 is a collection of tools and libraries providing you with an easy-to-use environment for building, installing and running native Windows software, it includes MinGW-w64. 
+  - MSYS2 is a collection of tools and libraries providing you with an easy-to-use environment for building, installing and running native Windows software, it includes MinGW-w64.
   - In MingGW-w64, the binary is called `mingw32-make.exe` instead of `make.exe`. Add the `bin` folder to `PATH`.
   - In MSYS2, you can use `make` directly. See [MSYS2 Porting](https://www.msys2.org/wiki/Porting/).
   - To compile Gitea with CGO_ENABLED (eg: SQLite3), you might need to use [tdm-gcc](https://jmeubank.github.io/tdm-gcc/) instead of MSYS2 gcc, because MSYS2 gcc headers lack some Windows-only CRT functions like `_beginthread`.
@@ -212,7 +212,7 @@ SVG icons are built using the `make svg` target which compiles the icon sources
 
 ### Building the Logo
 
-The PNG and SVG versions of the Gitea logo are built from a single SVG source file `assets/logo.svg` using the `TAGS="gitea" make generate-images` target. To run it, Node.js and npm must be available. 
+The PNG and SVG versions of the Gitea logo are built from a single SVG source file `assets/logo.svg` using the `TAGS="gitea" make generate-images` target. To run it, Node.js and npm must be available.
 
 The same process can also be used to generate custom logo PNGs from a SVG source file by updating `assets/logo.svg` and running `make generate-images`. Omitting the `gitea` tag will update only the user-designated logo files.
 
@@ -312,7 +312,6 @@ may need adjustment to the local environment.
 Take a look at [`integrations/README.md`](https://github.com/go-gitea/gitea/blob/main/integrations/README.md)
 for more information and how to run a single test.
 
-
 ### Testing for a PR
 
 Our continuous integration will test the code passes its unit tests and that
@@ -345,13 +344,13 @@ for more information.
 
 ## GoLand
 
-Clicking the `Run Application` arrow on the function `func main()` in `/main.go` 
+Clicking the `Run Application` arrow on the function `func main()` in `/main.go`
 can quickly start a debuggable Gitea instance.
 
-The `Output Directory` in `Run/Debug Configuration` MUST be set to the 
-gitea project directory (which contains `main.go` and `go.mod`), 
-otherwise, the started instance's working directory is a GoLand's temporary directory 
-and prevents Gitea from loading dynamic resources (eg: templates) in a development environment.  
+The `Output Directory` in `Run/Debug Configuration` MUST be set to the
+gitea project directory (which contains `main.go` and `go.mod`),
+otherwise, the started instance's working directory is a GoLand's temporary directory
+and prevents Gitea from loading dynamic resources (eg: templates) in a development environment.
 
 To run unit tests with SQLite in GoLand, set `-tags sqlite,sqlite_unlock_notify`
 in `Go tool arguments` of `Run/Debug Configuration`.
diff --git a/docs/content/doc/developers/migrations.en-us.md b/docs/content/doc/developers/migrations.en-us.md
index b749f4f604..168af1f7fa 100644
--- a/docs/content/doc/developers/migrations.en-us.md
+++ b/docs/content/doc/developers/migrations.en-us.md
@@ -16,11 +16,11 @@ menu:
 # Migration Features
 
 Complete migrations were introduced in Gitea 1.9.0. It defines two interfaces to support migrating
-repository data from other Git host platforms to Gitea or, in the future, migrating Gitea data to other
-Git host platforms.  
+repository data from other Git host platforms to Gitea or, in the future, migrating Gitea data to other Git host platforms.
+
 Currently, migrations from GitHub, GitLab, and other Gitea instances are implemented.
 
-First of all, Gitea defines some standard objects in packages [modules/migration](https://github.com/go-gitea/gitea/tree/main/modules/migration).  
+First of all, Gitea defines some standard objects in packages [modules/migration](https://github.com/go-gitea/gitea/tree/main/modules/migration).
 They are `Repository`, `Milestone`, `Release`, `ReleaseAsset`, `Label`, `Issue`, `Comment`, `PullRequest`, `Reaction`, `Review`, `ReviewComment`.
 
 ## Downloader Interfaces
@@ -29,7 +29,7 @@ To migrate from a new Git host platform, there are two steps to be updated.
 
 - You should implement a `Downloader` which will be used to get repository information.
 - You should implement a `DownloaderFactory` which will be used to detect if the URL matches and create the above `Downloader`.
-   - You'll need to register the `DownloaderFactory` via `RegisterDownloaderFactory` on `init()`.
+  - You'll need to register the `DownloaderFactory` via `RegisterDownloaderFactory` on `init()`.
 
 You can find these interfaces in [downloader.go](https://github.com/go-gitea/gitea/blob/main/modules/migration/downloader.go).
 
diff --git a/docs/content/doc/developers/migrations.zh-tw.md b/docs/content/doc/developers/migrations.zh-tw.md
index 0d892cae91..173c01a464 100644
--- a/docs/content/doc/developers/migrations.zh-tw.md
+++ b/docs/content/doc/developers/migrations.zh-tw.md
@@ -18,7 +18,7 @@ menu:
 完整的遷移從 Gitea 1.9.0 開始提供。它定義了兩個介面用來從其它 Git 託管平臺遷移儲存庫資料到 Gitea，未來或許會提供遷移到其它 git 託管平臺。
 目前已實作了從 Github, Gitlab 和其它 Gitea 遷移資料。
 
-Gitea 定義了一些基本物件於套件 [modules/migration](https://github.com/go-gitea/gitea/tree/master/modules/migration)。  
+Gitea 定義了一些基本物件於套件 [modules/migration](https://github.com/go-gitea/gitea/tree/master/modules/migration)。
 分別是 `Repository`, `Milestone`, `Release`, `ReleaseAsset`, `Label`, `Issue`, `Comment`, `PullRequest`, `Reaction`, `Review`, `ReviewComment`。
 
 ## Downloader 介面
diff --git a/docs/content/doc/developers/oauth2-provider.md b/docs/content/doc/developers/oauth2-provider.md
index ce6e9aad8c..9e6ab11742 100644
--- a/docs/content/doc/developers/oauth2-provider.md
+++ b/docs/content/doc/developers/oauth2-provider.md
@@ -34,6 +34,7 @@ Gitea supports acting as an OAuth2 provider to allow third party applications to
 ## Supported OAuth2 Grants
 
 At the moment Gitea only supports the [**Authorization Code Grant**](https://tools.ietf.org/html/rfc6749#section-1.3.1) standard with additional support of the following extensions:
+
 - [Proof Key for Code Exchange (PKCE)](https://tools.ietf.org/html/rfc7636)
 - [OpenID Connect (OIDC)](https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowAuth)
 
diff --git a/docs/content/doc/features/authentication.en-us.md b/docs/content/doc/features/authentication.en-us.md
index 4b02679388..7d555d1dcc 100644
--- a/docs/content/doc/features/authentication.en-us.md
+++ b/docs/content/doc/features/authentication.en-us.md
@@ -203,7 +203,7 @@ configure this, set the fields below:
 
 - Force SMTPS
 
-  - SMTPS will be used by default for connections to port 465, if you wish to use SMTPS 
+  - SMTPS will be used by default for connections to port 465, if you wish to use SMTPS
   for other ports. Set this value.
   - Otherwise if the server provides the `STARTTLS` extension this will be used.
 
diff --git a/docs/content/doc/features/comparison.zh-cn.md b/docs/content/doc/features/comparison.zh-cn.md
index 98a50f5dc2..990a78aec0 100644
--- a/docs/content/doc/features/comparison.zh-cn.md
+++ b/docs/content/doc/features/comparison.zh-cn.md
@@ -109,7 +109,6 @@ _表格中的符号含义:_
 | Pull/Merge requests 模板             | ✓     | ✓    | ✓         | ✓         | ✓         | ✘         | ✘            |
 | 查看 Cherry-picking 的更改           | ✘     | ✘    | ✘         | ✓         | ✓         | ✘         | ✘            |
 
-
 #### 第三方集成
 
 | 特性                       | Gitea | Gogs | GitHub EE | GitLab CE | GitLab EE | BitBucket | RhodeCode CE |
diff --git a/docs/content/doc/features/localization.en-us.md b/docs/content/doc/features/localization.en-us.md
index a5b7a52f89..e57233a622 100644
--- a/docs/content/doc/features/localization.en-us.md
+++ b/docs/content/doc/features/localization.en-us.md
@@ -26,6 +26,8 @@ For changes to a **non-English** translation, refer to the Crowdin project above
 
 Any language listed in the above Crowdin project will be supported as long as 25% or more has been translated.
 
-After a translation has been accepted, it will be reflected in the main repository after the next Crowdin sync, which is generally after any PR is merged.  
-At the time of writing, this means that a changed translation may not appear until the following Gitea release.  
+After a translation has been accepted, it will be reflected in the main repository after the next Crowdin sync, which is generally after any PR is merged.
+
+At the time of writing, this means that a changed translation may not appear until the following Gitea release.
+
 If you use a bleeding edge build, it should appear as soon as you update after the change is synced.
diff --git a/docs/content/doc/features/localization.zh-tw.md b/docs/content/doc/features/localization.zh-tw.md
index e100063606..7bb3a6e6a2 100644
--- a/docs/content/doc/features/localization.zh-tw.md
+++ b/docs/content/doc/features/localization.zh-tw.md
@@ -25,6 +25,8 @@ menu:
 
 上述 Crowdin 專案中列出的語言在翻譯超過 25% 後將被支援。
 
-翻譯被認可後將在下次 Crowdin 同步後進入到主儲存庫，通常是在任何合併請求被合併之後。  
-這表示更改的翻譯要到下次 Gitea 發佈後才會出現。  
+翻譯被認可後將在下次 Crowdin 同步後進入到主儲存庫，通常是在任何合併請求被合併之後。
+
+這表示更改的翻譯要到下次 Gitea 發佈後才會出現。
+
 如果您使用的是最新建置，它將會在同步完成、您更新後出現。
diff --git a/docs/content/doc/help/faq.en-us.md b/docs/content/doc/help/faq.en-us.md
index 5783169fa9..17983da695 100644
--- a/docs/content/doc/help/faq.en-us.md
+++ b/docs/content/doc/help/faq.en-us.md
@@ -15,7 +15,8 @@ menu:
 
 # Frequently Asked Questions <!-- omit in toc -->
 
-This page contains some common questions and answers.  
+This page contains some common questions and answers.
+
 For more help resources, check all [Support Options]({{< relref "doc/help/seek-help.en-us.md" >}}).
 
 **Table of Contents**
@@ -24,14 +25,18 @@ For more help resources, check all [Support Options]({{< relref "doc/help/seek-h
 
 ## Difference between 1.x and 1.x.x downloads
 
-Version 1.7.x will be used for this example.  
+Version 1.7.x will be used for this example.
+
 **NOTE:** this example applies to Docker images as well!
 
-On our [downloads page](https://dl.gitea.io/gitea/) you will see a 1.7 directory, as well as directories for 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, and 1.7.6.  
-The 1.7 and 1.7.0 directories are **not** the same. The 1.7 directory is built on each merged commit to the [`release/v1.7`](https://github.com/go-gitea/gitea/tree/release/v1.7) branch.  
+On our [downloads page](https://dl.gitea.io/gitea/) you will see a 1.7 directory, as well as directories for 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, and 1.7.6.
+
+The 1.7 and 1.7.0 directories are **not** the same. The 1.7 directory is built on each merged commit to the [`release/v1.7`](https://github.com/go-gitea/gitea/tree/release/v1.7) branch.
+
 The 1.7.0 directory, however, is a build that was created when the [`v1.7.0`](https://github.com/go-gitea/gitea/releases/tag/v1.7.0) tag was created.
 
-This means that 1.x downloads will change as commits are merged to their respective branch (think of it as a separate "main" branch for each release).  
+This means that 1.x downloads will change as commits are merged to their respective branch (think of it as a separate "main" branch for each release).
+
 On the other hand, 1.x.x downloads should never change.
 
 ## How to migrate from Gogs/GitHub/etc. to Gitea
@@ -41,11 +46,14 @@ To migrate from Gogs to Gitea:
 - [Gogs version 0.9.146 or less]({{< relref "doc/upgrade/from-gogs.en-us.md" >}})
 - [Gogs version 0.11.46.0418](https://github.com/go-gitea/gitea/issues/4286)
 
-To migrate from GitHub to Gitea, you can use Gitea's built-in migration form.  
-In order to migrate items such as issues, pull requests, etc. you will need to input at least your username.  
+To migrate from GitHub to Gitea, you can use Gitea's built-in migration form.
+
+In order to migrate items such as issues, pull requests, etc. you will need to input at least your username.
+
 [Example (requires login)](https://try.gitea.io/repo/migrate)
 
-To migrate from GitLab to Gitea, you can use this non-affiliated tool:  
+To migrate from GitLab to Gitea, you can use this non-affiliated tool:
+
 https://github.com/loganinak/MigrateGitlabToGogs
 
 ## Where does Gitea store what file
@@ -83,9 +91,9 @@ There are a few places that could make this show incorrectly.
 
 If certain clone options aren't showing up (HTTP/S or SSH), the following options can be checked in your `app.ini`
 
-`DISABLE_HTTP_GIT`: if set to true, there will be no HTTP/HTTPS link  
-`DISABLE_SSH`: if set to true, there will be no SSH link  
-`SSH_EXPOSE_ANONYMOUS`: if set to false, SSH links will be hidden for anonymous users
+- `DISABLE_HTTP_GIT`: if set to true, there will be no HTTP/HTTPS link
+- `DISABLE_SSH`: if set to true, there will be no SSH link
+- `SSH_EXPOSE_ANONYMOUS`: if set to false, SSH links will be hidden for anonymous users
 
 ## File upload fails with: 413 Request Entity Too Large
 
@@ -95,19 +103,21 @@ See the [reverse proxy guide]({{< relref "doc/usage/reverse-proxies.en-us.md" >}
 
 ## Custom Templates not loading or working incorrectly
 
-Gitea's custom templates must be added to the correct location or Gitea will not find and use them.  
+Gitea's custom templates must be added to the correct location or Gitea will not find and use them.
+
 The correct path for the template(s) will be relative to the `CustomPath`
 
 1. To find `CustomPath`, look for Custom File Root Path in Site Administration -> Configuration
 
-- If that doesn't exist, you can try `echo $GITEA_CUSTOM`
+    If that doesn't exist, you can try `echo $GITEA_CUSTOM`
 
-2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-x-file)
+2. If you are still unable to find a path, the default can be [calculated above](#where-does-gitea-store-what-file)
 3. Once you have figured out the correct custom path, you can refer to the [customizing Gitea]({{< relref "doc/advanced/customizing-gitea.en-us.md" >}}) page to add your template to the correct location.
 
 ## Active user vs login prohibited user
 
-In Gitea, an "active" user refers to a user that has activated their account via email.  
+In Gitea, an "active" user refers to a user that has activated their account via email.
+
 A "login prohibited" user is a user that is not allowed to log in to Gitea anymore
 
 ## Setting up logging
@@ -116,8 +126,10 @@ A "login prohibited" user is a user that is not allowed to log in to Gitea anymo
 
 ## What is Swagger?
 
-[Swagger](https://swagger.io/) is what Gitea uses for its API.  
-All Gitea instances have the built-in API, though it can be disabled by setting `ENABLE_SWAGGER` to `false` in the `api` section of your `app.ini`  
+[Swagger](https://swagger.io/) is what Gitea uses for its API.
+
+All Gitea instances have the built-in API, though it can be disabled by setting `ENABLE_SWAGGER` to `false` in the `api` section of your `app.ini`
+
 For more information, refer to Gitea's [API docs]({{< relref "doc/developers/api-usage.en-us.md" >}})
 
 [Swagger Example](https://try.gitea.io/api/swagger)
@@ -139,7 +151,8 @@ You can configure `EMAIL_DOMAIN_WHITELIST` or `EMAIL_DOMAIN_BLOCKLIST` in your a
 
 ### Only allow/block certain OpenID providers
 
-You can configure `WHITELISTED_URIS` or `BLACKLISTED_URIS` under `[openid]` in your `app.ini`  
+You can configure `WHITELISTED_URIS` or `BLACKLISTED_URIS` under `[openid]` in your `app.ini`
+
 **NOTE:** whitelisted takes precedence, so if it is non-blank then blacklisted is ignored
 
 ### Issue only users
@@ -163,38 +176,48 @@ Use [Fail2Ban]({{< relref "doc/usage/fail2ban-setup.en-us.md" >}}) to monitor an
 Gitea supports three official themes right now, `gitea` (light), `arc-green` (dark), and `auto` (automatically switches between the previous two depending on operating system settings).
 To add your own theme, currently the only way is to provide a complete theme (not just color overrides)
 
-As an example, let's say our theme is `arc-blue` (this is a real theme, and can be found [in this issue](https://github.com/go-gitea/gitea/issues/6011))  
-Name the `.css` file `theme-arc-blue.css` and add it to your custom folder in `custom/public/css`  
+As an example, let's say our theme is `arc-blue` (this is a real theme, and can be found [in this issue](https://github.com/go-gitea/gitea/issues/6011))
+
+Name the `.css` file `theme-arc-blue.css` and add it to your custom folder in `custom/public/css`
+
 Allow users to use it by adding `arc-blue` to the list of `THEMES` in your `app.ini`
 
 ## SSHD vs built-in SSH
 
-SSHD is the built-in SSH server on most Unix systems.  
+SSHD is the built-in SSH server on most Unix systems.
+
 Gitea also provides its own SSH server, for usage when SSHD is not available.
 
 ## Gitea is running slow
 
-The most common culprit for this is loading federated avatars.  
-This can be turned off by setting `ENABLE_FEDERATED_AVATAR` to `false` in your `app.ini`  
+The most common culprit for this is loading federated avatars.
+
+This can be turned off by setting `ENABLE_FEDERATED_AVATAR` to `false` in your `app.ini`
+
 Another option that may need to be changed is setting `DISABLE_GRAVATAR` to `true` in your `app.ini`
 
 ## Can't create repositories/files
 
-Make sure that Gitea has sufficient permissions to write to its home directory and data directory.  
-See [AppDataPath and RepoRootPath](#where-does-gitea-store-x-file)
+Make sure that Gitea has sufficient permissions to write to its home directory and data directory.
+
+See [AppDataPath and RepoRootPath](#where-does-gitea-store-what-file)
 
 **Note for Arch users:** At the time of writing this, there is an issue with the Arch package's systemd file including this line:
-`ReadWritePaths=/etc/gitea/app.ini`  
+
+`ReadWritePaths=/etc/gitea/app.ini`
+
 Which makes all other paths non-writeable to Gitea.
 
 ## Translation is incorrect/how to add more translations
 
-Our translations are currently crowd-sourced on our [Crowdin project](https://crowdin.com/project/gitea)  
+Our translations are currently crowd-sourced on our [Crowdin project](https://crowdin.com/project/gitea)
+
 Whether you want to change a translation or add a new one, it will need to be there as all translations are overwritten in our CI via the Crowdin integration.
 
 ## Hooks aren't running
 
-If Gitea is not running hooks, a common cause is incorrect setup of SSH keys.  
+If Gitea is not running hooks, a common cause is incorrect setup of SSH keys.
+
 See [SSH Issues](#ssh-issues) for more information.
 
 You can also try logging into the administration panel and running the `Resynchronize pre-receive, update and post-receive hooks of all repositories.` option.
@@ -203,7 +226,8 @@ You can also try logging into the administration panel and running the `Resynchr
 
 If you cannot reach repositories over `ssh`, but `https` works fine, consider looking into the following.
 
-First, make sure you can access Gitea via SSH.  
+First, make sure you can access Gitea via SSH.
+
 `ssh git@myremote.example`
 
 If the connection is successful, you should receive an error message like the following:
@@ -236,7 +260,8 @@ following things:
 - On the server:
   - Make sure the repository exists and is correctly named.
   - Check the permissions of the `.ssh` directory in the system user's home directory.
-  - Verify that the correct public keys are added to `.ssh/authorized_keys`.  
+  - Verify that the correct public keys are added to `.ssh/authorized_keys`.
+
     Try to run `Rewrite '.ssh/authorized_keys' file (for Gitea SSH keys)` on the
     Gitea admin panel.
   - Read Gitea logs.
@@ -289,7 +314,8 @@ Check that you have proper access to the repository
 error: failed to push some refs to '<GIT_REPO_URL>'
 ```
 
-Check the value of `LFS_HTTP_AUTH_EXPIRY` in your `app.ini` file.  
+Check the value of `LFS_HTTP_AUTH_EXPIRY` in your `app.ini` file.
+
 By default, your LFS token will expire after 20 minutes. If you have a slow connection or a large file (or both), it may not finish uploading within the time limit.
 
 You may want to set this value to `60m` or `120m`.
@@ -306,17 +332,21 @@ There is no setting for password resets. It is enabled when a [mail service]({{<
 
 - As an **admin**, you can change any user's password (and optionally force them to change it on next login)...
   - By navigating to your `Site Administration -> User Accounts` page and editing a user.
-  - By using the [admin CLI commands]({{< relref "doc/usage/command-line.en-us.md#admin" >}}).  
+  - By using the [admin CLI commands]({{< relref "doc/usage/command-line.en-us.md#admin" >}}).
+
     Keep in mind most commands will also need a [global flag]({{< relref "doc/usage/command-line.en-us.md#global-options" >}}) to point the CLI at the correct configuration.
 - As a **user** you can change it...
   - In your account `Settings -> Account` page (this method **requires** you to know your current password).
-  - By using the `Forgot Password` link.  
+  - By using the `Forgot Password` link.
+
     If the `Forgot Password/Account Recovery` page is disabled, please contact your administrator to configure a [mail service]({{< relref "doc/usage/email-setup.en-us.md" >}}).
 
 ## Why is my markdown broken
 
-In Gitea version `1.11` we moved to [goldmark](https://github.com/yuin/goldmark) for markdown rendering, which is [CommonMark](https://commonmark.org/) compliant.  
-If you have markdown that worked as you expected prior to version `1.11` and after upgrading it's not working anymore, please look through the CommonMark spec to see whether the problem is due to a bug or non-compliant syntax.  
+In Gitea version `1.11` we moved to [goldmark](https://github.com/yuin/goldmark) for markdown rendering, which is [CommonMark](https://commonmark.org/) compliant.
+
+If you have markdown that worked as you expected prior to version `1.11` and after upgrading it's not working anymore, please look through the CommonMark spec to see whether the problem is due to a bug or non-compliant syntax.
+
 If it is the latter, _usually_ there is a compliant alternative listed in the spec.
 
 ## Upgrade errors with MySQL
@@ -332,8 +362,10 @@ is too small. Gitea requires that the `ROWFORMAT` for its tables is `DYNAMIC`.
 
 If you are receiving an error line containing `Error 1071: Specified key was too long; max key length is 1000 bytes...`
 then you are attempting to run Gitea on tables which use the ISAM engine. While this may have worked by chance in previous versions of Gitea, it has never been officially supported and
-you must use InnoDB. You should run `ALTER TABLE table_name ENGINE=InnoDB;` for each table in the database.  
+you must use InnoDB. You should run `ALTER TABLE table_name ENGINE=InnoDB;` for each table in the database.
+
 If you are using MySQL 5, another possible fix is
+
 ```mysql
 SET GLOBAL innodb_file_format=Barracuda;
 SET GLOBAL innodb_file_per_table=1;
@@ -404,8 +436,8 @@ gitea doctor recreate-table
 
 It is highly recommended to back-up your database before running these commands.
 
-
 ## Why are tabs/indents wrong when viewing files
 
-If you are using Cloudflare, turn off the auto-minify option in the dashboard.  
+If you are using Cloudflare, turn off the auto-minify option in the dashboard.
+
 `Speed` -> `Optimization` -> Uncheck `HTML` within the `Auto-Minify` settings.
diff --git a/docs/content/doc/help/seek-help.en-us.md b/docs/content/doc/help/seek-help.en-us.md
index f1a93eacea..fe898e34b9 100644
--- a/docs/content/doc/help/seek-help.en-us.md
+++ b/docs/content/doc/help/seek-help.en-us.md
@@ -22,9 +22,10 @@ menu:
 
 1. Your `app.ini` (with any sensitive data scrubbed as necessary).
 2. The Gitea logs, and any other appropriate log files for the situation.
-    * The logs are likely to be outputted to console. If you need to collect logs from files, 
+    - The logs are likely to be outputted to console. If you need to collect logs from files,
       you could copy the following config into your `app.ini` (remove all other `[log]` sections),
       then you can find the `*.log` files in Gitea's log directory (default: `%(GITEA_WORK_DIR)/log`).
+
     ```ini
     ; To show all SQL logs, you can also set LOG_SQL=true in the [database] section 
     [log]
@@ -38,17 +39,20 @@ menu:
     FILE_NAME=router.log
     [log.file.xorm]
     FILE_NAME=xorm.log
-    ``` 
+    ```
+
 3. Any error messages you are seeing.
 4. When possible, try to replicate the issue on [try.gitea.io](https://try.gitea.io) and include steps so that others can reproduce the issue.
-    * This will greatly improve the chance that the root of the issue can be quickly discovered and resolved.
+    - This will greatly improve the chance that the root of the issue can be quickly discovered and resolved.
 5. If you meet slow/hanging/deadlock problems, please report the stack trace when the problem occurs:
     1. Enable pprof in `app.ini` and restart Gitea
-    ```ini
-    [server]
-    ENABLE_PPROF = true
-    ```
-    2. Trigger the bug, when Gitea 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`). 
+
+        ```ini
+        [server]
+        ENABLE_PPROF = true
+        ```
+
+    2. Trigger the bug, when Gitea 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)
 
diff --git a/docs/content/doc/help/seek-help.zh-tw.md b/docs/content/doc/help/seek-help.zh-tw.md
index 3d45e6c3b2..f9107a026b 100644
--- a/docs/content/doc/help/seek-help.zh-tw.md
+++ b/docs/content/doc/help/seek-help.zh-tw.md
@@ -22,10 +22,10 @@ menu:
 
 1. 您的 `app.ini` (必要時清除掉任何機密資訊)
 2. `gitea.log` (以及任何有關的日誌檔案)
-    * 例：如果錯誤和資料庫相關，提供 `xorm.log` 可能會有幫助
+    - 例：如果錯誤和資料庫相關，提供 `xorm.log` 可能會有幫助
 3. 您看到的任何錯誤訊息
 4. 儘可能地在 [try.gitea.io](https://try.gitea.io) 觸發您的問題並記下步驟，以便其他人能重現那個問題。
-    * 這將讓我們更有機會快速地找出問題的根源並解決它。
+    - 這將讓我們更有機會快速地找出問題的根源並解決它。
 5. 堆棧跟踪，[請參考英文文檔](https://docs.gitea.io/en-us/seek-help/)
 
 ## 錯誤回報
diff --git a/docs/content/doc/installation/database-preparation.en-us.md b/docs/content/doc/installation/database-preparation.en-us.md
index 13a215d814..b8ad5d6859 100644
--- a/docs/content/doc/installation/database-preparation.en-us.md
+++ b/docs/content/doc/installation/database-preparation.en-us.md
@@ -27,13 +27,13 @@ Note: All steps below requires that the database engine of your choice is instal
 
 ## MySQL
 
-1.  For remote database setup, you will need to make MySQL listen to your IP address. Edit `bind-address` option on `/etc/mysql/my.cnf` on database instance to:
+1. For remote database setup, you will need to make MySQL listen to your IP address. Edit `bind-address` option on `/etc/mysql/my.cnf` on database instance to:
 
     ```ini
     bind-address = 203.0.113.3
     ```
 
-2.  On database instance, login to database console as root:
+2. On database instance, login to database console as root:
 
     ```
     mysql -u root -p
@@ -41,7 +41,7 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Enter the password as prompted.
 
-3.  Create database user which will be used by Gitea, authenticated by password. This example uses `'gitea'` as password. Please use a secure password for your instance.
+3. Create database user which will be used by Gitea, authenticated by password. This example uses `'gitea'` as password. Please use a secure password for your instance.
 
     For local database:
 
@@ -61,7 +61,7 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Replace username and password above as appropriate.
 
-4.  Create database with UTF-8 charset and collation. Make sure to use `utf8mb4` charset instead of `utf8` as the former supports all Unicode characters (including emojis) beyond _Basic Multilingual Plane_. Also, collation chosen depending on your expected content. When in doubt, use either `unicode_ci` or `general_ci`.
+4. Create database with UTF-8 charset and collation. Make sure to use `utf8mb4` charset instead of `utf8` as the former supports all Unicode characters (including emojis) beyond _Basic Multilingual Plane_. Also, collation chosen depending on your expected content. When in doubt, use either `unicode_ci` or `general_ci`.
 
     ```sql
     CREATE DATABASE giteadb CHARACTER SET 'utf8mb4' COLLATE 'utf8mb4_unicode_ci';
@@ -69,7 +69,7 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Replace database name as appropriate.
 
-5.  Grant all privileges on the database to database user created above.
+5. Grant all privileges on the database to database user created above.
 
     For local database:
 
@@ -85,9 +85,9 @@ Note: All steps below requires that the database engine of your choice is instal
     FLUSH PRIVILEGES;
     ```
 
-6.  Quit from database console by `exit`.
+6. Quit from database console by `exit`.
 
-7.  On your Gitea server, test connection to the database:
+7. On your Gitea server, test connection to the database:
 
     ```
     mysql -u gitea -h 203.0.113.3 -p giteadb
@@ -99,13 +99,13 @@ Note: All steps below requires that the database engine of your choice is instal
 
 ## PostgreSQL
 
-1.  For remote database setup, configure PostgreSQL on database instance to listen to your IP address by editing `listen_addresses` on `postgresql.conf` to:
+1. For remote database setup, configure PostgreSQL on database instance to listen to your IP address by editing `listen_addresses` on `postgresql.conf` to:
 
     ```ini
     listen_addresses = 'localhost, 203.0.113.3'
     ```
 
-2.  PostgreSQL uses `md5` challenge-response encryption scheme for password authentication by default. Nowadays this scheme is not considered secure anymore. Use SCRAM-SHA-256 scheme instead by editing the `postgresql.conf` configuration file on the database server to:
+2. PostgreSQL uses `md5` challenge-response encryption scheme for password authentication by default. Nowadays this scheme is not considered secure anymore. Use SCRAM-SHA-256 scheme instead by editing the `postgresql.conf` configuration file on the database server to:
 
     ```ini
     password_encryption = scram-sha-256
@@ -113,13 +113,13 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Restart PostgreSQL to apply the setting.
 
-3.  On the database server, login to the database console as superuser:
+3. On the database server, login to the database console as superuser:
 
     ```
     su -c "psql" - postgres
     ```
 
-4.  Create database user (role in PostgreSQL terms) with login privilege and password. Please use a secure, strong password instead of `'gitea'` below:
+4. Create database user (role in PostgreSQL terms) with login privilege and password. Please use a secure, strong password instead of `'gitea'` below:
 
     ```sql
     CREATE ROLE gitea WITH LOGIN PASSWORD 'gitea';
@@ -127,7 +127,7 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Replace username and password as appropriate.
 
-5.  Create database with UTF-8 charset and owned by the database user created earlier. Any `libc` collations can be specified with `LC_COLLATE` and `LC_CTYPE` parameter, depending on expected content:
+5. Create database with UTF-8 charset and owned by the database user created earlier. Any `libc` collations can be specified with `LC_COLLATE` and `LC_CTYPE` parameter, depending on expected content:
 
     ```sql
     CREATE DATABASE giteadb WITH OWNER gitea TEMPLATE template0 ENCODING UTF8 LC_COLLATE 'en_US.UTF-8' LC_CTYPE 'en_US.UTF-8';
@@ -135,7 +135,7 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Replace database name as appropriate.
 
-6.  Allow the database user to access the database created above by adding the following authentication rule to `pg_hba.conf`.
+6. Allow the database user to access the database created above by adding the following authentication rule to `pg_hba.conf`.
 
     For local database:
 
@@ -155,7 +155,7 @@ Note: All steps below requires that the database engine of your choice is instal
 
     Restart PostgreSQL to apply new authentication rules.
 
-7.  On your Gitea server, test connection to the database.
+7. On your Gitea server, test connection to the database.
 
     For local database:
 
@@ -188,13 +188,13 @@ If the communication between Gitea and your database instance is performed throu
 
 The PostgreSQL driver used by Gitea supports two-way TLS. In two-way TLS, both database client and server authenticate each other by sending their respective certificates to their respective opposite for validation. In other words, the server verifies client certificate, and the client verifies server certificate.
 
-1.  On the server with the database instance, place the following credentials:
+1. On the server with the database instance, place the following credentials:
 
     - `/path/to/postgresql.crt`: Database instance certificate
     - `/path/to/postgresql.key`: Database instance private key
     - `/path/to/root.crt`: CA certificate chain to validate client certificates
 
-2.  Add following options to `postgresql.conf`:
+2. Add following options to `postgresql.conf`:
 
     ```ini
     ssl = on
@@ -204,14 +204,14 @@ The PostgreSQL driver used by Gitea supports two-way TLS. In two-way TLS, both d
     ssl_min_protocol_version = 'TLSv1.2'
     ```
 
-3.  Adjust credentials ownership and permission, as required by PostgreSQL:
+3. Adjust credentials ownership and permission, as required by PostgreSQL:
 
     ```
     chown postgres:postgres /path/to/root.crt /path/to/postgresql.crt /path/to/postgresql.key
     chmod 0600 /path/to/root.crt /path/to/postgresql.crt /path/to/postgresql.key
     ```
 
-4.  Edit `pg_hba.conf` rule to only allow Gitea database user to connect over SSL, and to require client certificate verification.
+4. Edit `pg_hba.conf` rule to only allow Gitea database user to connect over SSL, and to require client certificate verification.
 
     For PostgreSQL 12:
 
@@ -227,9 +227,9 @@ The PostgreSQL driver used by Gitea supports two-way TLS. In two-way TLS, both d
 
     Replace database name, user, and IP address of Gitea instance as appropriate.
 
-5.  Restart PostgreSQL to apply configurations above.
+5. Restart PostgreSQL to apply configurations above.
 
-6.  On the server running the Gitea instance, place the following credentials under the home directory of the user who runs Gitea (e.g. `git`):
+6. On the server running the Gitea instance, place the following credentials under the home directory of the user who runs Gitea (e.g. `git`):
 
     - `~/.postgresql/postgresql.crt`: Database client certificate
     - `~/.postgresql/postgresql.key`: Database client private key
@@ -237,14 +237,14 @@ The PostgreSQL driver used by Gitea supports two-way TLS. In two-way TLS, both d
 
     Note: Those file names above are hardcoded in PostgreSQL and it is not possible to change them.
 
-7.  Adjust credentials, ownership and permission as required:
+7. Adjust credentials, ownership and permission as required:
 
     ```
     chown git:git ~/.postgresql/postgresql.crt ~/.postgresql/postgresql.key ~/.postgresql/root.crt
     chown 0600 ~/.postgresql/postgresql.crt ~/.postgresql/postgresql.key ~/.postgresql/root.crt
     ```
 
-8.  Test the connection to the database:
+8. Test the connection to the database:
 
     ```
     psql "postgres://gitea@example.db/giteadb?sslmode=verify-full"
@@ -258,13 +258,13 @@ While the MySQL driver used by Gitea also supports two-way TLS, Gitea currently
 
 In one-way TLS, the database client verifies the certificate sent from server during the connection handshake, and the server assumes that the connected client is legitimate, since client certificate verification doesn't take place.
 
-1.  On the database instance, place the following credentials:
+1. On the database instance, place the following credentials:
 
     - `/path/to/mysql.crt`: Database instance certificate
     - `/path/to/mysql.key`: Database instance key
     - `/path/to/ca.crt`: CA certificate chain. This file isn't used on one-way TLS, but is used to validate client certificates on two-way TLS.
 
-2.  Add following options to `my.cnf`:
+2. Add following options to `my.cnf`:
 
     ```ini
     [mysqld]
@@ -274,16 +274,16 @@ In one-way TLS, the database client verifies the certificate sent from server du
     tls-version = TLSv1.2,TLSv1.3
     ```
 
-3.  Adjust credentials ownership and permission:
+3. Adjust credentials ownership and permission:
 
     ```
     chown mysql:mysql /path/to/ca.crt /path/to/mysql.crt /path/to/mysql.key
     chmod 0600 /path/to/ca.crt /path/to/mysql.crt /path/to/mysql.key
     ```
 
-4.  Restart MySQL to apply the setting.
+4. Restart MySQL to apply the setting.
 
-5.  The database user for Gitea may have been created earlier, but it would authenticate only against the IP addresses of the server running Gitea. To authenticate against its domain name, recreate the user, and this time also set it to require TLS for connecting to the database:
+5. The database user for Gitea may have been created earlier, but it would authenticate only against the IP addresses of the server running Gitea. To authenticate against its domain name, recreate the user, and this time also set it to require TLS for connecting to the database:
 
     ```sql
     DROP USER 'gitea'@'192.0.2.10';
@@ -294,9 +294,9 @@ In one-way TLS, the database client verifies the certificate sent from server du
 
     Replace database user name, password, and Gitea instance domain as appropriate.
 
-6.  Make sure that the CA certificate chain required to validate the database server certificate is on the system certificate store of both the database and Gitea servers. Consult your system documentation for instructions on adding a CA certificate to the certificate store.
+6. Make sure that the CA certificate chain required to validate the database server certificate is on the system certificate store of both the database and Gitea servers. Consult your system documentation for instructions on adding a CA certificate to the certificate store.
 
-7.  On the server running Gitea, test connection to the database:
+7. On the server running Gitea, test connection to the database:
 
     ```
     mysql -u gitea -h example.db -p --ssl
diff --git a/docs/content/doc/installation/from-binary.en-us.md b/docs/content/doc/installation/from-binary.en-us.md
index c598317b6e..91a6b2a9d6 100644
--- a/docs/content/doc/installation/from-binary.en-us.md
+++ b/docs/content/doc/installation/from-binary.en-us.md
@@ -32,6 +32,7 @@ chmod +x gitea
 ```
 
 ## Verify GPG signature
+
 Gitea signs all binaries with a [GPG key](https://keys.openpgp.org/search?q=teabot%40gitea.io) to prevent against unwanted modification of binaries.
 To validate the binary, download the signature file which ends in `.asc` for the binary you downloaded and use the GPG command line tool.
 
@@ -89,11 +90,11 @@ chmod 640 /etc/gitea/app.ini
 
 If you don't want the web installer to be able to write to the config file, it is possible to make the config file read-only for the Gitea user (owner/group `root:git`, mode `0640`) however you will need to edit your config file manually to:
 
- * Set `INSTALL_LOCK= true`,
- * Ensure all database configuration details are set correctly 
- * Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.)
- * Ensure that any other secret keys you need are set.
- 
+* Set `INSTALL_LOCK= true`,
+* Ensure all database configuration details are set correctly
+* Ensure that the `SECRET_KEY` and `INTERNAL_TOKEN` values are set. (You may want to use the `gitea generate secret` to generate these secret keys.)
+* Ensure that any other secret keys you need are set.
+
 See the [command line documentation]({{< relref "doc/usage/command-line.en-us.md" >}}) for information on using `gitea generate secret`.
 
 ### Configure Gitea's working directory
diff --git a/docs/content/doc/installation/from-package.en-us.md b/docs/content/doc/installation/from-package.en-us.md
index 56ca97a8a5..3f75f26a53 100644
--- a/docs/content/doc/installation/from-package.en-us.md
+++ b/docs/content/doc/installation/from-package.en-us.md
@@ -53,7 +53,7 @@ snap install gitea
 
 ## SUSE and openSUSE
 
-OpenSUSE build service provides packages for [openSUSE and SLE](https://software.opensuse.org/download/package?package=gitea&project=devel%3Atools%3Ascm) 
+OpenSUSE build service provides packages for [openSUSE and SLE](https://software.opensuse.org/download/package?package=gitea&project=devel%3Atools%3Ascm)
 in the Development Software Configuration Management Repository
 
 ## Windows
diff --git a/docs/content/doc/installation/from-source.en-us.md b/docs/content/doc/installation/from-source.en-us.md
index 54e79769ea..660f996b1e 100644
--- a/docs/content/doc/installation/from-source.en-us.md
+++ b/docs/content/doc/installation/from-source.en-us.md
@@ -101,7 +101,7 @@ Depending on requirements, the following build tags can be included.
 - `pam`: Enable support for PAM (Linux Pluggable Authentication Modules). Can
   be used to authenticate local users or extend authentication to methods
   available to PAM.
-* `gogit`: (EXPERIMENTAL) Use go-git variants of Git commands.
+- `gogit`: (EXPERIMENTAL) Use go-git variants of Git commands.
 
 Bundling assets into the binary using the `bindata` build tag is recommended for
 production deployments. It is possible to serve the static assets directly via a reverse proxy,
diff --git a/docs/content/doc/installation/from-source.fr-fr.md b/docs/content/doc/installation/from-source.fr-fr.md
index 4afbd13773..00f67eab55 100644
--- a/docs/content/doc/installation/from-source.fr-fr.md
+++ b/docs/content/doc/installation/from-source.fr-fr.md
@@ -30,7 +30,6 @@ cd $GOPATH/src/code.gitea.io/gitea
 
 Maintenant, il est temps de décider quelle version de Gitea vous souhaitez compiler et installer. Actuellement, ils existent plusieurs options possibles. Si vous voulez compiler notre branche `master`, vous pouvez directement passer à la [section compilation](#compilation), cette branche représente la dernière version en cours de développement et n'a pas vocation à être utiliser en production.
 
-
 Si vous souhaitez compiler la dernière version stable, utilisez les étiquettes ou les différentes branches disponibles. Vous pouvez voir les branches disponibles et comment utiliser cette branche avec ces commandes:
 
 ```
diff --git a/docs/content/doc/installation/from-source.zh-cn.md b/docs/content/doc/installation/from-source.zh-cn.md
index 7d08033603..275b0c2f74 100644
--- a/docs/content/doc/installation/from-source.zh-cn.md
+++ b/docs/content/doc/installation/from-source.zh-cn.md
@@ -26,7 +26,7 @@ go get -d -u code.gitea.io/gitea
 cd $GOPATH/src/code.gitea.io/gitea
 ```
 
-然后你可以选择编译和安装的版本，当前你有多个选择。如果你想编译 `master` 版本，你可以直接跳到 [编译](#build) 部分，这是我们的开发分支，虽然也很稳定但不建议您在正式产品中使用。
+然后你可以选择编译和安装的版本，当前你有多个选择。如果你想编译 `master` 版本，你可以直接跳到 [编译](#编译) 部分，这是我们的开发分支，虽然也很稳定但不建议您在正式产品中使用。
 
 如果你想编译最新稳定分支，你可以执行以下命令签出源码：
 
@@ -55,9 +55,9 @@ git checkout v{{< version >}}
 
 按照您的编译需求，以下 tags 可以使用：
 
-* `bindata`: 这个编译选项将会把运行Gitea所需的所有外部资源都打包到可执行文件中，这样部署将非常简单因为除了可执行程序将不再需要任何其他文件。
-* `sqlite sqlite_unlock_notify`: 这个编译选项将启用SQLite3数据库的支持，建议只在少数人使用时使用这个模式。
-* `pam`: 这个编译选项将会启用 PAM (Linux Pluggable Authentication Modules) 认证，如果你使用这一认证模式的话需要开启这个选项。
+- `bindata`: 这个编译选项将会把运行Gitea所需的所有外部资源都打包到可执行文件中，这样部署将非常简单因为除了可执行程序将不再需要任何其他文件。
+- `sqlite sqlite_unlock_notify`: 这个编译选项将启用SQLite3数据库的支持，建议只在少数人使用时使用这个模式。
+- `pam`: 这个编译选项将会启用 PAM (Linux Pluggable Authentication Modules) 认证，如果你使用这一认证模式的话需要开启这个选项。
 
 使用 bindata 可以打包资源文件到二进制可以使开发和测试更容易，你可以根据自己的需求决定是否打包资源文件。
 要包含资源文件，请使用 `bindata` tag：
diff --git a/docs/content/doc/installation/from-source.zh-tw.md b/docs/content/doc/installation/from-source.zh-tw.md
index 39c9878309..2b65d554ab 100644
--- a/docs/content/doc/installation/from-source.zh-tw.md
+++ b/docs/content/doc/installation/from-source.zh-tw.md
@@ -26,7 +26,7 @@ go get -d -u code.gitea.io/gitea
 cd $GOPATH/src/code.gitea.io/gitea
 ```
 
-現在該決定您要編譯或安裝的 Gitea 版本，您有很多可以選擇。如果您想編譯 `master` 版本，你可以直接跳到[編譯章節](#build)，這是我們開發分支，雖然很穩定，但是不建議用在正式環境。
+現在該決定您要編譯或安裝的 Gitea 版本，您有很多可以選擇。如果您想編譯 `master` 版本，你可以直接跳到[編譯章節](#編譯)，這是我們開發分支，雖然很穩定，但是不建議用在正式環境。
 
 假如您想要編譯最新穩定版本，可以執行底下命令切換到正確版本:
 
diff --git a/docs/content/doc/installation/on-kubernetes.zh-tw.md b/docs/content/doc/installation/on-kubernetes.zh-tw.md
index 5ea412aa00..345ff7ac2c 100644
--- a/docs/content/doc/installation/on-kubernetes.zh-tw.md
+++ b/docs/content/doc/installation/on-kubernetes.zh-tw.md
@@ -26,7 +26,7 @@ helm install gitea gitea-charts/gitea
 
 若您想自訂安裝（包括使用 kubernetes ingress），請前往完整的 [Gitea helm chart configuration details](https://gitea.com/gitea/helm-chart/)
 
-##運行狀況檢查終端節點
+## 運行狀況檢查終端節點
 
 Gitea 附帶了一個運行狀況檢查端點 `/api/healthz`，你可以像這樣在 kubernetes 中配置它:
 
diff --git a/docs/content/doc/installation/run-as-service-in-ubuntu.en-us.md b/docs/content/doc/installation/run-as-service-in-ubuntu.en-us.md
index 471377e9fc..9f65eaca9f 100644
--- a/docs/content/doc/installation/run-as-service-in-ubuntu.en-us.md
+++ b/docs/content/doc/installation/run-as-service-in-ubuntu.en-us.md
@@ -27,12 +27,14 @@ Change the user, home directory, and other required startup values. Change the
 PORT or remove the -p flag if default port is used.
 
 Enable and start Gitea at boot:
+
 ```
 sudo systemctl enable gitea
 sudo systemctl start gitea
 ```
 
 If you have systemd version 220 or later, you can enable and immediately start Gitea at once by:
+
 ```
 sudo systemctl enable gitea --now
 ```
@@ -40,11 +42,13 @@ sudo systemctl enable gitea --now
 #### Using supervisor
 
 Install supervisor by running below command in terminal:
+
 ```
 sudo apt install supervisor
 ```
 
 Create a log dir for the supervisor logs:
+
 ```
 # assuming Gitea is installed in /home/git/gitea/
 mkdir /home/git/gitea/log/supervisor
@@ -58,12 +62,14 @@ Using your favorite editor, change the user (`git`) and home
 or remove the -p flag if default port is used.
 
 Lastly enable and start supervisor at boot:
+
 ```
 sudo systemctl enable supervisor
 sudo systemctl start supervisor
 ```
 
 If you have systemd version 220 or later, you can enable and immediately start supervisor by:
+
 ```
 sudo systemctl enable supervisor --now
 ```
diff --git a/docs/content/doc/installation/run-as-service-in-ubuntu.zh-cn.md b/docs/content/doc/installation/run-as-service-in-ubuntu.zh-cn.md
index 02cd032b67..c76350ecdc 100644
--- a/docs/content/doc/installation/run-as-service-in-ubuntu.zh-cn.md
+++ b/docs/content/doc/installation/run-as-service-in-ubuntu.zh-cn.md
@@ -18,6 +18,7 @@ menu:
 #### systemd 方式
 
 在 terminal 中执行以下命令：
+
 ```
 sudo vim /etc/systemd/system/gitea.service
 ```
@@ -27,26 +28,29 @@ sudo vim /etc/systemd/system/gitea.service
 修改 user，home 目录以及其他必须的初始化参数，如果使用自定义端口，则需修改 PORT 参数，反之如果使用默认端口则需删除 -p 标记。
 
 激活 gitea 并将它作为系统自启动服务：
+
 ```
 sudo systemctl enable gitea
 sudo systemctl start gitea
 ```
 
-
 #### 使用 supervisor
 
 在 terminal 中执行以下命令安装 supervisor：
+
 ```
 sudo apt install supervisor
 ```
 
 为 supervisor 配置日志路径：
+
 ```
 # assuming gitea is installed in /home/git/gitea/
 mkdir /home/git/gitea/log/supervisor
 ```
 
 在文件编辑器中打开 supervisor 的配置文件：
+
 ```
 sudo vim /etc/supervisor/supervisord.conf
 ```
@@ -57,6 +61,7 @@ sudo vim /etc/supervisor/supervisord.conf
 将 user(git) 和 home(/home/git) 设置为与上文部署中匹配的值。如果使用自定义端口，则需修改 PORT 参数，反之如果使用默认端口则需删除 -p 标记。
 
 最后激活 supervisor 并将它作为系统自启动服务：
+
 ```
 sudo systemctl enable supervisor
 sudo systemctl start supervisor
diff --git a/docs/content/doc/installation/with-docker-rootless.en-us.md b/docs/content/doc/installation/with-docker-rootless.en-us.md
index 634e08a72e..3cae65c2b2 100644
--- a/docs/content/doc/installation/with-docker-rootless.en-us.md
+++ b/docs/content/doc/installation/with-docker-rootless.en-us.md
@@ -247,6 +247,7 @@ files; for named volumes, this is done through another container or by direct ac
 :exclamation::exclamation: **Make sure you have volumed data to somewhere outside Docker container** :exclamation::exclamation:
 
 To upgrade your installation to the latest release:
+
 ```
 # Edit `docker-compose.yml` to update the version, if you have one specified
 # Pull new images
diff --git a/docs/content/doc/installation/with-docker.en-us.md b/docs/content/doc/installation/with-docker.en-us.md
index 940b38aa75..fb60b97118 100644
--- a/docs/content/doc/installation/with-docker.en-us.md
+++ b/docs/content/doc/installation/with-docker.en-us.md
@@ -255,7 +255,7 @@ favorite browser to finalize the installation. Visit http://server-ip:3000 and f
 installation wizard. If the database was started with the `docker-compose` setup as
 documented above, please note that `db` must be used as the database hostname.
 
-## Configure the user inside Gitea using environment variables 
+## Configure the user inside Gitea using environment variables
 
 - `USER`: **git**: The username of the user that runs Gitea within the container.
 - `USER_UID`: **1000**: The UID (Unix user ID) of the user that runs Gitea within the container. Match this to the UID of the owner of the `/data` volume if using host volumes (this is not necessary with named volumes).
@@ -394,9 +394,9 @@ In this option, the idea is that the host simply uses the `authorized_keys` that
 Here is a detailed explanation what is happening when a SSH request is made:
 
 1. The client adds their SSH public key to Gitea using the webpage.
-2. Gitea in the container will add an entry for this key to the `.ssh/authorized_keys` file of its running user, `git`. 
+2. Gitea in the container will add an entry for this key to the `.ssh/authorized_keys` file of its running user, `git`.
     - However, because `/home/git/.ssh/` on the host is mounted as `/data/git/.ssh` this means that the key has been added to the host `git` user's `authorized_keys` file too.
-3. This entry has the public key, but also has a `command=` option. 
+3. This entry has the public key, but also has a `command=` option.
     - This command matches the location of the Gitea binary on the container, but also the location of the shim on the host.
 4. The client then makes an SSH request to the host SSH server using the `git` user, e.g. `git clone git@domain:user/repo.git`.
 5. The client will attempt to authenticate with the server, passing one or more public keys in turn to the host.
@@ -441,7 +441,7 @@ we create a new shell for the git user. As an administrative user on the host ru
 Here is a detailed explanation what is happening when a SSH request is made:
 
 1. The client adds their SSH public key to Gitea using the webpage.
-2. Gitea in the container will add an entry for this key to the `.ssh/authorized_keys` file of its running user, `git`. 
+2. Gitea in the container will add an entry for this key to the `.ssh/authorized_keys` file of its running user, `git`.
     - However, because `/home/git/.ssh/` on the host is mounted as `/data/git/.ssh` this means that the key has been added to the host `git` user's `authorized_keys` file too.
 3. This entry has the public key, but also has a `command=` option.
     - This command matches the location of the Gitea binary on the container.
@@ -482,7 +482,7 @@ sudo usermod -s /home/git/docker-shell git
 Here is a detailed explanation what is happening when a SSH request is made:
 
 1. The client adds their SSH public key to Gitea using the webpage.
-2. Gitea in the container will add an entry for this key to the `.ssh/authorized_keys` file of its running user, `git`. 
+2. Gitea in the container will add an entry for this key to the `.ssh/authorized_keys` file of its running user, `git`.
     - However, because `/home/git/.ssh/` on the host is mounted as `/data/git/.ssh` this means that the key has been added to the host `git` user's `authorized_keys` file too.
 3. This entry has the public key, but also has a `command=` option.
     - This command matches the location of the Gitea binary on the container.
@@ -531,7 +531,7 @@ In this option, the idea is that the host SSH uses an `AuthorizedKeysCommand` in
 
 Now all attempts to login as the `git` user on the host will be forwarded to the docker - including the `SSH_ORIGINAL_COMMAND`. We now need to set-up SSH authentication on the host.
 
-We will do this by leveraging the [SSH AuthorizedKeysCommand](https://docs.gitea.io/en-us/command-line/#keys) to match the keys against those accepted by Gitea. 
+We will do this by leveraging the [SSH AuthorizedKeysCommand](https://docs.gitea.io/en-us/command-line/#keys) to match the keys against those accepted by Gitea.
 
 Add the following block to `/etc/ssh/sshd_config`, on the host:
 
diff --git a/docs/content/doc/packages/maven.en-us.md b/docs/content/doc/packages/maven.en-us.md
index 837c8434ae..04ee488e49 100644
--- a/docs/content/doc/packages/maven.en-us.md
+++ b/docs/content/doc/packages/maven.en-us.md
@@ -107,4 +107,4 @@ mvn install
 mvn install
 mvn deploy
 mvn dependency:get:
-```
\ No newline at end of file
+```
diff --git a/docs/content/doc/packages/pypi.en-us.md b/docs/content/doc/packages/pypi.en-us.md
index d9f4872dca..1482575072 100644
--- a/docs/content/doc/packages/pypi.en-us.md
+++ b/docs/content/doc/packages/pypi.en-us.md
@@ -82,4 +82,4 @@ pip install --index-url https://testuser:password123@gitea.example.com/api/packa
 ```
 pip install
 twine upload
-```
\ No newline at end of file
+```
diff --git a/docs/content/doc/packages/rubygems.en-us.md b/docs/content/doc/packages/rubygems.en-us.md
index 9d9ce09b1c..98b3feafcd 100644
--- a/docs/content/doc/packages/rubygems.en-us.md
+++ b/docs/content/doc/packages/rubygems.en-us.md
@@ -124,4 +124,4 @@ gem install --host https://gitea.example.com/api/packages/testuser/rubygems test
 gem install
 bundle install
 gem push
-```
\ No newline at end of file
+```
diff --git a/docs/content/doc/translation/guidelines.de-de.md b/docs/content/doc/translation/guidelines.de-de.md
index 9f4b84ca9b..eee031a54e 100644
--- a/docs/content/doc/translation/guidelines.de-de.md
+++ b/docs/content/doc/translation/guidelines.de-de.md
@@ -15,10 +15,12 @@ menu:
 ## Allgemeines
 
 Anrede: Wenig förmlich:
+
 * "Du"-Form
 * Keine "Amtsdeusch"-Umschreibungen, einfach so als ob man den Nutzer direkt persönlich ansprechen würde
 
 Genauer definiert:
+
 * "falsch" anstatt "nicht korrekt/inkorrekt"
 * Benutzerkonto oder Konto? Oder Account?
 * "Wende dich an ..." anstatt "kontaktiere ..."
diff --git a/docs/content/doc/upgrade/from-gitea.en-us.md b/docs/content/doc/upgrade/from-gitea.en-us.md
index 2f64e0fac6..f5c9551f31 100644
--- a/docs/content/doc/upgrade/from-gitea.en-us.md
+++ b/docs/content/doc/upgrade/from-gitea.en-us.md
@@ -20,14 +20,14 @@ menu:
 {{< toc >}}
 
 To update Gitea, download a newer version, stop the old one, perform a backup, and run the new one.
-Every time a Gitea instance starts up, it checks whether a database migration should be run. 
+Every time a Gitea instance starts up, it checks whether a database migration should be run.
 If a database migration is required, Gitea will take some time to complete the upgrade and then serve.
 
 ## Backup for downgrade
 
-Gitea keeps compatibility for patch versions whose first two fields are the same (`a.b.x` -> `a.b.y`), 
-these patch versions can be upgraded and downgraded with the same database structure. 
-Otherwise (`a.b.?` -> `a.c.?`), a newer Gitea version will upgrade the old database 
+Gitea keeps compatibility for patch versions whose first two fields are the same (`a.b.x` -> `a.b.y`),
+these patch versions can be upgraded and downgraded with the same database structure.
+Otherwise (`a.b.?` -> `a.c.?`), a newer Gitea version will upgrade the old database
 to a new structure that may differ from the old version.
 
 For example:
@@ -39,8 +39,8 @@ For example:
 | 1.4.x | 1.5.y | ✅ Database gets upgraded. You can upgrade from 1.4.x to the latest 1.5.y directly. |
 | 1.5.y | 1.4.x | ❌ Database already got upgraded and can not be used for an old Gitea, use a backup to downgrade. |
 
-**Since you can not run an old Gitea with an upgraded database, 
-a backup should always be made before a database upgrade.** 
+**Since you can not run an old Gitea with an upgraded database,
+a backup should always be made before a database upgrade.**
 
 If you use Gitea in production, it's always highly recommended to make a backup before upgrade,
 even if the upgrade is between patch versions.
@@ -56,7 +56,6 @@ Backup steps:
 If you are using cloud services or filesystems with snapshot feature,
 a snapshot for the Gitea data volume and related object storage is more convenient.
 
-
 ## Upgrade with Docker
 
 * `docker pull` the latest Gitea release.
@@ -73,16 +72,16 @@ a snapshot for the Gitea data volume and related object storage is more convenie
 
 * Download the latest Gitea binary to a temporary directory.
 * Stop the running instance, backup data.
-* Replace the installed Gitea binary with the downloaded one. 
+* Replace the installed Gitea binary with the downloaded one.
 * Start the Gitea instance.
 
 A script automating these steps for a deployment on Linux can be found at [`contrib/upgrade.sh` in Gitea's source tree](https://github.com/go-gitea/gitea/blob/main/contrib/upgrade.sh).
 
 ## Take care about customized templates
 
-Gitea's template structure and variables may change between releases, if you are using customized templates, 
-do pay attention if your templates are compatible with the Gitea you are using. 
+Gitea's template structure and variables may change between releases, if you are using customized templates,
+do pay attention if your templates are compatible with the Gitea you are using.
 
-If the customized templates don't match Gitea version, you may experience: 
-`50x` server error, page components missing or malfunctioning, strange page layout, ... 
+If the customized templates don't match Gitea version, you may experience:
+`50x` server error, page components missing or malfunctioning, strange page layout, ...
 Remove or update the incompatible templates and Gitea web will work again.
diff --git a/docs/content/doc/usage/backup-and-restore.zh-tw.md b/docs/content/doc/usage/backup-and-restore.zh-tw.md
index 152d0a19b7..18e244b19c 100644
--- a/docs/content/doc/usage/backup-and-restore.zh-tw.md
+++ b/docs/content/doc/usage/backup-and-restore.zh-tw.md
@@ -45,6 +45,7 @@ Gitea 目前支援 `dump` 指令，用來將資料備份成 zip 檔案，後續�
 持續更新中: 此文件尚未完成.
 
 例:
+
 ```sh
 unzip gitea-dump-1610949662.zip
 cd gitea-dump-1610949662
diff --git a/docs/content/doc/usage/command-line.en-us.md b/docs/content/doc/usage/command-line.en-us.md
index 8cc420ed11..5f05bc4c3b 100644
--- a/docs/content/doc/usage/command-line.en-us.md
+++ b/docs/content/doc/usage/command-line.en-us.md
@@ -364,7 +364,7 @@ NB: Gitea must be running for this command to succeed.
 
 ### migrate
 
-Migrates the database. This command can be used to run other commands before starting the server for the first time.  
+Migrates the database. This command can be used to run other commands before starting the server for the first time.
 This command is idempotent.
 
 ### convert
@@ -522,7 +522,7 @@ Dump-repo dumps repository data from Git/GitHub/Gitea/GitLab:
 
 - Options:
   - `--git_service service` : Git service, it could be `git`, `github`, `gitea`, `gitlab`, If clone_addr could be recognized, this could be ignored.
-  - `--repo_dir dir`, `-r dir`: Repository dir path to store the data 
+  - `--repo_dir dir`, `-r dir`: Repository dir path to store the data
   - `--clone_addr addr`: The URL will be clone, currently could be a git/github/gitea/gitlab http/https URL. i.e. https://github.com/lunny/tango.git
   - `--auth_username lunny`: The username to visit the clone_addr
   - `--auth_password <password>`: The password to visit the clone_addr
diff --git a/docs/content/doc/usage/email-setup.en-us.md b/docs/content/doc/usage/email-setup.en-us.md
index df1b8545af..533e0fe1a8 100644
--- a/docs/content/doc/usage/email-setup.en-us.md
+++ b/docs/content/doc/usage/email-setup.en-us.md
@@ -60,9 +60,10 @@ To send a test email to validate the settings, go to Gitea > Site Administration
 For the full list of options check the [Config Cheat Sheet]({{< relref "doc/advanced/config-cheat-sheet.en-us.md" >}})
 
 Please note: authentication is only supported when the SMTP server communication is encrypted with TLS or `HOST=localhost`. TLS encryption can be through:
-  - STARTTLS (also known as Opportunistic TLS) via port 587. Initial connection is done over cleartext, but then be upgraded over TLS if the server supports it.
-  - SMTPS connection (SMTP over TLS) via the default port 465. Connection to the server use TLS from the beginning.
-  - Forced SMTPS connection with `IS_TLS_ENABLED=true`. (These are both known as Implicit TLS.)
+
+- STARTTLS (also known as Opportunistic TLS) via port 587. Initial connection is done over cleartext, but then be upgraded over TLS if the server supports it.
+- SMTPS connection (SMTP over TLS) via the default port 465. Connection to the server use TLS from the beginning.
+- Forced SMTPS connection with `IS_TLS_ENABLED=true`. (These are both known as Implicit TLS.)
 This is due to protections imposed by the Go internal libraries against STRIPTLS attacks.
 
 Note that Implicit TLS is recommended by [RFC8314](https://tools.ietf.org/html/rfc8314#section-3) since 2018.
@@ -82,4 +83,3 @@ MAILER_TYPE    = smtp
 IS_TLS_ENABLED = true
 HELO_HOSTNAME  = example.com
 ```
-
diff --git a/docs/content/doc/usage/fail2ban-setup.en-us.md b/docs/content/doc/usage/fail2ban-setup.en-us.md
index d1ff633246..f00551e3ef 100644
--- a/docs/content/doc/usage/fail2ban-setup.en-us.md
+++ b/docs/content/doc/usage/fail2ban-setup.en-us.md
@@ -29,31 +29,37 @@ on a bad authentication from the web or CLI using SSH or HTTP respectively:
 ```log
 2020/10/15 16:05:09 modules/ssh/ssh.go:143:publicKeyHandler() [W] Failed authentication attempt from xxx.xxx.xxx.xxx
 ```
+
 (DEPRECATED: This may be a false positive as the user may still go on to correctly authenticate.)
 
 ```log
 2020/10/15 16:05:09 modules/ssh/ssh.go:155:publicKeyHandler() [W] Failed authentication attempt from xxx.xxx.xxx.xxx
 ```
+
 (DEPRECATED: This may be a false positive as the user may still go on to correctly authenticate.)
 
 ```log
 2020/10/15 16:05:09 modules/ssh/ssh.go:198:publicKeyHandler() [W] Failed authentication attempt from xxx.xxx.xxx.xxx
 ```
+
 (DEPRECATED: This may be a false positive as the user may still go on to correctly authenticate.)
 
 ```log
 2020/10/15 16:05:09 modules/ssh/ssh.go:213:publicKeyHandler() [W] Failed authentication attempt from xxx.xxx.xxx.xxx
 ```
+
 (DEPRECATED: This may be a false positive as the user may still go on to correctly authenticate.)
 
 ```log
 2020/10/15 16:05:09 modules/ssh/ssh.go:227:publicKeyHandler() [W] Failed authentication attempt from xxx.xxx.xxx.xxx
 ```
+
 (DEPRECATED: This may be a false positive as the user may still go on to correctly authenticate.)
 
 ```log
 2020/10/15 16:05:09 modules/ssh/ssh.go:249:sshConnectionFailed() [W] Failed authentication attempt from xxx.xxx.xxx.xxx
 ```
+
 (From 1.15 this new message will available and doesn't have any of the false positive results that above messages from publicKeyHandler do. This will only be logged if the user has completely failed authentication.)
 
 ```log
diff --git a/docs/content/doc/usage/https-support.md b/docs/content/doc/usage/https-support.md
index 756e11fd03..783d6d8037 100644
--- a/docs/content/doc/usage/https-support.md
+++ b/docs/content/doc/usage/https-support.md
@@ -60,6 +60,7 @@ If you are using Docker, make sure that this port is configured in your `docker-
 [ACME](https://tools.ietf.org/html/rfc8555) is a Certificate Authority standard protocol that allows you to automatically request and renew SSL/TLS certificates. [Let's Encrypt](https://letsencrypt.org/) is a free publicly trusted Certificate Authority server using this standard. Only `HTTP-01` and `TLS-ALPN-01` challenges are implemented. In order for ACME challenges to pass and verify your domain ownership, external traffic to the gitea domain on port `80` (`HTTP-01`) or port `443` (`TLS-ALPN-01`) has to be served by the gitea instance. Setting up [HTTP redirection](#setting-up-http-redirection) and port-forwards might be needed for external traffic to route correctly. Normal traffic to port `80` will otherwise be automatically redirected to HTTPS. **You must consent** to the ACME provider's terms of service (default Let's Encrypt's [terms of service](https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf)).
 
 Minimum setup using the default Let's Encrypt:
+
 ```ini
 [server]
 PROTOCOL=https
@@ -72,6 +73,7 @@ ACME_EMAIL=email@example.com
 ```
 
 Minimumg setup using a [smallstep CA](https://github.com/smallstep/certificates), refer to [their tutorial](https://smallstep.com/docs/tutorials/acme-challenge) for more information.
+
 ```ini
 [server]
 PROTOCOL=https
diff --git a/docs/content/doc/usage/issue-pull-request-templates.zh-cn.md b/docs/content/doc/usage/issue-pull-request-templates.zh-cn.md
index 1d2539b7bd..db69f3e5ce 100644
--- a/docs/content/doc/usage/issue-pull-request-templates.zh-cn.md
+++ b/docs/content/doc/usage/issue-pull-request-templates.zh-cn.md
@@ -26,7 +26,6 @@ menu:
 * .github/ISSUE_TEMPLATE.md
 * .github/issue_template.md
 
-
 以下罗列了一些可供参考的 PR 模板:
 
 * PULL_REQUEST_TEMPLATE.md
diff --git a/docs/content/doc/usage/permissions.en-us.md b/docs/content/doc/usage/permissions.en-us.md
index 0c3dc9e09e..013dbfabd4 100644
--- a/docs/content/doc/usage/permissions.en-us.md
+++ b/docs/content/doc/usage/permissions.en-us.md
@@ -55,7 +55,7 @@ And there are some differences for permissions between individual repositories a
 
 ## Individual Repository
 
-For individual repositories, the creators are the only owners of repositories and have no limit to change anything of this 
+For individual repositories, the creators are the only owners of repositories and have no limit to change anything of this
 repository or delete it. Repositories owners could add collaborators to help maintain the repositories. Collaborators could have `Read`, `Write` and `Admin` permissions.
 
 ## Organization Repository
diff --git a/docs/content/doc/usage/push-options.en-us.md b/docs/content/doc/usage/push-options.en-us.md
index 6539c9d7cd..8d7de19609 100644
--- a/docs/content/doc/usage/push-options.en-us.md
+++ b/docs/content/doc/usage/push-options.en-us.md
@@ -18,14 +18,16 @@ menu:
 In Gitea `1.13`, support for some [push options](https://git-scm.com/docs/git-push#Documentation/git-push.txt--oltoptiongt)
 were added.
 
-
 ## Supported Options
 
-- `repo.private` (true|false) - Change the repository's visibility.  
-This is particularly useful when combined with push-to-create.
+- `repo.private` (true|false) - Change the repository's visibility.
+
+  This is particularly useful when combined with push-to-create.
+
 - `repo.template` (true|false) - Change whether the repository is a template.
 
-Example of changing a repository's visibility to public:  
+Example of changing a repository's visibility to public:
+
 ```shell
 git push -o repo.private=false -u origin master
 ```
diff --git a/docs/content/doc/usage/push-options.zh-tw.md b/docs/content/doc/usage/push-options.zh-tw.md
index b0fc75ac24..d6ffbe695b 100644
--- a/docs/content/doc/usage/push-options.zh-tw.md
+++ b/docs/content/doc/usage/push-options.zh-tw.md
@@ -20,8 +20,10 @@ Gitea 從 `1.13` 版開始支援某些 [push options](https://git-scm.com/docs/g
 
 ## 支援的 Options
 
-- `repo.private` (true|false) - 修改儲存庫的可見性。  
+- `repo.private` (true|false) - 修改儲存庫的可見性。
+
   與 push-to-create 一起使用時特別有用。
+
 - `repo.template` (true|false) - 修改儲存庫是否為範本儲存庫。
 
 以下範例修改儲存庫的可見性為公開：
diff --git a/docs/content/doc/usage/reverse-proxies.en-us.md b/docs/content/doc/usage/reverse-proxies.en-us.md
index 9e903f4259..5797d8e5eb 100644
--- a/docs/content/doc/usage/reverse-proxies.en-us.md
+++ b/docs/content/doc/usage/reverse-proxies.en-us.md
@@ -138,7 +138,6 @@ In your nginx config file containing your Gitea proxy directive, find the `locat
 `client_max_body_size 16M;` to set this limit to 16 megabytes or any other number of choice.
 If you use Git LFS, this will also limit the size of the largest file you will be able to push.
 
-
 ## Apache HTTPD
 
 If you want Apache HTTPD to serve your Gitea instance, you can add the following to your Apache HTTPD configuration (usually located at `/etc/apache2/httpd.conf` in Ubuntu):
@@ -307,6 +306,7 @@ If you wish to run Gitea with IIS. You will need to setup IIS with URL Rewrite a
 If you want HAProxy to serve your Gitea instance, you can add the following to your HAProxy configuration
 
 add an acl in the frontend section to redirect calls to gitea.example.com to the correct backend
+
 ```
 frontend http-in
     ...
@@ -316,6 +316,7 @@ frontend http-in
 ```
 
 add the previously defined backend section
+
 ```
 backend gitea
     server localhost:3000 check
@@ -338,6 +339,7 @@ frontend http-in
 With that configuration http://example.com/gitea/ will redirect to your Gitea instance.
 
 then for the backend section
+
 ```
 backend gitea
     http-request replace-path /gitea\/?(.*) \/\1
diff --git a/docs/content/doc/usage/reverse-proxies.zh-cn.md b/docs/content/doc/usage/reverse-proxies.zh-cn.md
index 88db0c3790..722b9c7c9d 100644
--- a/docs/content/doc/usage/reverse-proxies.zh-cn.md
+++ b/docs/content/doc/usage/reverse-proxies.zh-cn.md
@@ -121,4 +121,4 @@ gitea:
     - "traefik.http.services.gitea-websecure.loadbalancer.server.port=3000"
 ```
 
-这份配置假设您使用 traefik 来处理 HTTPS 服务，并在其和 Gitea 之间使用 HTTP 进行通信。
\ No newline at end of file
+这份配置假设您使用 traefik 来处理 HTTPS 服务，并在其和 Gitea 之间使用 HTTP 进行通信。
diff --git a/docs/content/doc/usage/template-repositories.md b/docs/content/doc/usage/template-repositories.md
index 24fdf28ee0..9a2a23ed2b 100644
--- a/docs/content/doc/usage/template-repositories.md
+++ b/docs/content/doc/usage/template-repositories.md
@@ -19,8 +19,10 @@ menu:
 
 {{< toc >}}
 
-Gitea `1.11.0` and above includes template repositories, and one feature implemented with them is auto-expansion of specific variables within your template files.  
-To tell Gitea which files to expand, you must include a `template` file inside the `.gitea` directory of the template repository.  
+Gitea `1.11.0` and above includes template repositories, and one feature implemented with them is auto-expansion of specific variables within your template files.
+
+To tell Gitea which files to expand, you must include a `template` file inside the `.gitea` directory of the template repository.
+
 Gitea uses [gobwas/glob](https://github.com/gobwas/glob) for its glob syntax. It closely resembles a traditional `.gitignore`, however there may be slight differences.
 
 ## Example `.gitea/template` file
@@ -45,7 +47,8 @@ a/b/c/d.json
 
 ## Variable Expansion
 
-In any file matched by the above globs, certain variables will be expanded.  
+In any file matched by the above globs, certain variables will be expanded.
+
 All variables must be of the form `$VAR` or `${VAR}`. To escape an expansion, use a double `$$`, such as `$$VAR` or `$${VAR}`
 
 | Variable             | Expands To                                          | Transformable |
@@ -65,7 +68,8 @@ All variables must be of the form `$VAR` or `${VAR}`. To escape an expansion, us
 
 ## Transformers :robot:
 
-Gitea `1.12.0` adds a few transformers to some of the applicable variables above.  
+Gitea `1.12.0` adds a few transformers to some of the applicable variables above.
+
 For example, to get `REPO_NAME` in `PASCAL`-case, your template would use `${REPO_NAME_PASCAL}`
 
 Feeding `go-sdk` to the available transformers yields...
diff --git a/docs/content/page/index.de-de.md b/docs/content/page/index.de-de.md
index e901702969..8f8f264ed1 100644
--- a/docs/content/page/index.de-de.md
+++ b/docs/content/page/index.de-de.md
@@ -10,27 +10,28 @@ draft: false
 
 # Was ist Gitea?
 
-Gitea ist ein einfacher, selbst gehosteter Git-Service. Änlich wie GitHub, Bitbucket oder GitLab.  
+Gitea ist ein einfacher, selbst gehosteter Git-Service. Änlich wie GitHub, Bitbucket oder GitLab.
+
 Gitea ist ein [Gogs](http://gogs.io)-Fork.
 
 ## Ziele
 
- * Einfach zu installieren
- * Plattformübergreifend
- * Leichtgewichtig
- * Quelloffen
+* Einfach zu installieren
+* Plattformübergreifend
+* Leichtgewichtig
+* Quelloffen
 
 ## System Voraussetzungen
 
-- Ein Raspberry Pi 3 ist leistungsstark genug, um Gitea für kleine Belastungen laufen zu lassen.
-- 2 CPU Kerne und 1GB RAM sind für kleine Teams/Projekte ausreichend.
-- Gitea sollte unter einem seperaten nicht-root Account auf UNIX-Systemen ausgeführt werden.
-   - Achtung: Gitea verwaltet die `~/.ssh/authorized_keys` Datei. Gitea unter einem normalen Benutzer auszuführen könnte dazu führen, dass dieser sich nicht mehr anmelden kann.
-- [Git](https://git-scm.com/) Version 2.0 oder später wird benötigt.
-   - Wenn git >= 2.1.2. und [Git large file storage](https://git-lfs.github.com/) aktiviert ist, dann wird es auch in Gitea verwendbar sein.
-   - Wenn git >= 2.18, dann wird das Rendern von Commit-Graphen automatisch aktiviert.
+* Ein Raspberry Pi 3 ist leistungsstark genug, um Gitea für kleine Belastungen laufen zu lassen.
+* 2 CPU Kerne und 1GB RAM sind für kleine Teams/Projekte ausreichend.
+* Gitea sollte unter einem seperaten nicht-root Account auf UNIX-Systemen ausgeführt werden.
+  * Achtung: Gitea verwaltet die `~/.ssh/authorized_keys` Datei. Gitea unter einem normalen Benutzer auszuführen könnte dazu führen, dass dieser sich nicht mehr anmelden kann.
+* [Git](https://git-scm.com/) Version 2.0 oder später wird benötigt.
+  * Wenn git >= 2.1.2. und [Git large file storage](https://git-lfs.github.com/) aktiviert ist, dann wird es auch in Gitea verwendbar sein.
+  * Wenn git >= 2.18, dann wird das Rendern von Commit-Graphen automatisch aktiviert.
 
 ## Browser Unterstützung
 
-- Letzten 2 Versions von Chrome, Firefox, Safari und Edge
-- Firefox ESR
+* Letzten 2 Versions von Chrome, Firefox, Safari und Edge
+* Firefox ESR
diff --git a/docs/content/page/index.en-us.md b/docs/content/page/index.en-us.md
index f9da78df51..8e2e36223a 100644
--- a/docs/content/page/index.en-us.md
+++ b/docs/content/page/index.en-us.md
@@ -27,43 +27,43 @@ You can try it out using [the online demo](https://try.gitea.io/).
 ## Features
 
 - User Dashboard
-    - Context switcher (organization or current user)
-    - Activity timeline
-        - Commits
-        - Issues
-        - Pull requests
-        - Repository creation
-    - Searchable repository list
-    - List of organizations
-    - A list of mirror repositories
+  - Context switcher (organization or current user)
+  - Activity timeline
+    - Commits
+    - Issues
+    - Pull requests
+    - Repository creation
+  - Searchable repository list
+  - List of organizations
+  - A list of mirror repositories
 - Issues dashboard
-    - Context switcher (organization or current user)
-    - Filter by
-        - Open
-        - Closed
-        - Your repositories
-        - Assigned issues
-        - Your issues
-        - Repository
-    - Sort by
-        - Oldest
-        - Last updated
-        - Number of comments
+  - Context switcher (organization or current user)
+  - Filter by
+    - Open
+    - Closed
+    - Your repositories
+    - Assigned issues
+    - Your issues
+    - Repository
+  - Sort by
+    - Oldest
+    - Last updated
+    - Number of comments
 - Pull request dashboard
-    - Same as issue dashboard
+  - Same as issue dashboard
 - Repository types
-    - Mirror
-    - Normal
-    - Migrated
+  - Mirror
+  - Normal
+  - Migrated
 - Notifications (email and web)
-    - Read
-    - Unread
-    - Pin
+  - Read
+  - Unread
+  - Pin
 - Explore page
-    - Users
-    - Repos
-    - Organizations
-    - Search
+  - Users
+  - Repos
+  - Organizations
+  - Search
 - Custom templates
 - Override public files (logo, css, etc)
 - CSRF and XSS protection
@@ -71,187 +71,187 @@ You can try it out using [the online demo](https://try.gitea.io/).
 - Set allowed upload sizes and types
 - Logging
 - Configuration
-    - Databases
-        - MySQL (>=5.7)
-        - PostgreSQL (>=10)
-        - SQLite3
-        - MSSQL (>=2008R2 SP3)
-        - TiDB (MySQL protocol)
-    - Configuration file
-        - [app.ini](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini)
-    - Admin panel
-        - Statistics
-        - Actions
-            - Delete inactive accounts
-            - Delete cached repository archives
-            - Delete repositories records which are missing their files
-            - Run garbage collection on repositories
-            - Rewrite SSH keys
-            - Resync hooks
-            - Recreate repositories which are missing
-        - Server status
-            - Uptime
-            - Memory
-            - Current # of goroutines
-            - And more
-         - User management
-            - Search
-            - Sort
-            - Last login
-            - Authentication source
-            - Maximum repositories
-            - Disable account
-            - Admin permissions
-            - Permission to create Git Hooks
-            - Permission to create organizations
-            - Permission to import repositories
-        - Organization management
-            - People
-            - Teams
-            - Avatar
-            - Hooks
-        - Repository management
-            - See all repository information and manage repositories
-        - Authentication sources
-            - OAuth
-            - PAM
-            - LDAP
-            - SMTP
-        - Configuration viewer
-            - Everything in config file
-        - System notices
-            - When something unexpected happens
-        - Monitoring
-            - Current processes
-            - Cron jobs
-                - Update mirrors
-                - Repository health check
-                - Check repository statistics
-                - Clean up old archives
-    - Environment variables
-    - Command line options
+  - Databases
+    - MySQL (>=5.7)
+    - PostgreSQL (>=10)
+    - SQLite3
+    - MSSQL (>=2008R2 SP3)
+    - TiDB (MySQL protocol)
+  - Configuration file
+    - [app.ini](https://github.com/go-gitea/gitea/blob/main/custom/conf/app.example.ini)
+  - Admin panel
+    - Statistics
+    - Actions
+      - Delete inactive accounts
+      - Delete cached repository archives
+      - Delete repositories records which are missing their files
+      - Run garbage collection on repositories
+      - Rewrite SSH keys
+      - Resync hooks
+      - Recreate repositories which are missing
+    - Server status
+      - Uptime
+      - Memory
+      - Current # of goroutines
+      - And more
+    - User management
+      - Search
+      - Sort
+      - Last login
+      - Authentication source
+      - Maximum repositories
+      - Disable account
+      - Admin permissions
+      - Permission to create Git Hooks
+      - Permission to create organizations
+      - Permission to import repositories
+    - Organization management
+      - People
+      - Teams
+      - Avatar
+      - Hooks
+    - Repository management
+      - See all repository information and manage repositories
+    - Authentication sources
+      - OAuth
+      - PAM
+      - LDAP
+      - SMTP
+    - Configuration viewer
+      - Everything in config file
+    - System notices
+      - When something unexpected happens
+    - Monitoring
+      - Current processes
+      - Cron jobs
+        - Update mirrors
+        - Repository health check
+        - Check repository statistics
+        - Clean up old archives
+  - Environment variables
+  - Command line options
 - Multi-language support ([21 languages](https://github.com/go-gitea/gitea/tree/main/options/locale))
 - [Mermaid](https://mermaidjs.github.io/) Diagram support
 - Mail service
-    - Notifications
-    - Registration confirmation
-    - Password reset
+  - Notifications
+  - Registration confirmation
+  - Password reset
 - Reverse proxy support
-    - Includes subpaths
+  - Includes subpaths
 - Users
-    - Profile
-        - Name
-        - Username
-        - Email
-        - Website
-        - Join date
-        - Followers and following
-        - Organizations
-        - Repositories
-        - Activity
-        - Starred repositories
-    - Settings
-        - Same as profile and more below
-        - Keep email private
-        - Avatar
-            - Gravatar
-            - Libravatar
-            - Custom
-        - Password
-        - Multiple email addresses
-        - SSH Keys
-        - Connected applications
-        - Two factor authentication
-        - Linked OAuth2 sources
-        - Delete account
+  - Profile
+    - Name
+    - Username
+    - Email
+    - Website
+    - Join date
+    - Followers and following
+    - Organizations
+    - Repositories
+    - Activity
+    - Starred repositories
+  - Settings
+    - Same as profile and more below
+    - Keep email private
+    - Avatar
+      - Gravatar
+      - Libravatar
+      - Custom
+    - Password
+    - Multiple email addresses
+    - SSH Keys
+    - Connected applications
+    - Two factor authentication
+    - Linked OAuth2 sources
+    - Delete account
 - Repositories
-    - Clone with SSH/HTTP/HTTPS
-    - Git LFS
-    - Watch, Star, Fork
-    - View watchers, stars, and forks
-    - Code
-        - Branch browser
-        - Web based file upload and creation
-        - Clone urls
-        - Download
-            - ZIP
-            - TAR.GZ
-        - Web based editor
-            - Markdown editor
-            - Plain text editor
-                - Syntax highlighting
-            - Diff preview
-            - Preview
-            - Choose where to commit to
-        - View file history
-        - Delete file
-        - View raw
-    - Issues
-        - Issue templates
-        - Milestones
-        - Labels
-        - Assign issues
-        - Track time
-        - Reactions
-        - Filter
-            - Open
-            - Closed
-            - Assigned person
-            - Created by you
-            - Mentioning you
-        - Sort
-            - Oldest
-            - Last updated
-            - Number of comments
-        - Search
-        - Comments
-        - Attachments
-    - Pull requests
-        - Same features as issues
-    - Commits
-        - Commit graph
-        - Commits by branch
-        - Search
-        - Search in all branches
-        - View diff
-        - View SHA
-        - View author
-        - Browse files in commit
-    - Releases
-        - Attachments
-        - Title
-        - Content
-        - Delete
-        - Mark as pre-release
-        - Choose branch
-    - Wiki
-        - Import
-        - Markdown editor
-    - Settings
-        - Options
-            - Name
-            - Description
-            - Private/Public
-            - Website
-            - Wiki
-                - Enabled/disabled
-                - Internal/external
-            - Issues
-                - Enabled/disabled
-                - Internal/external
-                - External supports url rewriting for better integration
-            - Enable/disable pull requests
-            - Transfer repository
-            - Delete wiki
-            - Delete repository
-        - Collaboration
-            - Read/write/admin
-        - Branches
-            - Default branch
-            - Branch protection
-        - Webhooks
-        - Git Hooks
-        - Deploy keys
+  - Clone with SSH/HTTP/HTTPS
+  - Git LFS
+  - Watch, Star, Fork
+  - View watchers, stars, and forks
+  - Code
+    - Branch browser
+    - Web based file upload and creation
+    - Clone urls
+    - Download
+      - ZIP
+      - TAR.GZ
+    - Web based editor
+      - Markdown editor
+      - Plain text editor
+        - Syntax highlighting
+      - Diff preview
+      - Preview
+      - Choose where to commit to
+    - View file history
+    - Delete file
+    - View raw
+  - Issues
+    - Issue templates
+    - Milestones
+    - Labels
+    - Assign issues
+    - Track time
+    - Reactions
+    - Filter
+      - Open
+      - Closed
+      - Assigned person
+      - Created by you
+      - Mentioning you
+    - Sort
+      - Oldest
+      - Last updated
+      - Number of comments
+    - Search
+    - Comments
+    - Attachments
+  - Pull requests
+    - Same features as issues
+  - Commits
+    - Commit graph
+    - Commits by branch
+    - Search
+    - Search in all branches
+    - View diff
+    - View SHA
+    - View author
+    - Browse files in commit
+  - Releases
+    - Attachments
+    - Title
+    - Content
+    - Delete
+    - Mark as pre-release
+    - Choose branch
+  - Wiki
+    - Import
+    - Markdown editor
+  - Settings
+    - Options
+      - Name
+      - Description
+      - Private/Public
+      - Website
+      - Wiki
+        - Enabled/disabled
+        - Internal/external
+      - Issues
+        - Enabled/disabled
+        - Internal/external
+        - External supports url rewriting for better integration
+      - Enable/disable pull requests
+      - Transfer repository
+      - Delete wiki
+      - Delete repository
+    - Collaboration
+      - Read/write/admin
+    - Branches
+      - Default branch
+      - Branch protection
+    - Webhooks
+    - Git Hooks
+    - Deploy keys
 - Package Registries
   - Composer
   - Conan
@@ -269,10 +269,10 @@ You can try it out using [the online demo](https://try.gitea.io/).
 - A Raspberry Pi 3 is powerful enough to run Gitea for small workloads.
 - 2 CPU cores and 1GB RAM is typically sufficient for small teams/projects.
 - Gitea should be run with a dedicated non-root system account on UNIX-type systems.
-   - Note: Gitea manages the `~/.ssh/authorized_keys` file. Running Gitea as a regular user could break that user's ability to log in.
+  - Note: Gitea manages the `~/.ssh/authorized_keys` file. Running Gitea as a regular user could break that user's ability to log in.
 - [Git](https://git-scm.com/) version 2.0.0 or later is required.
-   - [Git Large File Storage](https://git-lfs.github.com/) will be available if enabled and if your Git version is >= 2.1.2
-   - Git commit-graph rendering will be enabled automatically if your Git version is >= 2.18
+  - [Git Large File Storage](https://git-lfs.github.com/) will be available if enabled and if your Git version is >= 2.1.2
+  - Git commit-graph rendering will be enabled automatically if your Git version is >= 2.18
 
 ## Browser Support
 
@@ -281,22 +281,22 @@ You can try it out using [the online demo](https://try.gitea.io/).
 
 ## Components
 
-* Web server framework: [Chi](http://github.com/go-chi/chi)
-* ORM: [XORM](https://xorm.io)
-* UI frameworks:
-  * [jQuery](https://jquery.com)
-  * [Fomantic UI](https://fomantic-ui.com)
-  * [Vue2](https://vuejs.org)
-  * and various components (see package.json)
-* Editors:
-  * [CodeMirror](https://codemirror.net)
-  * [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
-  * [Monaco Editor](https://microsoft.github.io/monaco-editor)
-* Database drivers:
-  * [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
-  * [github.com/lib/pq](https://github.com/lib/pq)
-  * [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
-  * [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
+- Web server framework: [Chi](http://github.com/go-chi/chi)
+- ORM: [XORM](https://xorm.io)
+- UI frameworks:
+  - [jQuery](https://jquery.com)
+  - [Fomantic UI](https://fomantic-ui.com)
+  - [Vue2](https://vuejs.org)
+  - and various components (see package.json)
+- Editors:
+  - [CodeMirror](https://codemirror.net)
+  - [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
+  - [Monaco Editor](https://microsoft.github.io/monaco-editor)
+- Database drivers:
+  - [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
+  - [github.com/lib/pq](https://github.com/lib/pq)
+  - [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
+  - [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
 
 ## Software and Service Support
 
diff --git a/docs/content/page/index.fr-fr.md b/docs/content/page/index.fr-fr.md
index b3828c7141..39d7ff8df3 100755
--- a/docs/content/page/index.fr-fr.md
+++ b/docs/content/page/index.fr-fr.md
@@ -19,43 +19,43 @@ Le but de ce projet est de fournir de la manière la plus simple, la plus rapide
 ## Fonctionalités
 
 - Tableau de bord de l'utilisateur
-    - Choix du contexte (organisation ou utilisateur actuel)
-    - Chronologie de l'activité
-        - Révisions (_Commits_)
-        - Tickets
-        - Demande d'ajout (_Pull request_)
-        - Création de dépôts
-    - Liste des dépôts
-    - Liste de vos organisations
-    - Liste des dépôts miroires
+  - Choix du contexte (organisation ou utilisateur actuel)
+  - Chronologie de l'activité
+    - Révisions (_Commits_)
+    - Tickets
+    - Demande d'ajout (_Pull request_)
+    - Création de dépôts
+  - Liste des dépôts
+  - Liste de vos organisations
+  - Liste des dépôts miroires
 - Tableau de bord des tickets
-    - Choix du contexte (organisation ou utilisateur actuel)
-    - Filtres
-        - Ouvert
-        - Fermé
-        - Vos dépôts
-        - Tickets assignés
-        - Vos tickets
-        - Dépôts
-    - Options de tri
-        - Plus vieux
-        - Dernière mise à jour
-        - Nombre de commentaires
+  - Choix du contexte (organisation ou utilisateur actuel)
+  - Filtres
+    - Ouvert
+    - Fermé
+    - Vos dépôts
+    - Tickets assignés
+    - Vos tickets
+    - Dépôts
+  - Options de tri
+    - Plus vieux
+    - Dernière mise à jour
+    - Nombre de commentaires
 - Tableau de bord des demandes d'ajout
-    - Identique au tableau de bord des tickets
+  - Identique au tableau de bord des tickets
 - Types de dépôt
-    - Miroire
-    - Normal
-    - Migré
+  - Miroire
+  - Normal
+  - Migré
 - Notifications (courriel et web)
-    - Lu
-    - Non lu
-    - Épinglé
+  - Lu
+  - Non lu
+  - Épinglé
 - Page d'exploration
-    - Utilisateurs
-    - Dépôts
-    - Organisations
-    - Moteur de recherche
+  - Utilisateurs
+  - Dépôts
+  - Organisations
+  - Moteur de recherche
 - Interface personnalisables
 - Fichiers publiques remplaçables (logo, css, etc)
 - Protection CSRF et XSS
@@ -63,183 +63,183 @@ Le but de ce projet est de fournir de la manière la plus simple, la plus rapide
 - Configuration des types et de la taille maximale des fichiers téléversés
 - Journalisation (_Log_)
 - Configuration
-    - Base de données
-        - MySQL
-        - PostgreSQL
-        - SQLite3
-        - MSSQL
-        - [TiDB](https://github.com/pingcap/tidb) (MySQL protocol)
-    - Fichier de configuration
-        - Voir [ici](https://github.com/go-gitea/gitea/blob/master/custom/conf/app.example.ini)
-    - Panel d'administration
-        - Statistiques
-        - Actions
-            - Suppression des comptes inactifs
-            - Suppression des dépôts archivés
-            - Suppression des dépôts pour lesquels il manque leurs fichiers
-            - Exécution du _garbage collector_ sur les dépôts
-            - Ré-écriture des clefs SSH
-            - Resynchronisation des hooks
-            - Recreation des dépôts manquants
-        - Status du server
-            - Temps de disponibilité
-            - Mémoire
-            - Nombre de goroutines
-            - et bien plus...
-         - Gestion des utilisateurs
-            - Recherche
-            - Tri
-            - Dernière connexion
-            - Méthode d'authentification
-            - Nombre maximum de dépôts
-            - Désactivation du compte
-            - Permissions d'administration
-            - Permission pour crééer des hooks
-            - Permission pour crééer des organisations
-            - Permission pour importer des dépôts
-        - Gestion des organisations
-            - Membres
-            - Équipes
-            - Avatar
-            - Hooks
-        - Gestion des depôts
-            - Voir toutes les informations pour un dépôt donné et gérer tous les dépôts
-        - Méthodes d'authentification
-            - OAuth
-            - PAM
-            - LDAP
-            - SMTP
-        - Visualisation de la configuration
-            - Tout ce que contient le fichier de configuration
-        - Alertes du système
-            - Quand quelque chose d'inattendu survient
-        - Surveillance
-            - Processus courrants
-            - Tâches CRON
-                - Mise à jour des dépôts miroires
-                - Vérification de l'état des dépôts
-                - Vérification des statistiques des dépôts
-                - Nettoyage des anciennes archives
-    - Variables d'environement
-    - Options de ligne de commande
+  - Base de données
+    - MySQL
+    - PostgreSQL
+    - SQLite3
+    - MSSQL
+    - [TiDB](https://github.com/pingcap/tidb) (MySQL protocol)
+  - Fichier de configuration
+    - Voir [ici](https://github.com/go-gitea/gitea/blob/master/custom/conf/app.example.ini)
+  - Panel d'administration
+    - Statistiques
+    - Actions
+      - Suppression des comptes inactifs
+      - Suppression des dépôts archivés
+      - Suppression des dépôts pour lesquels il manque leurs fichiers
+      - Exécution du _garbage collector_ sur les dépôts
+      - Ré-écriture des clefs SSH
+      - Resynchronisation des hooks
+      - Recreation des dépôts manquants
+    - Status du server
+      - Temps de disponibilité
+      - Mémoire
+      - Nombre de goroutines
+      - et bien plus...
+    - Gestion des utilisateurs
+      - Recherche
+      - Tri
+      - Dernière connexion
+      - Méthode d'authentification
+      - Nombre maximum de dépôts
+      - Désactivation du compte
+      - Permissions d'administration
+      - Permission pour crééer des hooks
+      - Permission pour crééer des organisations
+      - Permission pour importer des dépôts
+    - Gestion des organisations
+      - Membres
+      - Équipes
+      - Avatar
+      - Hooks
+    - Gestion des depôts
+      - Voir toutes les informations pour un dépôt donné et gérer tous les dépôts
+    - Méthodes d'authentification
+      - OAuth
+      - PAM
+      - LDAP
+      - SMTP
+    - Visualisation de la configuration
+      - Tout ce que contient le fichier de configuration
+    - Alertes du système
+      - Quand quelque chose d'inattendu survient
+    - Surveillance
+      - Processus courrants
+      - Tâches CRON
+        - Mise à jour des dépôts miroires
+        - Vérification de l'état des dépôts
+        - Vérification des statistiques des dépôts
+        - Nettoyage des anciennes archives
+  - Variables d'environement
+  - Options de ligne de commande
 - Internationalisation ([21 langues](https://github.com/go-gitea/gitea/tree/master/options/locale))
 - Courriel
-    - Notifications
-    - Confirmation d'inscription
-    - Ré-initialisation du mot de passe
+  - Notifications
+  - Confirmation d'inscription
+  - Ré-initialisation du mot de passe
 - Support de _reverse proxy_
-    - _subpaths_ inclus
+  - _subpaths_ inclus
 - Utilisateurs
-    - Profil
-        - Nom
-        - Prénom
-        - Courriel
-        - Site internet
-        - Date de création
-        - Abonnés et abonnements
-        - Organisations
-        - Dépôts
-        - Activité
-        - Dépôts suivis
-    - Paramètres
-        - Identiques au profil avec en plus les éléments ci-dessous
-        - Rendre l'adresse de courriel privée
-        - Avatar
-            - Gravatar
-            - Libravatar
-            - Personnalisé
-        - Mot de passe
-        - Courriels multiples
-        - Clefs SSH
-        - Applications connectées
-        - Authentification à double facteurs
-        - Identités OAuth2 attachées
-        - Suppression du compte
+  - Profil
+    - Nom
+    - Prénom
+    - Courriel
+    - Site internet
+    - Date de création
+    - Abonnés et abonnements
+    - Organisations
+    - Dépôts
+    - Activité
+    - Dépôts suivis
+  - Paramètres
+    - Identiques au profil avec en plus les éléments ci-dessous
+    - Rendre l'adresse de courriel privée
+    - Avatar
+      - Gravatar
+      - Libravatar
+      - Personnalisé
+    - Mot de passe
+    - Courriels multiples
+    - Clefs SSH
+    - Applications connectées
+    - Authentification à double facteurs
+    - Identités OAuth2 attachées
+    - Suppression du compte
 - Dépôts
-    - Clone à partir de SSH / HTTP / HTTPS
-    - Git LFS
-    - Suivre, Voter, Fork
-    - Voir les personnes qui suivent, les votes et les forks
-    - Code
-        - Navigation entre les branches
-        - Création ou téléversement de fichier depuis le navigateur
-        - URLs pour clôner le dépôt
-        - Téléchargement
-            - ZIP
-            - TAR.GZ
-        - Édition en ligne
-            - Éditeur Markdown
-            - Éditeur de texte
-                - Coloration syntaxique
-            - Visualisation des Diffs
-            - Visualisation
-            - Possibilité de choisir où sauvegarder la révision
-        - Historiques des fichiers
-        - Suppression de fichiers
-        - Voir le fichier brut
-    - Tickets
-        - Modèle de ticket
-        - Jalons
-        - Étiquettes
-        - Affecter des tickets
-        - Filtres
-            - Ouvert
-            - Ferme
-            - Personne assignée
-            - Créer par vous
-            - Qui vous mentionne
-        - Tri
-            - Plus vieux
-            - Dernière mise à jour
-            - Nombre de commentaires
-        - Moteur de recherche
-        - Commentaires
-        - Joindre des fichiers
-    - Demande d’ajout (_Pull request_)
-        - Les mêmes fonctionnalités que pour les tickets
-    - Révisions (_Commits_)
-        - Representation graphique des révisions
-        - Révisions par branches
-        - Moteur de recherche
-        - Voir les différences
-        - Voir les numéro de révision SHA
-        - Voir l'auteur
-        - Naviguer dans les fichiers d'une révision donnée
-    - Publication
-        - Pièces jointes
-        - Titre
-        - Contenu
-        - Suppression
-        - Définir comme une pré-publication
-        - Choix de la branche
-    - Wiki
-        - Import
-        - Éditeur Markdown
-    - Paramètres
-        - Options
-            - Nom
-            - Description
-            - Privé / Publique
-            - Site internet
-            - Wiki
-                - Activé / Désactivé
-                - Interne / externe
-            - Tickets
-                - Activé / Désactivé
-                - Interne / externe
-                - URL personnalisable pour une meilleur intégration avec un gestionnaire de tickets externe
-            - Activer / désactiver les demandes d'ajout (_Pull request_)
-            - Transfert du dépôt
-            - Suppression du wiki
-            - Suppression du dépôt
-        - Collaboration
-            - Lecture / Écriture / Administration
-        - Branches
-            - Branche par défaut
-            - Protection
-        - Webhooks
-        - Git hooks
-        - Clefs de déploiement
+  - Clone à partir de SSH / HTTP / HTTPS
+  - Git LFS
+  - Suivre, Voter, Fork
+  - Voir les personnes qui suivent, les votes et les forks
+  - Code
+    - Navigation entre les branches
+    - Création ou téléversement de fichier depuis le navigateur
+    - URLs pour clôner le dépôt
+    - Téléchargement
+      - ZIP
+      - TAR.GZ
+    - Édition en ligne
+      - Éditeur Markdown
+      - Éditeur de texte
+        - Coloration syntaxique
+      - Visualisation des Diffs
+      - Visualisation
+      - Possibilité de choisir où sauvegarder la révision
+    - Historiques des fichiers
+    - Suppression de fichiers
+    - Voir le fichier brut
+  - Tickets
+    - Modèle de ticket
+    - Jalons
+    - Étiquettes
+    - Affecter des tickets
+    - Filtres
+      - Ouvert
+      - Ferme
+      - Personne assignée
+      - Créer par vous
+      - Qui vous mentionne
+    - Tri
+      - Plus vieux
+      - Dernière mise à jour
+      - Nombre de commentaires
+    - Moteur de recherche
+    - Commentaires
+    - Joindre des fichiers
+  - Demande d’ajout (_Pull request_)
+    - Les mêmes fonctionnalités que pour les tickets
+  - Révisions (_Commits_)
+    - Representation graphique des révisions
+    - Révisions par branches
+    - Moteur de recherche
+    - Voir les différences
+    - Voir les numéro de révision SHA
+    - Voir l'auteur
+    - Naviguer dans les fichiers d'une révision donnée
+  - Publication
+    - Pièces jointes
+    - Titre
+    - Contenu
+    - Suppression
+    - Définir comme une pré-publication
+    - Choix de la branche
+  - Wiki
+    - Import
+    - Éditeur Markdown
+  - Paramètres
+    - Options
+      - Nom
+      - Description
+      - Privé / Publique
+      - Site internet
+      - Wiki
+        - Activé / Désactivé
+        - Interne / externe
+      - Tickets
+        - Activé / Désactivé
+        - Interne / externe
+        - URL personnalisable pour une meilleur intégration avec un gestionnaire de tickets externe
+      - Activer / désactiver les demandes d'ajout (_Pull request_)
+      - Transfert du dépôt
+      - Suppression du wiki
+      - Suppression du dépôt
+    - Collaboration
+      - Lecture / Écriture / Administration
+    - Branches
+      - Branche par défaut
+      - Protection
+    - Webhooks
+    - Git hooks
+    - Clefs de déploiement
 
 ## Configuration requise
 
@@ -253,21 +253,21 @@ Le but de ce projet est de fournir de la manière la plus simple, la plus rapide
 
 ## Composants
 
-* Framework web : [Chi](http://github.com/go-chi/chi)
-* ORM: [XORM](https://xorm.io)
-* Interface graphique :
-  * [jQuery](https://jquery.com)
-  * [Fomantic UI](https://fomantic-ui.com)
-  * [Vue2](https://vuejs.org)
-  * [CodeMirror](https://codemirror.net)
-  * [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
-  * [Monaco Editor](https://microsoft.github.io/monaco-editor)
-  * ... (package.json)
-* Connecteurs de base de données :
-  * [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
-  * [github.com/lib/pq](https://github.com/lib/pq)
-  * [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
-  * [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
+- Framework web : [Chi](http://github.com/go-chi/chi)
+- ORM: [XORM](https://xorm.io)
+- Interface graphique :
+  - [jQuery](https://jquery.com)
+  - [Fomantic UI](https://fomantic-ui.com)
+  - [Vue2](https://vuejs.org)
+  - [CodeMirror](https://codemirror.net)
+  - [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
+  - [Monaco Editor](https://microsoft.github.io/monaco-editor)
+  - ... (package.json)
+- Connecteurs de base de données :
+  - [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
+  - [github.com/lib/pq](https://github.com/lib/pq)
+  - [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
+  - [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
 
 ## Logiciels et services
 
diff --git a/docs/content/page/index.zh-cn.md b/docs/content/page/index.zh-cn.md
index d364edb2d7..1c94f8ea78 100644
--- a/docs/content/page/index.zh-cn.md
+++ b/docs/content/page/index.zh-cn.md
@@ -47,22 +47,22 @@ Gitea的首要目标是创建一个极易安装，运行非常快速，安装和
 
 ## 组件
 
-* Web框架： [Chi](http://github.com/go-chi/chi)
-* ORM: [XORM](https://xorm.io)
-* UI 框架：
-  * [jQuery](https://jquery.com)
-  * [Fomantic UI](https://fomantic-ui.com)
-  * [Vue2](https://vuejs.org)
-  * 更多组件参见 package.json
-* 编辑器：
-  * [CodeMirror](https://codemirror.net)
-  * [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
-  * [Monaco Editor](https://microsoft.github.io/monaco-editor)
-* 数据库驱动：
-  * [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
-  * [github.com/lib/pq](https://github.com/lib/pq)
-  * [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
-  * [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
+- Web框架： [Chi](http://github.com/go-chi/chi)
+- ORM: [XORM](https://xorm.io)
+- UI 框架：
+  - [jQuery](https://jquery.com)
+  - [Fomantic UI](https://fomantic-ui.com)
+  - [Vue2](https://vuejs.org)
+  - 更多组件参见 package.json
+- 编辑器：
+  - [CodeMirror](https://codemirror.net)
+  - [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
+  - [Monaco Editor](https://microsoft.github.io/monaco-editor)
+- 数据库驱动：
+  - [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
+  - [github.com/lib/pq](https://github.com/lib/pq)
+  - [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
+  - [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
 
 ## 软件及服务支持
 
diff --git a/docs/content/page/index.zh-tw.md b/docs/content/page/index.zh-tw.md
index 0c67ef0b28..3dde97a943 100644
--- a/docs/content/page/index.zh-tw.md
+++ b/docs/content/page/index.zh-tw.md
@@ -10,7 +10,7 @@ draft: false
 
 # 關於 Gitea
 
-Gitea 是一個可自行託管的 Git 服務。你可以拿 GitHub、Bitbucket 或 Gitlab 來比較看看。  
+Gitea 是一個可自行託管的 Git 服務。你可以拿 GitHub、Bitbucket 或 Gitlab 來比較看看。
 Gitea 是從 [Gogs](http://gogs.io) Fork 出來的，請閱讀部落格文章 [Gitea 公告](https://blog.gitea.io/2016/12/welcome-to-gitea/)以了解我們 Fork 的理由。
 
 ## 目標
@@ -269,19 +269,18 @@ Gitea 是從 [Gogs](http://gogs.io) Fork 出來的，請閱讀部落格文章 [G
 - Web 框架： [Chi](http://github.com/go-chi/chi)
 - ORM： [XORM](https://xorm.io)
 - UI 元件：
-  * [jQuery](https://jquery.com)
-  * [Fomantic UI](https://fomantic-ui.com)
-  * [Vue2](https://vuejs.org)
-  * [CodeMirror](https://codemirror.net)
-  * [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
-  * [Monaco Editor](https://microsoft.github.io/monaco-editor)
-  * ... (package.json)
+  - [jQuery](https://jquery.com)
+  - [Fomantic UI](https://fomantic-ui.com)
+  - [Vue2](https://vuejs.org)
+  - [CodeMirror](https://codemirror.net)
+  - [EasyMDE](https://github.com/Ionaru/easy-markdown-editor)
+  - [Monaco Editor](https://microsoft.github.io/monaco-editor)
+  - ... (package.json)
 - 資料庫驅動程式：
-  * [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
-  * [github.com/lib/pq](https://github.com/lib/pq)
-  * [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
-  * [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
-
+  - [github.com/go-sql-driver/mysql](https://github.com/go-sql-driver/mysql)
+  - [github.com/lib/pq](https://github.com/lib/pq)
+  - [github.com/mattn/go-sqlite3](https://github.com/mattn/go-sqlite3)
+  - [github.com/denisenkom/go-mssqldb](https://github.com/denisenkom/go-mssqldb)
 
 ## 軟體和服務支援