diff --git a/pages/stack/transactions/transaction-flow.mdx b/pages/stack/transactions/transaction-flow.mdx
index b076e5c4..4c3b0a40 100644
--- a/pages/stack/transactions/transaction-flow.mdx
+++ b/pages/stack/transactions/transaction-flow.mdx
@@ -15,7 +15,7 @@ This guide explains the transaction flow process for rollup transactions. The pr
 
 *   The transaction needs to be executed to modify the state (by `op-geth`).
     Afterwards, `op-proposer` writes a [commitment](https://en.wikipedia.org/wiki/Commitment_scheme) to the post-transaction state to L1.
-    Note that `op-proposer` does not need to write a commitment after each transaction to L1, it is OK to commit to the state after a block of transactions.
+    Note that `op-proposer` does not need to write a commitment after each transaction to L1; it is OK to commit to the state after a block of transactions.
 
 ![Overall process.](/img/op-stack/protocol/transaction-flow.svg)