Removed the transactions suggestion from the pipelining doc (#1349)

docs/modules/cluster-performance/pages/pipelining.adoc

@@ -43,15 +43,7 @@ with requests in that situation. See the <<back-pressure, Back Pressure section>
 You can use the pipelining both on the clients and members. You do not need a special configuration, it works out-of-the-box.
 
 The pipelining can be used for any asynchronous call. You can use it for IMap asynchronous get/put methods as well as for
-ICache, IAtomicLong, etc. It cannot be used as a transaction mechanism though. So you cannot do some calls and throw away the pipeline and expect that
-none of the requests are executed. If you want to use an atomic behavior, see  xref:transactions:providing-xa-transactions.adoc[Transactions] for more details.
-The pipelining is just a performance optimization, not a mechanism for atomic behavior.
-
-[CAUTION]
-.Deprecation Notice for Transactions
-====
-Transactions have been deprecated, and will be removed as of Hazelcast version 7.0. An improved version of this feature is under consideration. If you are already using transactions, get in touch and share your use case. Your feedback will help us to develop a solution that meets your needs.
-====
+ICache, IAtomicLong, etc. It cannot be used as a transaction mechanism though. So you cannot do some calls and throw away the pipeline and expect that none of the requests are executed. The pipelining is just a performance optimization, not a mechanism for atomic behavior.
 
 The pipelines are cheap and should frequently be replaced because they accumulate results. It is fine to have a few hundred or
 even a few thousand calls being processed with the pipelining. However, all the responses to all requests are stored in the pipeline