Fix few snippet related issues with docs

Author: mysticmind

docs/guide/basics.md

@@ -10,22 +10,22 @@ something happened. Just know that as far as Wolverine is concerned, those are r
 Here's a couple simple samples:
 
 <!-- snippet: sample_DebutAccount_command -->
-<a id='snippet-sample_debutaccount_command'></a>
+<a id='snippet-sample_DebutAccount_command'></a>
 ```cs
 // A "command" message
 public record DebitAccount(long AccountId, decimal Amount);
 
 // An "event" message
 public record AccountOverdrawn(long AccountId);
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/DocumentationSamples/MessageBusBasics.cs#L76-L84' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_debutaccount_command' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/DocumentationSamples/MessageBusBasics.cs#L76-L84' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_DebutAccount_command' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The next concept in Wolverine is a message handler, which is just a method that "knows" how to process an incoming message. Here's an extremely
 simple example:
 
 <!-- snippet: sample_DebitAccountHandler -->
-<a id='snippet-sample_debitaccounthandler'></a>
+<a id='snippet-sample_DebitAccountHandler'></a>
 ```cs
 public static class DebitAccountHandler
 {
@@ -35,7 +35,7 @@ public static class DebitAccountHandler
     }
 }
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/DocumentationSamples/MessageBusBasics.cs#L64-L74' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_debitaccounthandler' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/DocumentationSamples/MessageBusBasics.cs#L64-L74' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_DebitAccountHandler' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 Wolverine can act as a completely local mediator tool that allows your code to invoke the handler for a message at any time without having

docs/guide/codegen.md

@@ -203,7 +203,7 @@ As of Wolverine 5.0, you now have the ability to better control the usage of the
 code generation to potentially avoid unwanted usage:
 
 <!-- snippet: sample_configuring_ServiceLocationPolicy -->
-<a id='snippet-sample_configuring_servicelocationpolicy'></a>
+<a id='snippet-sample_configuring_ServiceLocationPolicy'></a>
 ```cs
 var builder = Host.CreateApplicationBuilder();
 builder.UseWolverine(opts =>
@@ -225,7 +225,7 @@ builder.UseWolverine(opts =>
     opts.ServiceLocationPolicy = ServiceLocationPolicy.NotAllowed;
 });
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/DocumentationSamples/ServiceLocationUsage.cs#L11-L33' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_configuring_servicelocationpolicy' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/DocumentationSamples/ServiceLocationUsage.cs#L11-L33' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_configuring_ServiceLocationPolicy' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 ::: note
@@ -370,7 +370,7 @@ and you can configure different behavior for production versus development time
 using var host = await Host.CreateDefaultBuilder()
     .UseWolverine(opts =>
     {
-        // Use "Dynamic" type load mode at development time, but
+        // Use "Auto" type load mode at development time, but
         // "Static" any other time
         opts.Services.CritterStackDefaults(x =>
         {

docs/guide/command-line.md

@@ -7,7 +7,7 @@ tools. To get started, apply Oakton as the command line parser in your applicati
 sample application bootstrapping from Wolverine's [Getting Started](/tutorials/getting-started):
 
 <!-- snippet: sample_Quickstart_Program -->
-<a id='snippet-sample_quickstart_program'></a>
+<a id='snippet-sample_Quickstart_Program'></a>
 ```cs
 using JasperFx;
 using Quickstart;
@@ -49,7 +49,7 @@ app.MapGet("/", () => Results.Redirect("/swagger"));
 // your Wolverine application
 return await app.RunJasperFxCommands(args);
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Quickstart/Program.cs#L1-L43' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_quickstart_program' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Quickstart/Program.cs#L1-L43' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_Quickstart_Program' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 From this project's root in the command line terminal tool of your choice, type:

docs/guide/configuration.md

@@ -30,7 +30,7 @@ Below is a sample of adding Wolverine to an ASP.NET Core application that is boo
 `WebApplicationBuilder`:
 
 <!-- snippet: sample_Quickstart_Program -->
-<a id='snippet-sample_quickstart_program'></a>
+<a id='snippet-sample_Quickstart_Program'></a>
 ```cs
 using JasperFx;
 using Quickstart;
@@ -72,7 +72,7 @@ app.MapGet("/", () => Results.Redirect("/swagger"));
 // your Wolverine application
 return await app.RunJasperFxCommands(args);
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Quickstart/Program.cs#L1-L43' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_quickstart_program' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Quickstart/Program.cs#L1-L43' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_Quickstart_Program' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 ## "Headless" Applications

docs/guide/diagnostics.md

@@ -9,7 +9,7 @@ to utilize this command line integration, you need to apply JasperFx as your com
 sample `Program.cs` file:
 
 <!-- snippet: sample_Quickstart_Program -->
-<a id='snippet-sample_quickstart_program'></a>
+<a id='snippet-sample_Quickstart_Program'></a>
 ```cs
 using JasperFx;
 using Quickstart;
@@ -51,7 +51,7 @@ app.MapGet("/", () => Results.Redirect("/swagger"));
 // your Wolverine application
 return await app.RunJasperFxCommands(args);
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Quickstart/Program.cs#L1-L43' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_quickstart_program' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Quickstart/Program.cs#L1-L43' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_Quickstart_Program' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 ## Command Line Description

docs/guide/durability/efcore/multi-tenancy.md

@@ -173,7 +173,7 @@ Then you can _still_ use those EF Core `DbContext` services with Wolverine messa
 this sample code:
 
 <!-- snippet: sample_using_IDbContextOutboxFactory -->
