chore: fix dingtalk formatting (#878)

Author: tomekpapiernik

docs/guides/social-signin/dingtalk.mdx

@@ -10,29 +10,30 @@ Follow these steps to add DingTalk as a social sign-in provider to your Ory Clou
 1. [Create a DingTalk OAuth app](https://open-dev.dingtalk.com/fe/app#/corp/app).
 2. In the created app, set the redirect URI to:
 
-```shell
-https://<ory-cloud-project-slug>.projects.oryapis.com/self-service/methods/oidc/callback/dingtalk
-```
+  ```shell
+  https://<ory-cloud-project-slug>.projects.oryapis.com/self-service/methods/oidc/callback/dingtalk
+  ```
 
 <a name="mapping"></a>
+
 3. Create a Jsonnet code snippet to map the desired claims to the Ory Identity schema.
 Specific information [DingTalk's User API](https://open.dingtalk.com/document/orgapp-server/dingtalk-retrieve-user-information) can be viewed.
 
-```json
-local claims = std.extVar('claims');
-{
-  identity: {
-    traits: {
-      // Allowing unverified email addresses enables account
-      // enumeration attacks, especially if the value is used for
-      // e.g. verification or as a password login identifier.
-      //
-      // Therefore we only return the email if it (a) exists by DingTalk.
-      [if "email" in claims then "email" else null]: claims.email,
+  ```json
+  local claims = std.extVar('claims');
+  {
+    identity: {
+      traits: {
+        // Allowing unverified email addresses enables account
+        // enumeration attacks, especially if the value is used for
+        // e.g. verification or as a password login identifier.
+        //
+        // Therefore we only return the email if it (a) exists by DingTalk.
+        [if "email" in claims then "email" else null]: claims.email,
+      },
     },
-  },
-}
-```
+  }
+  ```
 
 ```mdx-code-block
 import JsonnetWarning from '../../_common/jsonnetwarning.mdx'
@@ -43,43 +44,49 @@ import JsonnetWarning from '../../_common/jsonnetwarning.mdx'
 4. Encode the Jsonnet snippet with [Base64](https://www.base64encode.org/) or host it under an URL accessible to Ory Cloud.
 5. Download the Identity Service config from your Ory Cloud project and save it to a file:
 
-```shell
-## List all available projects
-ory list projects
+  ```shell
+  ## List all available projects
+  ory list projects
 
-## Get config
-ory get identity-config <project-id> --format yaml > identity-config.yaml
-```
+  ## Get config
+  ory get identity-config <project-id> --format yaml > identity-config.yaml
+  ```
 
 <a name="config"></a>
+
 6. Add the social sign-in provider configuration to the downloaded config. Add the Jsonnet snippet with mappings as a Base64
    string or provide an URL to the file.
 
-```yaml
-selfservice:
-  methods:
-    oidc:
-      enabled: true
-      config:
-        providers:
-          - id: dingtalk # this is `<provider-id>` in the Authorization callback URL. DO NOT CHANGE IT ONCE SET!
-            provider: dingtalk
-            client_id: .... # Replace this with the OAuth2 Client ID provided by DingTalk
-            client_secret: .... # Replace this with the OAuth2 Client Secret provided by DingTalk
-            mapper_url: 'base64://<YOUR_BASE64_ENCODED_JSONNET_HERE>'
-            # Alternatively, use an URL:
-            # mapper_url: https://storage.googleapis.com/abc-cde-prd/9cac9717f007808bf17f22ce7f4295c739604b183f05ac4afb4
-            scope:
-              # DingTalk supports only the `openid` or `openid corpid` scopes. For a basic setup, use the `openid` scope.
-              # To learn more about the scopes available for DingTalk, read the [related documentation](https://open.dingtalk.com/document/orgapp-server/tutorial-obtaining-user-personal-information).
-              - openid
-```
+  ```yaml
+  selfservice:
+    methods:
+      oidc:
+        enabled: true
+        config:
+          providers:
+            - id: dingtalk # this is `<provider-id>` in the Authorization callback URL. DO NOT CHANGE IT ONCE SET!
+              provider: dingtalk
+              client_id: .... # Replace this with the OAuth2 Client ID provided by DingTalk
+              client_secret: .... # Replace this with the OAuth2 Client Secret provided by DingTalk
+              mapper_url: 'base64://<YOUR_BASE64_ENCODED_JSONNET_HERE>'
+              # Alternatively, use an URL:
+              # mapper_url: https://storage.googleapis.com/abc-cde-prd/9cac9717f007808bf17f22ce7f4295c739604b183f05ac4afb4
+              scope:
+                # DingTalk supports only the `openid` or `openid corpid` scopes. For a basic setup, use the `openid` scope.
+                - openid
+  ```
+
+  :::info
+
+  To learn more about the scopes available for DingTalk, read the [related documentation](https://open.dingtalk.com/document/orgapp-server/tutorial-obtaining-user-personal-information).
+
+  :::
 
 7. Update the Ory Cloud Identity Service configuration using the file you worked with:
 
-```shell
-ory update identity-config <project-id> --file updated_config.yaml
-```
+  ```shell
+  ory update identity-config <project-id> --file updated_config.yaml
+  ```
 
 ## Configuration for Self-hosted Instances
 
@@ -88,9 +95,9 @@ Follow these steps to add DingTalk as a social sign-in provider when self-hostin
 1. [Create a DingTalk OAuth app](https://open-dev.dingtalk.com/fe/app#/corp/app).
 2. Set the redirect URI to URL that follows this pattern:
 
-```shell
-http(s)://<domain-of-ory-kratos>:<public-port>/self-service/methods/oidc/callback/dingtalk
-```
+  ```shell
+  http(s)://<domain-of-ory-kratos>:<public-port>/self-service/methods/oidc/callback/dingtalk
+  ```
 
 3. Create a [Jsonnet code snippet to map the desired claims to the Ory Identity schema](#mapping).
 4. Encode the Jsonnet snippet with [Base64](https://www.base64encode.org/) or store it in a location available to your Ory Kratos