diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index b3388c141f..02e6e4e06a 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -213,11 +213,10 @@ Django provides a single API to control database transactions.
         This also applies to any other mechanism that may hold app state, such
         as caching or global variables. For example, if the code proactively
         updates data in the cache after saving an object, it's recommended to
-        use :ref:`transcation.on_commit <performing-actions-after-commit>`
+        use :ref:`transaction.on_commit() <performing-actions-after-commit>`
         instead, to defer cache alterations until the transaction is actually
         committed.
 
-
     In order to guarantee atomicity, ``atomic`` disables some APIs. Attempting
     to commit, roll back, or change the autocommit state of the database
     connection within an ``atomic`` block will raise an exception.