diff --git a/docs/src/main/asciidoc/transaction.adoc b/docs/src/main/asciidoc/transaction.adoc
index 833423a479d9a..007c448e28564 100644
--- a/docs/src/main/asciidoc/transaction.adoc
+++ b/docs/src/main/asciidoc/transaction.adoc
@@ -188,14 +188,14 @@ The default value is 60 seconds.
 
 == Configuring transaction node name identifier
 
-Narayana, as the underlaying transaction manager, has an concept of unique node identifier.
-This is important if you consider to use XA transactions with involve multiple resources.
+Narayana, as the underlying transaction manager, has a concept of unique node identifier.
+This is important if you consider using XA transactions that involve multiple resources.
 
 The node name identifier plays a crucial part in the identification of a transaction.
 The node name identifier is forged into the transaction id when the transaction is created.
-Based on the node name identifier the transaction manager is capable to recognized the XA tranaction
+Based on the node name identifier, the transaction manager is capable to recognize the XA transaction
 counterparts created in database or JMS broker. The identifier makes possible for the transaction manager
-to roll-back the transaction counterparts during recovery.
+to roll back the transaction counterparts during recovery.
 
 The node name identifier needs to be unique per transaction manager deployment.
 And the node identifier needs to be stable over the transaction manager restarts.