README.md in clearance-2.2.1 vs README.md in clearance-2.3.0

@@ -58,10 +58,11 @@
   config.httponly = false
   config.mailer_sender = "[e-mail]"
   config.password_strategy = Clearance::PasswordStrategies::BCrypt
   config.redirect_url = "/"
   config.rotate_csrf_on_sign_in = true
+  config.same_site = nil
   config.secure_cookie = false
   config.sign_in_guards = []
   config.user_model = "User"
   config.parent_controller = "ApplicationController"
 end
@@ -282,27 +283,9 @@
 which the `Clearance::User` module will add to the configured model class and
 which may conflict with or duplicate already present validations on the `email`
 and `password` attributes. Over-riding the `email_optional?` or
 `skip_password_validation?` methods to return `true` will disable those
 validations from being added.
-
-### Deliver Email in Background Job
-
-Clearance has a password reset mailer. If you are using Rails 4.2 and Clearance
-1.6 or greater, Clearance will use ActiveJob's `deliver_later` method to
-automatically take advantage of your configured queue.
-
-If you are using an earlier version of Rails, you can override the
-`Clearance::Passwords` controller and define the behavior you need in the
-`deliver_email` method.
-
-```ruby
-class PasswordsController < Clearance::PasswordsController
-  def deliver_email(user)
-    ClearanceMailer.delay.change_password(user)
-  end
-end
-```
 
 ## Extending Sign In
 
 By default, Clearance will sign in any user with valid credentials. If you need
 to support additional checks during the sign in process then you can use the