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

@@ -43,20 +43,19 @@
 Then run `bundle install`.
 
 Next, add the database tables:
 
 ```
-$ rails quo_vadis:install:migrations
-$ rails db:migrate
+rails quo_vadis:install:migrations && rails db:migrate
 ```
 
 All the database tables are prefixed with `qv_`.
 
 Finally, copy the example views across:
 
 ```
-$ rails generate quo_vadis:install
+rails generate quo_vadis:install
 ```
 
 
 ## Usage
 
@@ -216,11 +215,11 @@
 2. [Your controller] Your code tells QuoVadis to email the user a confirmation link.  The link is valid for `QuoVadis.account_confirmation_token_lifetime`.
 3. [The email] The user clicks the link.
 4. [Account-confirmation confirmation page] The user clicks a button to confirm their account.  (This step is to prevent any link prefetching in the user's mail client from confirming them unintentionally.)
 5. QuoVadis confirms the user's account and logs them in.
 
-Your new user sign-up form ([example](https://github.com/airblade/quo_vadis/blob/master/test/dummy/app/views/users/new.html.erb)) must include:
+Your new user sign-up form ([example](https://github.com/airblade/quo_vadis/blob/master/test/dummy/app/views/sign_ups/new.html.erb)) must include:
 
 - a `:password` field;
 - optionally a `:password_confirmation` field;
 - a field for their identifier;
 - an `:email` field if the identifier is not their email.
@@ -490,10 +489,10 @@
 #### Rails configuration
 
 You must also configure the mailer host so URLs are generated correctly in emails:
 
 ```ruby
-config.action_mailer.default_url_options: { host: 'example.com }
+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:
 
 ```ruby