Little markdown linting clean up

Author: jeremydmiller

docs/configuration/hostbuilder.md

@@ -256,7 +256,7 @@ public interface IConfigureMarten
 <sup><a href='https://github.com/JasperFx/marten/blob/master/src/Marten/MartenServiceCollectionExtensions.cs#L877-L888' title='Snippet source file'>snippet source</a> | <a href='#snippet-sample_iconfiguremarten' title='Start of snippet'>anchor</a></sup>
 <!-- endSnippet -->
 
-You could alternatively implement a custom `IConfigureMarten` (or `IConfigureMarten<T> where T : IDocumentStore` if you're [working with multiple databases](#working-with-multiple-marten-databases)) class like so:
+You could alternatively implement a custom `IConfigureMarten` (or `IConfigureMarten<T> where T : IDocumentStore` if you're working with multiple databases class like so:
 
 <!-- snippet: sample_UserMartenConfiguration -->
 <a id='snippet-sample_usermartenconfiguration'></a>

docs/configuration/optimized_artifact_workflow.md

@@ -69,4 +69,4 @@ At production time, that changes to:
   of automatic database change detection and migration at runtime. This is also a minor performance
   optimization that sidesteps potential locking issues.
 * `StoreOptions.GeneratedCodeMode = TypeLoadMode.Static` to only try to load pre-built types from
-  what Marten thinks is the application assembly.
+  what Marten thinks is the application assembly.

docs/migration-guide.md

@@ -45,7 +45,7 @@ The projection base classes have minor changes in Marten 8:
 * The `SingleStreamProjection` now requires 2 generic type arguments for both the projected document type and the identity type of that document. This compromise was made to better support the increasing widespread usage of strong typed identifiers.
 
 v7: `InvoiceProjection : SingleStreamProjection<Invoice>`
-~~~~
+
 v8: `InvoiceProjection : SingleStreamProjection<Invoice, InvoiceId>`
 
 * Both `SingleStreamProjection` and `MultiStreamProjection` have improved options for writing explicit code for projections for more complex scenarios or if you just prefer that over the conventional `Apply` / `Create` method approach