-<a id='snippet-sample_using_idbcontextoutboxfactory'></a>
+<a id='snippet-sample_using_IDbContextOutboxFactory'></a>
 ```cs
 public class MyMessageHandler
 {
@@ -203,7 +203,7 @@ public class MyMessageHandler
     }
 }
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Persistence/EfCoreTests/MultiTenancy/MultiTenancyDocumentationSamples.cs#L190-L220' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_using_idbcontextoutboxfactory' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Persistence/EfCoreTests/MultiTenancy/MultiTenancyDocumentationSamples.cs#L190-L220' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_using_IDbContextOutboxFactory' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The important thing to note above is just that this pattern and service will work with any .NET code and not just within Wolverine

docs/guide/durability/efcore/operations.md

@@ -5,7 +5,7 @@ Just know that Wolverine completely supports the concept of [Storage Operations]
 Assuming you have an EF Core `DbContext` type like this registered in your system:
 
 <!-- snippet: sample_TodoDbContext -->
-<a id='snippet-sample_tododbcontext'></a>
+<a id='snippet-sample_TodoDbContext'></a>
 ```cs
 public class TodoDbContext : DbContext
 {
@@ -27,14 +27,14 @@ public class TodoDbContext : DbContext
     }
 }
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Persistence/EfCoreTests/using_storage_return_types_and_entity_attributes.cs#L55-L77' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_tododbcontext' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Persistence/EfCoreTests/using_storage_return_types_and_entity_attributes.cs#L55-L77' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_TodoDbContext' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 You can use storage operations in Wolverine message handlers or HTTP endpoints like these samples from the Wolverine
 test suite:
 
 <!-- snippet: sample_TodoHandler_to_demonstrate_storage_operations -->
-<a id='snippet-sample_todohandler_to_demonstrate_storage_operations'></a>
+<a id='snippet-sample_TodoHandler_to_demonstrate_storage_operations'></a>
 ```cs
 public static class TodoHandler
 {
@@ -134,7 +134,7 @@ public static class TodoHandler
     }
 }
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Testing/Wolverine.ComplianceTests/StorageActionCompliance.cs#L294-L394' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_todohandler_to_demonstrate_storage_operations' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Testing/Wolverine.ComplianceTests/StorageActionCompliance.cs#L294-L394' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_TodoHandler_to_demonstrate_storage_operations' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 ::: warning

docs/guide/durability/efcore/sagas.md

@@ -92,7 +92,7 @@ public class Order : Saga
 And a matching `OrdersDbContext` that can persist that type like so:
 
 <!-- snippet: sample_OrdersDbContext -->
-<a id='snippet-sample_ordersdbcontext'></a>
+<a id='snippet-sample_OrdersDbContext'></a>
 ```cs
 public class OrdersDbContext : DbContext
 {
@@ -119,7 +119,7 @@ public class OrdersDbContext : DbContext
     }
 }
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/EFCoreSample/ItemService/Orders/Order.cs#L81-L108' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_ordersdbcontext' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/EFCoreSample/ItemService/Orders/Order.cs#L81-L108' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_OrdersDbContext' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 There's no other registration to do other than adding the `OrdersDbContext` to your IoC container and enabling

docs/guide/durability/idempotency.md

@@ -14,7 +14,7 @@ Instead of immediately deleting message storage for a successfully completed mes
 that message in storage for a default of 5 minutes to protect against duplicate incoming messages. To override that setting, you have this option:
 
 <!-- snippet: sample_configuring_KeepAfterMessageHandling -->
-<a id='snippet-sample_configuring_keepaftermessagehandling'></a>
+<a id='snippet-sample_configuring_KeepAfterMessageHandling'></a>
 ```cs
 using var host = await Host.CreateDefaultBuilder()
     .UseWolverine(opts =>
@@ -25,5 +25,5 @@ using var host = await Host.CreateDefaultBuilder()
         opts.Durability.KeepAfterMessageHandling = 10.Minutes();
     }).StartAsync();
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Persistence/PersistenceTests/Samples/DocumentationSamples.cs#L195-L206' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_configuring_keepaftermessagehandling' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Persistence/PersistenceTests/Samples/DocumentationSamples.cs#L195-L206' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_configuring_KeepAfterMessageHandling' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->

docs/guide/durability/index.md

@@ -27,7 +27,7 @@ getting lost en route.
 Consider this sample message handler from Wolverine's [AppWithMiddleware sample project](https://github.com/JasperFx/wolverine/tree/main/src/Samples/Middleware):
 
 <!-- snippet: sample_DebitAccountHandler_that_uses_IMessageContext -->
-<a id='snippet-sample_debitaccounthandler_that_uses_imessagecontext'></a>
+<a id='snippet-sample_DebitAccountHandler_that_uses_IMessageContext'></a>
 ```cs
 [Transactional]
 public static async Task Handle(
@@ -62,7 +62,7 @@ public static async Task Handle(
         new DeliveryOptions { DeliverWithin = 5.Seconds() });
 }
 ```
-<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Middleware/AppWithMiddleware/Account.cs#L126-L161' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_debitaccounthandler_that_uses_imessagecontext' title='Start of snippet'>anchor</a></sup>
+<sup><a href='https://github.com/JasperFx/wolverine/blob/main/src/Samples/Middleware/AppWithMiddleware/Account.cs#L126-L161' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_DebitAccountHandler_that_uses_IMessageContext' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
 The handler code above is committing changes to an `Account` in the underlying database and potentially sending out additional messages based on the state of the `Account`.