chore: format

Author: vinckr

docs/hydra/guides/oauth2-clients.mdx

@@ -137,14 +137,14 @@ OAuth2 client secret rotation allows you to change a client's secret without dow
 remains valid until you explicitly clean it up, allowing you to update all services using the client credentials without service
 interruption.
 
-### How secret rotation works
+##### How secret rotation works
 
 1. Rotate the secret: Generate a new secret for the client
 2. Both secrets work: Old and new secrets both authenticate until cleanup
 3. Update services: Update your applications to use the new secret
 4. Cleanup: Manually remove old rotated secrets once all services are updated
 
-### Rotate client secret
+##### Rotate client secret
 
 To rotate an OAuth2 client secret, use the following methods:
 
@@ -186,7 +186,7 @@ console.log("New secret:", client.client_secret)
 </Tabs>
 ````
 
-### Clear rotated secrets
+##### Clear rotated secrets
 
 Once all services have been updated to use the new secret, you can remove the old rotated secrets to revoke access using the old
 credentials:
@@ -219,7 +219,7 @@ await ory.deleteRotatedOAuth2ClientSecrets({
 </Tabs>
 ````
 
-### Secret rotation workflow example
+##### Secret rotation workflow example
 
 Here's a complete workflow for rotating a client secret:
 
@@ -248,12 +248,19 @@ curl -X DELETE "https://{project.slug}.projects.oryapis.com/admin/clients/$CLIEN
 # Old secret is now revoked
 ```
 
-:::tip Zero-downtime credential rotation Secret rotation enables zero-downtime credential updates. Both the old and new secrets
-remain valid until you manually clean up the rotated secrets, allowing you to update all your services without service
-interruption. :::
+:::tip Zero-downtime credential rotation
 
-:::warning Security best practice Rotated secrets remain valid indefinitely until you explicitly clean them up. Always remove old
-rotated secrets once your migration is complete to ensure that compromised credentials cannot be used. :::
+Secret rotation enables zero-downtime credential updates. Both the old and new secrets remain valid until you manually clean up
+the rotated secrets, allowing you to update all your services without service interruption.
+
+:::
+
+:::warning Security best practice
+
+Rotated secrets remain valid indefinitely until you explicitly clean them up. Always remove old rotated secrets once your
+migration is complete to ensure that compromised credentials cannot be used.
+
+:::
 
 ## Delete OAuth2 client