README.md in gds-sso-13.6.0 vs README.md in gds-sso-14.0.0

@@ -100,11 +100,11 @@
 
 # fails unless the user has both of these permissions
 authorise_user!(all_of: %w(edit create))
 ```
 
-The signon application makes sure that only users who have been granted access to the application can access it (e.g. they have the `signin` permission for your app).  This used to be left up to the applications themselves to check with the `require_signin_permission!` method.  This is now deprecated and can be removed from your controllers.  You should replace it with a call to `authenticate_user!` if you aren't already using that method, otherwise no signon authentication will be performed.
+The signon application makes sure that only users who have been granted access to the application can access it (e.g. they have the `signin` permission for your app).
 
 ### Authorisation for API Users
 
 In addition to the single-sign-on strategy, this gem also allows authorisation
 via a "bearer token". This is used by publishing applications to be authorised
@@ -171,9 +171,10 @@
 
 ```ruby
 GDS::SSO.config do |config|
   # other config here
   config.additional_mock_permissions_required = ["array", "of", "permissions"]
+end
 ```
 
 The mock bearer token will then ensure that the dummy api user has the required permission.
 
 ### Testing in your application