diff --git a/guides/source/active_record_querying.md b/guides/source/active_record_querying.md
index de976acd016311ad7ad625d36bd8c210e74bc61a..2f10bc4e7cf4112a2a3bb1e7f14eb01e24176de1 100644
--- a/guides/source/active_record_querying.md
+++ b/guides/source/active_record_querying.md
@@ -317,7 +317,7 @@ end
 
 The `find_each` method accepts most of the options allowed by the regular `find` method, except for `:order` and `:limit`, which are reserved for internal use by `find_each`.
 
-Two additional options, `:batch_size` and `:begin_at`, are available as well.
+Three additional options, `:batch_size`, `:begin_at` and `:end_at`, are available as well.
 
 **`:batch_size`**
 
@@ -348,7 +348,7 @@ Another example would be if you wanted multiple workers handling the same proces
 Similar to the `:begin_at` option, `:end_at` allows you to configure the last ID of the sequence whenever the highest ID is not the one you need.
 This would be useful, for example, if you wanted to run a batch process, using a subset of records based on `:begin_at` and `:end_at`
 
-For example, to send newsletters only to users with the primary key starting from 2000 up to 10000 and to retrieve them in batches of 1000:
+For example, to send newsletters only to users with the primary key starting from 2000 up to 10000 and to retrieve them in batches of 5000:
 
 ```ruby
 User.find_each(begin_at: 2000, end_at: 10000, batch_size: 5000) do |user|