docs: Fix section nesting in webhook.md

docs/operator-manual/webhook.md

@@ -21,14 +21,14 @@ arbitrary value in the secret. This value will be used when configuring the webh
 
 To prevent DDoS attacks with unauthenticated webhook events (the `/api/webhook` endpoint currently lacks rate limiting protection), it is recommended to limit the payload size. You can achieve this by configuring the `argocd-cm` ConfigMap with the `webhook.maxPayloadSizeMB` attribute. The default value is 50MB.
 
-## Github
+### Github
 
 ![Add Webhook](../assets/webhook-config.png "Add Webhook")
 
 !!! note
     When creating the webhook in GitHub, the "Content type" needs to be set to "application/json". The default value "application/x-www-form-urlencoded" is not supported by the library used to handle the hooks
 
-## Azure DevOps
+### Azure DevOps
 
 ![Add Webhook](../assets/azure-devops-webhook-config.png "Add Webhook")
 
@@ -122,4 +122,4 @@ For public repositories, the Argo CD webhook handler uses a no-auth client for t
 For private repositories, the Argo CD webhook handler searches for a valid repository OAuth token for the HTTP/HTTPS URL.
 The webhook handler uses this OAuth token to make the API request to the originating server.
 If the Argo CD webhook handler cannot find a matching repository credential, the list of changed files would remain empty.
-If errors occur during the callback, the list of changed files will be empty.
+If errors occur during the callback, the list of changed files will be empty.