A draft review has two outcomes. A change request sends it back for editing. Approval ends the review. Show those outcomes as separate paths in the Markdown note.

Name the states and the events

~~~mermaid
stateDiagram-v2
  [*] --> Draft
  Draft --> InReview : Submit
  InReview --> Draft : Request changes
  InReview --> Approved : Approve
  Approved --> [*]
~~~

Draft is submitted for review, then review either requests changes or approves the draft.

Illustrated lifecycle. Read the labels as the events that move the draft.

Trace the two outcomes from review

In the saved preview, follow Submit to InReview. Follow Request changes back to Draft, then try the approval route from InReview to Approved and the end marker. If approved work can reopen in your process, add that route once you know what triggers it. Give the two outcomes in text beside the graph for readers whose viewer shows only source.

Request changes returns to Draft; Approve leads through Approved to the end.

Illustrated route check. Trace both paths from InReview.

Mermaid’s state diagram syntax