fix for couple tests, yet more markdown fixes

docs/events/projections/aggregate-projections.md

@@ -714,8 +714,7 @@ 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
-  can do next
+- 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

src/Marten/StoreOptions.cs

@@ -884,6 +884,9 @@ public PoliciesExpression PartitionMultiTenantedDocuments(Action<PartitioningExp
         public PoliciesExpression PartitionMultiTenantedDocumentsUsingMartenManagement(string schemaName)
         {
             var policy = new MartenManagedTenantListPartitions(_parent, schemaName);
+
+            _parent.Storage.Add(policy.Partitions);
+
             _parent._postPolicies.Add(policy);
 
             return this;

src/MultiTenancyTests/marten_managed_tenant_id_partitioning.cs

@@ -1,3 +1,4 @@
+using System;
 using System.Linq;
 using System.Threading;
 using System.Threading.Tasks;
@@ -22,8 +23,15 @@ public async Task InitializeAsync()
     {
         using var conn = new NpgsqlConnection(ConnectionSource.ConnectionString);
         await conn.OpenAsync();
-        await conn.CreateCommand($"delete from tenants.{MartenManagedTenantListPartitions.TableName}")
-            .ExecuteNonQueryAsync();
+        try
+        {
+            await conn.CreateCommand($"delete from tenants.{MartenManagedTenantListPartitions.TableName}")
+                .ExecuteNonQueryAsync();
+        }
+        catch (Exception)
+        {
+            // being lazy here
+        }
         await conn.CloseAsync();
     }