docs: fix references about other integrations in spanner doc (#3413) (#…

…3472) * docs: fix references about other integrations (#1) The original text says: > Other Google Cloud database-related integrations like Spanner and Firestore can introduce `PlatformTransactionManager` … However, the docs _are_ about Spanner integration. * add Datastore to text as other Google Cloud database-related integrations. --------- Co-authored-by: Viktors Garkavijs <[email protected]>
GoogleCloudPlatform · Jan 15, 2025 · 20ba29a · 20ba29a
1 parent d33a267
commit 20ba29a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/src/main/asciidoc/spanner.adoc b/docs/src/main/asciidoc/spanner.adoc
@@ -956,7 +956,7 @@ This feature requires a bean of `SpannerTransactionManager`, which is provided w
 If a method annotated with `@Transactional` calls another method also annotated, then both methods will work within the same transaction.
 `performReadOnlyTransaction` and `performReadWriteTransaction` cannot be used in `@Transactional` annotated methods because Cloud Spanner does not support transactions within transactions.
 
-Other Google Cloud database-related integrations like Spanner and Firestore can introduce `PlatformTransactionManager` beans, and can interfere with Datastore Transaction Manager. To disambiguate, explicitly specify the name of the transaction manager bean for such `@Transactional` methods. Example:
+Other Google Cloud database-related integrations like Datastore and Firestore can introduce `PlatformTransactionManager` beans, and can interfere with Spanner Transaction Manager. To disambiguate, explicitly specify the name of the transaction manager bean for such `@Transactional` methods. Example:
 
 [source,java]
 ----