anchor.diff:  
   The `R2dbcTransactionManager` class is a `ReactiveTransactionManager` implementation for
   single R2DBC datasources. It binds an R2DBC connection from the specified connection factory
  -to the subscriber `Context`, potentially allowing for one subscriber connection for each 
  +to the subscriber `Context`, potentially allowing for one subscriber connection for each
   connection factory.
   
   Application code is required to retrieve the R2DBC connection through
  
positive.code: parameters are not escaped properly. `DatabaseClient` leverages R2DBC's
  `bind` API to eliminate the risk of SQL injection for query parameters.
  You can provide a parameterized SQL statement with the `execute(…)` operator
  and bind parameters to the actual `Statement`. Your R2DBC driver then executes
  the statement by using prepared statements and parameter substitution.
  
  Parameter binding supports two binding strategies:
  
negative.code: 
  When you use Spring's R2DBC layer, you can can configure your own with a
  connection pool implementation provided by a third party. A popular
  implementation is R2DBC Pool (`r2dbc-pool`). Implementations in the Spring
  distribution are meant only for testing purposes and do not provide pooling.
  
  To configure a `ConnectionFactory`:
  