Markdown linting

docs/events/projections/aggregate-projections.md

@@ -714,11 +714,11 @@ Man, that's a mouthful of a title. _Sometimes_, it can be valuable to emit new e
 when you first know the new state of the projected aggregate documents. Or maybe what you might want to do is to send
 a message for the new state of an updated projection. Here's a couple possible scenarios that might lead you here:
 
-* There's some kind of business logic that can be processed against an aggregate to "decide" what the system
+-There's some kind of business logic that can be processed against an aggregate to "decide" what the system
   can do next
-* You need to send updates about the aggregated projection state to clients via web sockets
-* You need to replicate the Marten projection data in a completely different database
-* There are business processes that can be kicked off for updates to the aggregated state
+- You need to send updates about the aggregated projection state to clients via web sockets
+- You need to replicate the Marten projection data in a completely different database
+- There are business processes that can be kicked off for updates to the aggregated state
 
 To do any of this, you can override the `RaiseSideEffects()` method in any aggregated projection that uses one of the 
 following base classes:
@@ -744,4 +744,3 @@ A couple important facts about this new functionality:
 This relatively new behavior that was built for a specific [JasperFx Software](https://jasperfx.net) client project, 
 but has been on the backlog for quite some time. If there are any difficulties with this approach, please feel free
 to join the [Marten Discord room](https://discord.gg/BGkCDx5d). 
-

docs/events/projections/custom-aggregates.md

@@ -149,5 +149,3 @@ as shown below:
 snippet: sample_using_simple_explicit_code_for_live_aggregation
 
 Note that this usage is valid for all possible projection lifecycles now (`Live`, `Inline`, and `Async`).
-
-

docs/events/projections/rebuilding.md

@@ -45,4 +45,4 @@ A long standing request has been to be able to rebuild only a single stream or s
 by stream id (or string key). Marten now has a (admittedly crude) ability to do so with this syntax
 on `IDocumentStore`:
 
-snippet: sample_rebuild_single_stream
+snippet: sample_rebuild_single_stream