Use docusaurus warning/note syntax instead markdown

docs/usage/authentication.md

@@ -348,4 +348,6 @@ If set `ENABLE_REVERSE_PROXY_FULL_NAME=true`, a user full name expected in `X-WE
 
 You can also limit the reverse proxy's IP address range with `REVERSE_PROXY_TRUSTED_PROXIES` which default value is `127.0.0.0/8,::1/128`. By `REVERSE_PROXY_LIMIT`, you can limit trusted proxies level.
 
-Notice: Reverse Proxy Auth doesn't support the API. You still need an access token or basic auth to make API requests.
+:::note
+Reverse Proxy Auth doesn't support the API. You still need an access token or basic auth to make API requests.
+:::

docs/usage/code-owners.md

@@ -32,7 +32,7 @@ Regexp can start with `!` for negative rules - match all files except specified.
 
 Example file:
 
-```
+```bash
 .*\\.go @user1 @user2 # This is comment
 
 # Comment too

docs/usage/linked-references.md

@@ -197,5 +197,7 @@ _The last section is for repositories with external issue trackers that use alph
 
 _**-**: not applicable._
 
-Note: automatic references between repositories with different types of issues (external vs. internal) are not fully supported
+:::note
+Automatic references between repositories with different types of issues (external vs. internal) are not fully supported
 and may render invalid links.
+:::

docs/usage/multi-factor-authentication.md

@@ -28,8 +28,10 @@ This interface does not support MFA, and trying to use a password normally will
 If SSH is not an option for Git operations, an access token can be generated within the "Applications" tab of the user settings page.
 This access token can be used as if it were a password in order to allow the Git CLI to function over HTTP.
 
-> **Warning** - By its very nature, an access token sidesteps the security benefits of MFA.
-> It must be kept secure and should only be used as a last resort.
+:::warning
+By its very nature, an access token sidesteps the security benefits of MFA.
+It must be kept secure and should only be used as a last resort.
+:::
 
 The Gitea API supports providing the relevant TOTP password in the `X-Gitea-OTP` header, as described in [API Usage](development/api-usage.md).
 This should be used instead of an access token where possible.

docs/usage/packages/container.md

@@ -57,7 +57,9 @@ For example, these are all valid image names for the owner `testuser`:
 
 `gitea.example.com/testuser/my/image`
 
-**NOTE:** The registry only supports case-insensitive tag names. So `image:tag` and `image:Tag` get treated as the same image and tag.
+:::note
+The registry only supports case-insensitive tag names. So `image:tag` and `image:Tag` get treated as the same image and tag.
+:::
 
 ## Push an image
 

docs/usage/repo-mirror.md

@@ -39,7 +39,9 @@ For an existing remote repository, you can set up pull mirroring as follows:
 
 The repository now gets mirrored periodically from the remote repository. You can force a sync by selecting **Synchronize Now** in the repository settings.
 
-:exclamation::exclamation: **NOTE:** You can only set up pull mirroring for repos that don't exist yet on your instance. Once the repo is created, you can't convert it into a pull mirror anymore. :exclamation::exclamation:
+:::warning
+:exclamation::exclamation: You can only set up pull mirroring for repos that don't exist yet on your instance. Once the repo is created, you can't convert it into a pull mirror anymore. :exclamation::exclamation:
+:::
 
 ## Pushing to a remote repository
 
@@ -52,7 +54,9 @@ For an existing repository, you can set up push mirroring as follows:
 
 The repository now gets mirrored periodically to the remote repository. You can force a sync by selecting **Synchronize Now**. In case of an error a message displayed to help you resolve it.
 
-:exclamation::exclamation: **NOTE:** This will force push to the remote repository. This will overwrite any changes in the remote repository! :exclamation::exclamation:
+:::warning
+:exclamation::exclamation: This will force push to the remote repository. This will overwrite any changes in the remote repository! :exclamation::exclamation:
+:::
 
 ### Setting up a push mirror from Gitea to GitHub
 

docs/usage/template-repositories.md

@@ -32,7 +32,7 @@ Gitea uses [gobwas/glob](https://github.com/gobwas/glob) for its glob syntax. It
 
 All paths are relative to the base of the repository
 
-```gitignore
+```bash
 # Expand all .go files, anywhere in the repository
 **.go
 

docs/usage/webhooks.md

@@ -34,12 +34,14 @@ All event pushes are POST requests. The methods currently supported are:
 
 ### Event information
 
-**WARNING**: The `secret` field in the payload is deprecated as of Gitea 1.13.0 and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755
+:::warning
+The `secret` field in the payload is deprecated as of Gitea 1.13.0 and will be removed in 1.14.0: https://github.com/go-gitea/gitea/issues/11755
+:::
 
 The following is an example of event information that will be sent by Gitea to
 a Payload URL:
 
-```
+```http
 X-GitHub-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
 X-GitHub-Event: push
 X-Gogs-Delivery: f6266f16-1bf3-46a5-9ea4-602e06ead473
@@ -133,7 +135,7 @@ In your repository Settings, under Webhooks, Setup a Gitea webhook as follows:
 
 Now on your server create the php file webhook.php
 
-```
+```php
 <?php
 
 $secret_key = '123';