Added link to RaiseSideffects docs

Author: oskardudycz

Workshops/IntroductionToEventSourcing/17-Projections.MultiStream.Marten/ProjectionsTests.cs

@@ -27,12 +27,6 @@ bool IsAcceptable
 );
 
 // ENUMS
-public enum VerificationStatus
-{
-    Pending,
-    Passed,
-    Failed
-}
 
 public enum PaymentStatus
 {

Workshops/IntroductionToEventSourcing/17-Projections.MultiStream.Marten/README.md

@@ -17,7 +17,7 @@ Events arrive from three different streams (payment, merchant, and fraud check),
 ## Steps
 
 1. Create a `PaymentVerificationProjection` class with `Handle` methods for each event type
-2. Register your handlers using `eventStore.Register`
+2. Register your handlers using document store options `options.Projections.Add` as inline.
 3. Implement decision logic in the `FraudScoreCalculated` handler (always last for completed payments):
     - Reject if merchant failed
     - Reject if fraud score > 0.75

Workshops/IntroductionToEventSourcing/18-Projections.MultiStream.OutOfOrder.Marten/README.md

@@ -10,7 +10,7 @@ Learn how to build resilient Marten projections that work even when events arriv
 
 Same out-of-order context as Exercise 16: events can arrive in any order (e.g., from different RabbitMQ queues or Kafka topics). The projection from Exercise 17 assumes ordered events — run the test to see it fail.
 
-**Emit event when payment verification is completed**.
+**Emit event when payment verification is completed**. Use [`RaiseSideEffects`method from Marten projections](https://martendb.io/events/projections/side-effects.html#side-effects)
 
 ## Reference