Redo changes per Gavin's review comment focus on the association being contextual

Author: njr-11

spec/src/main/asciidoc/repository.asciidoc

@@ -999,19 +999,17 @@ Support for stateful repositories is defined in the dedicated module `jakarta.da
 
 ==== Persistence contexts
 
-Each operation on a stateful repository is associated with a _persistence context_, a set of managed entity instances in which at most one instance represents a given record in the database.
+A stateful repository operation applies to a _persistence context_, a set of managed entity instances in which at most one instance represents a given record in the database. Persistence context can span multiple repository operations, such as all operations performed within a transaction.
 
 - An entity instance never belongs to multiple persistence contexts.
 
 - The Jakarta Data implementation must ensure that a given persistence context never contains more than one entity instance representing the same record.
 
-- Multiple operations on a single repository, in particular those running in the same transaction or thread, can share a persistence context.
-
-- Operations on multiple repositories might share a persistence context, especially if the repositories share a datastore.
+- Multiple repositories might share a persistence context, especially if they share a datastore.
 
 - A persistence context is never shared across transactions.
 
-A query method of a stateful repository which returns an entity type always returns managed instances belonging to a persistence context associated with the repository.
+A query method of a stateful repository which returns an entity type always returns managed instances associated with the persistence context under which the repository operation is running.
 
 [WARNING]
 ====
@@ -1020,10 +1018,6 @@ If an application program accesses an entity instance belonging to a persistence
 
 This specification does not define the lifecycle of a persistence context, nor how a persistence context is propagated across repositories.
 
-===== Persistence context within a transaction
-
-All operations performed on a given repository that participate in a given transaction must run under the same persistence context. The Jakarta Data provider must ensure that the persistence context is flushed prior to or during the before completion phase of transaction commit.
-
 [NOTE]
 ====
 Implementations of Jakarta Data are encouraged to propagate a single persistence context within a given transaction across repositories which share a given data store.
@@ -1049,7 +1043,7 @@ Invocation of a lifecycle method or modification of the state of a managed entit
 Such changes to the database do not typically happen synchronously with invocation of the lifecycle method, or immediately after modification of the managed entity.
 Instead, such changes are made when the persistence context is periodically _flushed_.
 
-NOTE: This specification does not prescribe the timing of flush operations for persistence context that does not participate in a transaction.
+NOTE: This specification does not prescribe the timing of flush operations, but a flush typically happens before execution of a query or during the before completion phase of transaction commit.
 An implementation of Jakarta Data should flush as needed to ensure that query results are consistent with the current state of the persistence context.