Reformat docs (#13897)

Co-authored-by: 6543 <6543@obermui.de>
Co-authored-by: Lauris BH <lauris@nix.lv>

docs/content/doc/advanced/signing.en-us.md

@@ -15,6 +15,10 @@ menu:
 
 # GPG Commit Signatures
 
+**Table of Contents**
+
+{{< toc >}}
+
 Gitea will verify GPG commit signatures in the provided tree by
 checking if the commits are signed by a key within the gitea database,
 or if the commit matches the default key for git.
@@ -36,10 +40,10 @@ this requires git >= 2.0.0.
 
 There are a number of places where Gitea will generate commits itself:
 
-* Repository Initialisation
-* Wiki Changes
-* CRUD actions using the editor or the API
-* Merges from Pull Requests
+- Repository Initialisation
+- Wiki Changes
+- CRUD actions using the editor or the API
+- Merges from Pull Requests
 
 Depending on configuration and server trust you may want Gitea to
 sign these commits.
@@ -78,12 +82,12 @@ MERGES = pubkey, twofa, basesigned, commitssigned
 The first option to discuss is the `SIGNING_KEY`. There are three main
 options:
 
-* `none` - this prevents Gitea from signing any commits
-* `default` - Gitea will default to the key configured within
-`git config`
-* `KEYID` - Gitea will sign commits with the gpg key with the ID
-`KEYID`. In this case you should provide a `SIGNING_NAME` and
-`SIGNING_EMAIL` to be displayed for this key.
+- `none` - this prevents Gitea from signing any commits
+- `default` - Gitea will default to the key configured within
+  `git config`
+- `KEYID` - Gitea will sign commits with the gpg key with the ID
+  `KEYID`. In this case you should provide a `SIGNING_NAME` and
+  `SIGNING_EMAIL` to be displayed for this key.
 
 The `default` option will interrogate `git config` for
 `commit.gpgsign` option - if this is set, then it will use the results
@@ -99,10 +103,10 @@ ideal UI and therefore subject to change.
 This option determines whether Gitea should sign the initial commit
 when creating a repository. The possible values are:
 
-* `never`: Never sign
-* `pubkey`: Only sign if the user has a public key
-* `twofa`: Only sign if the user logs in with two factor authentication
-* `always`: Always sign
+- `never`: Never sign
+- `pubkey`: Only sign if the user has a public key
+- `twofa`: Only sign if the user logs in with two factor authentication
+- `always`: Always sign
 
 Options other than `never` and `always` can be combined as a comma
 separated list.
@@ -112,11 +116,11 @@ separated list.
 This options determines if Gitea should sign commits to the Wiki.
 The possible values are:
 
-* `never`: Never sign
-* `pubkey`: Only sign if the user has a public key
-* `twofa`: Only sign if the user logs in with two factor authentication
-* `parentsigned`: Only sign if the parent commit is signed.
-* `always`: Always sign
+- `never`: Never sign
+- `pubkey`: Only sign if the user has a public key
+- `twofa`: Only sign if the user logs in with two factor authentication
+- `parentsigned`: Only sign if the parent commit is signed.
+- `always`: Always sign
 
 Options other than `never` and `always` can be combined as a comma
 separated list.
@@ -126,11 +130,11 @@ separated list.
 This option determines if Gitea should sign commits from the web
 editor or API CRUD actions. The possible values are:
 
-* `never`: Never sign
-* `pubkey`: Only sign if the user has a public key
-* `twofa`: Only sign if the user logs in with two factor authentication
-* `parentsigned`: Only sign if the parent commit is signed.
-* `always`: Always sign
+- `never`: Never sign
+- `pubkey`: Only sign if the user has a public key
+- `twofa`: Only sign if the user logs in with two factor authentication
+- `parentsigned`: Only sign if the parent commit is signed.
+- `always`: Always sign
 
 Options other than `never` and `always` can be combined as a comma
 separated list.
@@ -140,14 +144,14 @@ separated list.
 This option determines if Gitea should sign merge commits from PRs.
 The possible options are:
 
-* `never`: Never sign
-* `pubkey`: Only sign if the user has a public key
-* `twofa`: Only sign if the user logs in with two factor authentication
-* `basesigned`: Only sign if the parent commit in the base repo is signed.
-* `headsigned`: Only sign if the head commit in the head branch is signed.
-* `commitssigned`: Only sign if all the commits in the head branch to the merge point are signed.
-* `approved`: Only sign approved merges to a protected branch.
-* `always`: Always sign
+- `never`: Never sign
+- `pubkey`: Only sign if the user has a public key
+- `twofa`: Only sign if the user logs in with two factor authentication
+- `basesigned`: Only sign if the parent commit in the base repo is signed.
+- `headsigned`: Only sign if the head commit in the head branch is signed.
+- `commitssigned`: Only sign if all the commits in the head branch to the merge point are signed.
+- `approved`: Only sign approved merges to a protected branch.
+- `always`: Always sign
 
 Options other than `never` and `always` can be combined as a comma
 separated list.
@@ -156,12 +160,12 @@ separated list.
 
 The public key used to sign Gitea's commits can be obtained from the API at:
 
-```
+```sh
 /api/v1/signing-key.gpg
 ```
 
 In cases where there is a repository specific key this can be obtained from:
 
-```
+```sh
 /api/v1/repos/:username/:reponame/signing-key.gpg
 ```