anchor.diff:  ===== Specifying Transaction Settings
   
   You can specify transaction settings (such as the propagation mode, the isolation level,
  -the timeout, and so forth) for the `TransactionalOperator`.
  -By default, `TransactionalOperator` instances have the
  +the timeout, and so forth) for the `TransactionalOperator`. By default,
  +`TransactionalOperator` instances have
   <<transaction-declarative-txadvice-settings,default transactional settings>>. The
  -following example shows customization of the transactional settings for
  -a specific `TransactionalOperator:`
  +following example shows customization of the transactional settings for a specific
  +`TransactionalOperator:`
   
   [source,java,indent=0,subs="verbatim,quotes",role="primary"]
   .Java
  
positive.code: [[transaction-programmatic-rtm]]
  ===== Using the `ReactiveTransactionManager`
  
  When working with reactive transactions, you can use 
  `org.springframework.transaction.ReactiveTransactionManager`
  directly to manage your transaction. To do so, pass the implementation of the
  `ReactiveTransactionManager` you use to your bean through a bean reference. Then,
  by using the `TransactionDefinition` and `ReactiveTransaction` objects, you can initiate
  transactions, roll back, and commit. The following example shows how to do so:
  
  [source,java,indent=0,subs="verbatim,quotes",role="primary"]
  .Java
  
negative.code: Java EE transaction contexts, a `TransactionStatus` is associated with a thread of
  execution.
  
  As of Spring Framework 5.2, Spring also provides a transaction management abstraction for
  reactive applications that make use of reactive types or Kotlin Coroutines. The following
  listing shows the transaction strategy defined by
  `org.springframework.transaction.ReactiveTransactionManager`:
  
  [source,java,indent=0,subs="verbatim,quotes",role="primary"]
  