From 0d4259de5cceae63f253ba57402a99e04a6d41d1 Mon Sep 17 00:00:00 2001
From: Joshua Nitschke <33307206+JoshuaNitschke@users.noreply.github.com>
Date: Thu, 7 Sep 2023 21:35:59 -0700
Subject: [PATCH] Update sagas.md

The "start" verbiage confused me as it overlaps the special Start handler.

I think this slight clarification helps make things a bit more clear.
---
 docs/guide/http/sagas.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/guide/http/sagas.md b/docs/guide/http/sagas.md
index fba6f727f..0240715c5 100644
--- a/docs/guide/http/sagas.md
+++ b/docs/guide/http/sagas.md
@@ -60,8 +60,8 @@ public static (
 
 Remember in Wolverine.HTTP that the *first* return value of an endpoint is assumed to be the response body by Wolverine, so if you are
 wanting to start a new saga from an HTTP endpoint, the `Saga` return value either has to be a secondary value in a tuple to
-opt into the Saga mechanics. Alternatively, if all you want to do is start a new saga, but nothing else, you can return
-the `Saga` type *and* force Wolverine to use the return value as a new `Saga` like so:
+opt into the Saga mechanics. Alternatively, if all you want to do is *create* a new saga, but nothing else, you can return
+the `Saga` type *and* force Wolverine to use the return value as a new `Saga` as shown in the snippet below.  Please note that when creating a `Saga` entity in this manner, if it has a static `Start()` method, it will not be invoked.  Other message handlers in the `Saga` will behave as usual.
 
 snippet: sample_start_saga_from_http_endpoint_empty_body