diff --git a/docs/events/projections/aggregate-projections.md b/docs/events/projections/aggregate-projections.md index 733d84362c..5b2a866c5e 100644 --- a/docs/events/projections/aggregate-projections.md +++ b/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 diff --git a/src/Marten/StoreOptions.cs b/src/Marten/StoreOptions.cs index b823218d36..3509da0950 100644 --- a/src/Marten/StoreOptions.cs +++ b/src/Marten/StoreOptions.cs @@ -884,6 +884,9 @@ public PoliciesExpression PartitionMultiTenantedDocuments(Action