Fix formatting

Author: maartenba

src/content/docs/accesstokenmanagement/advanced/client-credentials.mdx

@@ -55,7 +55,8 @@ You can add token client definitions to your host while configuring the DotNet s
             client.Resource = "urn:invoices";
     });`}/>
     </TabItem>
-</Tabs>    
+</Tabs>
+
 You can set the following options:
 
 * `TokenEndpoint` - URL of the OAuth token endpoint where this token client requests tokens from

src/content/docs/bff/extensibility/management/diagnostics.md

@@ -23,6 +23,5 @@ For example, you could take whatever actions you need before normal processing o
 public Task ProcessRequestAsync(HttpContext context, CancellationToken ct)
 {
     // Custom logic here
-
 }
 ```

src/content/docs/bff/extensibility/management/user.md

@@ -34,7 +34,6 @@ There are several ways how you can enrich the claims for a specific user.
 The most robust way would be to implement a custom `IClaimsTransformation`. 
 
 ```csharp
-
 services.AddScoped<IClaimsTransformation, CustomClaimsTransformer>();
 
 public class CustomClaimsTransformer : IClaimsTransformation

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

@@ -111,23 +111,23 @@ In Duende.BFF version 3, use the `MapRemoteBffApiEndpoint` method with the `Requ
 
 Remote APIs sometimes allow anonymous access, but usually require an access token, and the type of access token (user or client) will vary as well. You can specify access token requirements via the `WithAccessToken` extension method. Its `RequiredTokenType` parameter has three options:
 
-* `None`
+* **`None`**
 
     No token is required.
 
-* `User`
+* **`User`**
 
     A valid user access token is required and will be forwarded to the remote API. A user access token is an access token obtained during an OIDC flow (or subsequent refresh), and is associated with a particular user. User tokens are obtained when the user initially logs in, and will be automatically refreshed using a refresh token when they expire.
 
-* `Client`
+* **`Client`**
 
     A valid client access token is required and will be forwarded to the remote API. A client access token is an access token obtained through the client credentials flow, and is associated with the client application, not any particular user. Client tokens can be obtained even if the user is not logged in.
 
-* `UserOrClient`
+* **`UserOrClient`**
 
     Either a valid user access token or a valid client access token (as fallback) is required and will be forwarded to the remote API.
 
-* `UserOrNone`
+* **`UserOrNone`**
 
     A valid user access token will be forwarded to the remote API when logged in. No access token will be sent when not logged in, and no OIDC flow is challenged to get an access token.
 

src/content/docs/bff/fundamentals/multi-frontend/index.mdx

@@ -140,7 +140,6 @@ frontends.Remove(name);
 A frontend can define its own API surface, by specifying remote APIs.
 
 ```csharp
-
 var frontend = new BffFrontend(BffFrontendName.Parse("frontend1"))
    .WithRemoteApis(
       // map the local path /path to the remote api
@@ -161,7 +160,6 @@ See the topic on [Token Management](../tokens.md) for more information about the
 When deploying a multi-frontend BFF, it makes most sense to have the frontend's configured with an `index.html` file that is retrieved from a Content Delivery Network (CDN). 
 
 ```csharp
-
 var frontend = new BffFrontend(BffFrontendName.Parse("frontend1"))
    .WithIndexHtml(new Uri("https://my_cdn/some_app/index.html"))
 ```

src/content/docs/bff/fundamentals/session/handlers.mdx

@@ -32,7 +32,6 @@ A call `BffBuilder.ConfigureOpenIdConnect()` will make sure that:
 Below is an example on how to configure the BFF's authentication pipeline. 
 
 ```csharp
