diff --git a/src/reference/defining-flows.adoc b/src/reference/defining-flows.adoc index 8fcdda8f..21c3e357 100644 --- a/src/reference/defining-flows.adoc +++ b/src/reference/defining-flows.adoc @@ -100,7 +100,7 @@ Use the `end-state` element to define a flow outcome: ---- -When a flow transitions to a end-state it terminates and the outcome is returned. +When a flow transitions to a end-state, it ends and the outcome is returned. === Checkpoint: Essential language elements diff --git a/src/reference/flow-managed-persistence.adoc b/src/reference/flow-managed-persistence.adoc index 8e3354b5..53b65927 100644 --- a/src/reference/flow-managed-persistence.adoc +++ b/src/reference/flow-managed-persistence.adoc @@ -19,7 +19,7 @@ This pattern provides isolation of intermediate edits by committing changes to t This pattern is often used in conjunction with an optimistic locking strategy to protect the integrity of data modified in parallel by multiple users. To support saving and restarting the progress of a flow over an extended period of time, a durable store for flow state must be used. If a save and restart capability is not required, standard HTTP session-based storage of the flow state is sufficient. -In that case, session expiration or termination before commit could potentially result in changes being lost. +In that case, a session expiring or ending before commit could potentially result in changes being lost. To use the flow-scoped `PersistenceContext` pattern, first mark your flow as a `persistence-context`, as follows: