Update developer-guide.rst: Fix typo 'guaranatees' -> 'guarantees' (#…

…11851)

documentation/sphinx/source/developer-guide.rst

@@ -970,4 +970,4 @@ The trickiest errors are non-retryable errors. ``Transaction.on_error`` will ret
 
 If you see one of those errors, the best way of action is to fail the client.
 
-At a first glance this looks very similar to an ``commit_unknown_result``. However, these errors lack the one guarantee ``commit_unknown_result`` still gives to the user: if the commit has already been sent to the database, the transaction could get committed at a later point in time. This means that if you retry the transaction, your new transaction might race with the old transaction. While this technically doesn't violate any consistency guarantees, abandoning a transaction means that there are no causality guaranatees.
+At a first glance this looks very similar to an ``commit_unknown_result``. However, these errors lack the one guarantee ``commit_unknown_result`` still gives to the user: if the commit has already been sent to the database, the transaction could get committed at a later point in time. This means that if you retry the transaction, your new transaction might race with the old transaction. While this technically doesn't violate any consistency guarantees, abandoning a transaction means that there are no causality guarantees.