-
 services.AddBff()
     .ConfigureOpenIdConnect(options =>
     {

src/content/docs/bff/getting-started/multi-frontend.mdx

@@ -26,14 +26,14 @@ Multi-frontend support is available in Duende.BFF v4 and later. The v3-style of
 
 ### 1. Create A New ASP.NET Core Project
 
-```sh
+```bash title="Terminal"
 dotnet new web -n MyMultiBffApp
 cd MyMultiBffApp
 ```
 
 ### 2. Add The Duende.BFF NuGet Package
 
-```sh
+```bash title="Terminal"
 dotnet add package Duende.BFF
 ```
 
@@ -42,50 +42,51 @@ dotnet add package Duende.BFF
 Configure OpenID Connect authentication for your BFF host. This is similar to the single frontend setup, but applies to all frontends unless overridden per frontend.
 
 ```csharp
-    builder.Services.AddBff()
-        .ConfigureOpenIdConnect(options =>
-        {
-            options.Authority = "https://demo.duendesoftware.com";
-            options.ClientId = "interactive.confidential";
-            options.ClientSecret = "secret";
-            options.ResponseType = "code";
-            options.ResponseMode = "query";
-
-            options.GetClaimsFromUserInfoEndpoint = true;
-            options.SaveTokens = true;
-            options.MapInboundClaims = false;
-
-            options.Scope.Clear();
-            options.Scope.Add("openid");
-            options.Scope.Add("profile");
-
-            // Add this scope if you want to receive refresh tokens
-            options.Scope.Add("offline_access");
-        })
-        .ConfigureCookies(options =>
-        {
-            // Because we use an identity server that's configured on a different site
-            // (duendesoftware.com vs localhost), we need to configure the SameSite property to Lax.
-            // Setting it to Strict would cause the authentication cookie not to be sent after logging in.
-            // The user would have to refresh the page to get the cookie.
-            // Recommendation: Set it to 'strict' if your IDP is on the same site as your BFF.
-            options.Cookie.SameSite = SameSiteMode.Lax;
-        });
-
-    builder.Services.AddAuthorization();
-
-    var app = builder.Build();
-
-    app.UseAuthentication();
-    app.UseRouting();
-
-    // adds antiforgery protection for local APIs
-    app.UseBff();
-
-    // adds authorization for local and remote API endpoints
-    app.UseAuthorization();
-
-    app.Run();
+// Program.cs
+builder.Services.AddBff()
+    .ConfigureOpenIdConnect(options =>
+    {
+        options.Authority = "https://demo.duendesoftware.com";
+        options.ClientId = "interactive.confidential";
+        options.ClientSecret = "secret";
+        options.ResponseType = "code";
+        options.ResponseMode = "query";
+
+        options.GetClaimsFromUserInfoEndpoint = true;
+        options.SaveTokens = true;
+        options.MapInboundClaims = false;
+
+        options.Scope.Clear();
+        options.Scope.Add("openid");
+        options.Scope.Add("profile");
+
+        // Add this scope if you want to receive refresh tokens
+        options.Scope.Add("offline_access");
+    })
+    .ConfigureCookies(options =>
+    {
+        // Because we use an identity server that's configured on a different site
+        // (duendesoftware.com vs localhost), we need to configure the SameSite property to Lax.
+        // Setting it to Strict would cause the authentication cookie not to be sent after logging in.
+        // The user would have to refresh the page to get the cookie.
+        // Recommendation: Set it to 'strict' if your IDP is on the same site as your BFF.
+        options.Cookie.SameSite = SameSiteMode.Lax;
+    });
+
+builder.Services.AddAuthorization();
+
+var app = builder.Build();
+
+app.UseAuthentication();
+app.UseRouting();
+
+// adds antiforgery protection for local APIs
+app.UseBff();
+
+// adds authorization for local and remote API endpoints
+app.UseAuthorization();
+
+app.Run();
 ```
 ### 4. Configure BFF In `Program.cs`
 
@@ -94,30 +95,31 @@ Configure OpenID Connect authentication for your BFF host. This is similar to th
   {/* prettier-ignore */}
   <TabItem label="Static">
 
-  Register multiple frontends directly in code using `AddFrontends`:
+      Register multiple frontends directly in code using `AddFrontends`:
 
-  ```csharp
-  builder.Services.AddBff()
-      .AddFrontends(
-          new BffFrontend(BffFrontendName.Parse("default-frontend"))
-              .WithIndexHtmlUrl(new Uri("https://localhost:5005/static/index.html")),
-          new BffFrontend(BffFrontendName.Parse("admin-frontend"))
-              .WithIndexHtmlUrl(new Uri("https://localhost:5005/admin/index.html"))
-      );
-  
-  // ...existing code for authentication, authorization, etc.
-  ```
+      <Code
+          lang="csharp"
+          title="Program.cs"
+          code={`builder.Services.AddBff()
+    .AddFrontends(
+        new BffFrontend(BffFrontendName.Parse("default-frontend"))
+            .WithIndexHtmlUrl(new Uri("https://localhost:5005/static/index.html")),
+        new BffFrontend(BffFrontendName.Parse("admin-frontend"))
+            .WithIndexHtmlUrl(new Uri("https://localhost:5005/admin/index.html"))
+    );
+
+// ...existing code for authentication, authorization, etc.`}/>
 
   </TabItem>
   {/* prettier-ignore */}
   <TabItem label="From Config">
+    You can also load frontend configuration from an `IConfiguration` source, such as a JSON file:
 
-  You can also load frontend configuration from an `IConfiguration` source, such as a JSON file:
-
-  Example `bffconfig.json`:
+    Example `bffconfig.json`:
 
-  ```json
-  {
+    <Code
+        lang="json"
+        code={`{
     "defaultOidcSettings": null,
     "defaultCookieSettings": null,
     "frontends": {
@@ -136,21 +138,21 @@ Configure OpenID Connect authentication for your BFF host. This is similar to th
         ]
       }
     }
-  }
-  ```
+  }`}/>
 
   Load and use the configuration in `Program.cs`:
 
-  ```csharp
-  var bffConfig = new ConfigurationBuilder()
-      .AddJsonFile("bffconfig.json")
-      .Build();
+    <Code
+    lang="csharp"
+    title="Program.cs"
+    code={`var bffConfig = new ConfigurationBuilder()
+    .AddJsonFile("bffconfig.json")
+    .Build();
 
-  builder.Services.AddBff()
-      .LoadConfiguration(bffConfig);
+builder.Services.AddBff()
+    .LoadConfiguration(bffConfig);
   
-  // ...existing code for authentication, authorization, etc.
-  ```
+// ...existing code for authentication, authorization, etc.`}/>
 
   </TabItem>
 </Tabs>
@@ -167,6 +169,7 @@ You can configure remote API proxying in two ways:
   You can configure remote APIs for each frontend individually:
 
   ```csharp
+  // Program.cs
   builder.Services.AddBff()
       .AddFrontends(
           new BffFrontend(BffFrontendName.Parse("default-frontend"))