From 543b865586b10eb47b7b395e4438bc9d39f2dca4 Mon Sep 17 00:00:00 2001
From: Ryuta Kamizono <kamipo@gmail.com>
Date: Tue, 25 Feb 2020 00:48:18 +0900
Subject: [PATCH] Fix a doc regression [ci skip]

https://github.com/rails/rails/pull/37731#discussion_r347128770
https://github.com/rails/rails/pull/37731#discussion_r347128858
---
 activerecord/lib/active_record/callbacks.rb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/activerecord/lib/active_record/callbacks.rb b/activerecord/lib/active_record/callbacks.rb
index 40197955cb..b086957656 100644
--- a/activerecord/lib/active_record/callbacks.rb
+++ b/activerecord/lib/active_record/callbacks.rb
@@ -21,8 +21,8 @@ module ActiveRecord
   # * (6) <tt>after_save</tt>
   # * (7) <tt>after_commit</tt>
   #
-  # Check out ActiveRecord::Transactions for more details about <tt>after_commit</tt> and
   # Also, an <tt>after_rollback</tt> callback can be configured to be triggered whenever a rollback is issued.
+  # Check out ActiveRecord::Transactions for more details about <tt>after_commit</tt> and
   # <tt>after_rollback</tt>.
   #
   # Additionally, an <tt>after_touch</tt> callback is triggered whenever an
@@ -83,7 +83,7 @@ module ActiveRecord
   #
   # == Types of callbacks
   #
-  # There are four types of callbacks accepted by the callback macros: method references (symbol), callback objects,
+  # There are three types of callbacks accepted by the callback macros: method references (symbol), callback objects,
   # inline methods (using a proc). Method references and callback objects are the recommended approaches,
   # inline methods using a proc are sometimes appropriate (such as for creating mix-ins).
   #