README.md in quo_vadis-2.0.1 vs README.md in quo_vadis-2.0.2

@@ -230,11 +230,11 @@
 class UsersController < ApplicationController
   def create
     @user = User.new user_params
     if @user.save
       request_confirmation @user
-      redirect_to qv.confirmations_path  # a page where you advise the user to check their email
+      redirect_to quo_vadis.confirmations_path  # a page where you advise the user to check their email
     else
       # ...
     end
   end
 
@@ -250,11 +250,11 @@
 
 See the Configuration section below for how to set QuoVadis's emails' from addresses, headers, etc.
 
 Now write the page to where the user is redirected while they wait for the email ([example](https://github.com/airblade/quo_vadis/blob/master/test/dummy/app/views/quo_vadis/confirmations/index.html.erb)).  It must be in `app/views/quo_vadis/confirmations/index.html.:format`.
 
-It's a good idea for that page to link to `new_confirmation_path` where the user can request another email if need be.
+On that page you can show the user the address the email was sent to, enable them to update their email address if they make a mistake on the sign-up form, and provide a button to resend another email directly.  If the sign-up occurred in a different browser session, you can instead link to `new_confirmation_path` where the user can request another email if need be.
 
 Next, write the page to which the link in the email points ([example](https://github.com/airblade/quo_vadis/blob/master/test/dummy/app/views/quo_vadis/confirmations/edit.html.erb)).  It must be in `app/views/quo_vadis/confirmations/edit.html.:format`.
 
 Finally, write the page where people can put in their identifier (not their email, unless the identifier is email) again to request another confirmation email ([example](https://github.com/airblade/quo_vadis/blob/master/test/dummy/app/views/quo_vadis/confirmations/new.html.erb)).  It must be in `app/views/quo_vadis/confirmations/new.html.:format`.
 
@@ -486,16 +486,35 @@
 
 For example, the default login path is at `/login`.  If you set `mount_point` to `/auth`, the login path would be `/auth/login`.
 
 #### Rails configuration
 
+__Mailer URLs__
+
 You must also configure the mailer host so URLs are generated correctly in emails:
 
 ```ruby
 config.action_mailer.default_url_options: { host: 'example.com' }
 ```
 
-Finally, you can set up your post-authentication and post-password-change routes.  If you don't, you must have a root route.  For example:
+__Layouts__
+
+You can specify QuoVadis's controllers' layouts in a `#to_prepare` block in your application configuration.  For example:
+
+```ruby
+# config/application.rb
+module YourApp
+  class Application < Rails::Application
+    config.to_prepare do
+      QuoVadis::ConfirmationsController.layout 'your_layout'
+    end
+  end
+end
+```
+
+__Routes__
+
+You can set up your post-authentication and post-password-change routes.  If you don't, you must have a root route.  For example:
 
 ```ruby
 # config/routes.rb
 get '/dashboard', to: 'dashboards#show', as: 'after_login'
 get '/profile',   to: 'profiles#show',   as: 'after_password_change'