ci: apply automated fixes (attempt 2/3)

Author: autofix-ci[bot]

pages/docs/integrations/azure-ad-b2c/sso-saml/+Page.mdx

@@ -128,8 +128,7 @@ For this step, we assume you have an app running locally (i.e. on localhost:3000
    1. Access your ngrok tunnel via your copied URL
    1. You should be prompted to log in or sign up
 
-   ![img/5-3.png](../img/5-3.png)
-   4. After login, you should be able to see the application
+   ![img/5-3.png](../img/5-3.png) 4. After login, you should be able to see the application
 
 ## Bonus: Update your Azure AD B2C custom policies to support the password reset flow {#bonus}
 

pages/docs/k8s/guides/endpoint-types/+Page.mdx

@@ -92,7 +92,8 @@ policy:
 on_http_request: - actions: - type: forward-internal
 config:
 url: https://example-service.internal:8443
-```
+
+````
 </TabItem>
 
 </Tabs>
@@ -138,7 +139,8 @@ on_http_request: - actions: - type: forward-internal
 config:
 url: tcp://example-service.internal:8000
 bindings: - public
-```
+````
+
 </TabItem>
 
 </Tabs>

pages/docs/k8s/guides/how-to/basic-auth/+Page.mdx

@@ -105,7 +105,8 @@ config:
 realm: sample-realm
 credentials: - user:password1 - admin:password2
 enforce: true
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on an `Ingress`
 
@@ -129,7 +130,8 @@ service:
 name: example-service
 port:
 number: 80
-```
+````
+
 </TabItem>
 <TabItem value="gateway-api" label="Gateway API">
 💡 Gateway API resources do not natively support Basic Authentication, but they can be extended using a traffic policy.
@@ -150,7 +152,8 @@ config:
 realm: sample-realm
 credentials: - user:password1 - admin:password2
 enforce: true
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on a `Gateway`
 
@@ -172,7 +175,8 @@ listeners: - name: example-hostname
 hostname: "example-hostname.ngrok.io"
 port: 443
 protocol: HTTPS
-```
+````
+
 </TabItem>
 
 </Tabs>

pages/docs/k8s/guides/how-to/circuit-breaking/+Page.mdx

@@ -101,7 +101,8 @@ volume_threshold: 1
 window_duration: 60s
 tripped_duration: 2m
 enforce: true
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on an `Ingress`
 
@@ -125,7 +126,8 @@ service:
 name: example-service
 port:
 number: 80
-```
+````
+
 </TabItem>
 <TabItem value="gateway-api" label="Gateway API">
 💡 Gateway API resources do not natively support circuit breaking, but they can be extended using a traffic policy.
@@ -148,7 +150,8 @@ volume_threshold: 1
 window_duration: 60s
 tripped_duration: 2m
 enforce: true
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on a `Gateway`
 
@@ -170,7 +173,8 @@ listeners: - name: example-hostname
 hostname: "example-hostname.ngrok.io"
 port: 443
 protocol: HTTPS
-```
+````
+
 </TabItem>
 
 </Tabs>

pages/docs/k8s/guides/how-to/compress-response/+Page.mdx

@@ -108,7 +108,8 @@ on_http_response: - expressions: - req.url.path.startsWith('/api/')
 actions: - type: compress-response
 config:
 algorithms: - gzip - br - deflate - compress
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on an `Ingress`
 
@@ -132,7 +133,8 @@ service:
 name: example-service
 port:
 number: 80
-```
+````
+
 </TabItem>
 <TabItem value="gateway-api" label="Gateway API">
 💡 Gateway API resources do not natively support response compression, but they can be extended using a traffic policy.
@@ -152,7 +154,8 @@ on_http_response: - expressions: - req.url.path.startsWith('/api/')
 actions: - type: compress-response
 config:
 algorithms: - gzip - br - deflate - compress
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on a `Gateway`
 
@@ -174,7 +177,8 @@ listeners: - name: example-hostname
 hostname: "example-hostname.ngrok.io"
 port: 443
 protocol: HTTPS
-```
+````
+
 </TabItem>
 
 </Tabs>

pages/docs/k8s/guides/how-to/deny-requests/+Page.mdx

@@ -95,7 +95,8 @@ on_http_request: - expressions: - conn.client_ip.geo.location.is_eu == false
 actions: - type: deny
 config:
 status_code: 403
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on an `Ingress`
 
@@ -119,7 +120,8 @@ service:
 name: example-service
 port:
 number: 80
-```
+````
+
 </TabItem>
 <TabItem value="gateway-api" label="Gateway API">
 💡 Gateway API resources do not natively support request denial configuration, but they can be extended using a traffic policy.
@@ -139,7 +141,8 @@ on_http_request: - expressions: - conn.client_ip.geo.location.is_eu == false
 actions: - type: deny
 config:
 status_code: 403
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on a `Gateway`
 
@@ -161,7 +164,8 @@ listeners: - name: example-hostname
 hostname: "example-hostname.ngrok.io"
 port: 443
 protocol: HTTPS
-```
+````
+
 </TabItem>
 
 </Tabs>

pages/docs/k8s/guides/how-to/jwt-validation/+Page.mdx

@@ -153,7 +153,8 @@ allowed_algorithms: - RS256 - ES256
 keys:
 sources:
 additional_jkus: - https://example.com/issuer/jku
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on an `Ingress`
 
@@ -177,7 +178,8 @@ service:
 name: example-service
 port:
 number: 80
-```
+````
+
 </TabItem>
 <TabItem value="gateway-api" label="Gateway API">
 💡 Gateway API resources do not natively support JWT validation, but they can be extended using a traffic policy.
@@ -211,7 +213,8 @@ allowed_algorithms: - RS256 - ES256
 keys:
 sources:
 additional_jkus: - https://example.com/issuer/jku
-```
+
+````
 
     ### 2. Use the `NgrokTrafficPolicy` on a `Gateway`
 
@@ -233,7 +236,8 @@ listeners: - name: example-hostname
 hostname: "example-hostname.ngrok.io"
 port: 443
 protocol: HTTPS
-```
+````
+
 </TabItem>
 
 </Tabs>