Need to explicitly add {/* prettier-ignore */}

Author: maartenba

src/content/docs/bff/fundamentals/apis/local.mdx

@@ -98,57 +98,59 @@ Additionally, API endpoints should handle scenarios where the session has expire
 
 Duende.BFF can automate the pre-processing step of requiring the custom anti-forgery header. To do so, first add the BFF middleware to the pipeline, and then decorate your endpoints to indicate that they should receive BFF pre-processing.
 
+{/* prettier-ignore */}
 <Steps>
 
-1. **Add Middleware to the pipeline**
+1.  **Add Middleware to the pipeline**
 
-   Add the BFF middleware to the pipeline by calling `UseBff`. Note that the middleware must be placed before the authorization middleware, but after routing.
+    Add the BFF middleware to the pipeline by calling `UseBff`. Note that the middleware must be placed before the authorization middleware, but after routing.
 
-   ```csharp {5}
-   // Program.cs
-   app.UseAuthentication();
-   app.UseRouting();
+    ```csharp {5}
+    // Program.cs
+    app.UseAuthentication();
+    app.UseRouting();
 
-   app.UseBff();
+    app.UseBff();
 
-   app.UseAuthorization();
+    app.UseAuthorization();
 
-   // map endpoints
-   ```
+    // map endpoints
+    ```
 
-2. **Decorate Endpoints**
+2.  **Decorate Endpoints**
 
-    Endpoints that require the pre- and post-processing described above must be decorated with a call to `AsBffApiEndpoint()`.
+        Endpoints that require the pre- and post-processing described above must be decorated with a call to `AsBffApiEndpoint()`.
 
-    For Minimal API endpoints, you can apply BFF pre- and post-processing when they are mapped.
+        For Minimal API endpoints, you can apply BFF pre- and post-processing when they are mapped.
 
-    ```csharp {4-5}
-    app.MapPost("/foo", context => {
-        // ...
-    })
-        .RequireAuthorization()  // no anonymous access
-        .AsBffApiEndpoint();     // BFF pre/post processing
-    ```
+        ```csharp {4-5}
+        app.MapPost("/foo", context => {
+            // ...
+        })
+            .RequireAuthorization()  // no anonymous access
+            .AsBffApiEndpoint();     // BFF pre/post processing
+        ```
 
-    For MVC controllers, you can similarly apply BFF pre- and post-processing to controller actions when they are mapped.
+        For MVC controllers, you can similarly apply BFF pre- and post-processing to controller actions when they are mapped.
 
-    ```csharp {2-3}
-    app.MapControllers()
-        .RequireAuthorization()  // no anonymous access
-        .AsBffApiEndpoint();     // BFF pre/post processing
-    ```
+        ```csharp {2-3}
+        app.MapControllers()
+            .RequireAuthorization()  // no anonymous access
+            .AsBffApiEndpoint();     // BFF pre/post processing
+        ```
 
-    Alternatively, you can apply the `[BffApi]` attribute directly to the controller or action.
+        Alternatively, you can apply the `[BffApi]` attribute directly to the controller or action.
 
-    ```csharp {2}
-    [Route("myApi")]
-    [BffApi]
-    public class MyApiController : ControllerBase
-    {
-        // ...
-    }
-    ```
-</Steps>
+        ```csharp {2}
+        [Route("myApi")]
+        [BffApi]
+        public class MyApiController : ControllerBase
+        {
+            // ...
+        }
+        ```
+
+    </Steps>
 
 ### Disabling Anti-forgery Protection
 

src/content/docs/bff/upgrading/bff-v2-to-v3.md

@@ -1,9 +1,9 @@
 ---
 title: "Duende BFF Security Framework v2.x to v3.0"
 description: Guide for upgrading Duende BFF Security Framework from version 2.x to version 3.0, including migration steps for custom implementations and breaking changes.
-order: 29
 sidebar:
   label: v2.x → v3.0
+  order: 30
 redirect_from:
   - /bff/v2/upgrading/bff_v2_to_v3/
   - /bff/v3/upgrading/bff_v2_to_v3/

src/content/docs/identityserver/upgrades/identityserver4-to-duende-identityserver-v7.mdx

@@ -15,6 +15,7 @@ IdentityServer4 reached its end of life (EOL) on December 13, 2022. It is strong
 Depending on your current version of IdentityServer4, different steps may be required.
 You can determine the version of IdentityServer4 by running the `dotnet list` command at the root of your IdentityServer host project, or using NuGet tooling in Visual Studio or JetBrains Rider.
 
+{/* prettier-ignore */}
 <Tabs>
   <TabItem label="Windows">
     <Code
@@ -164,6 +165,7 @@ Make sure to verify the database migrations as part of your IdentityServer4 upgr
 
 For the operational data, you can create and apply an Entity Framework Core migration that targets the `PersistedGrantDbContext` database context.
 
+{/* prettier-ignore */}
 <Steps>
 
 1. Create the migration:
@@ -183,6 +185,7 @@ For the operational data, you can create and apply an Entity Framework Core migr
 For your configuration data, the conversation from the old schema to the new will need to be performed by applying a custom SQL script.
 We'll start with creating a migration that targets the `ConfigurationDbContext` database context:
 
+{/* prettier-ignore */}
 <Steps>
 
 1. Create the migration:
@@ -416,6 +419,7 @@ In this section, we'll look at updating the database schema based on the stores
 You'll need to create two database migrations that update the database schema: one that targets the `PersistedGrantDbContext` (for operational data), and one that targets the `ConfigurationDbContext` (for configuration data).
 Note that you may want to change the database migration paths in the examples below to match your project structure.
 
+{/* prettier-ignore */}
 <Steps>
 
 1. Create the migrations for the operational and configuration database context: