[skip ci] Corrections to the README.md

README.md

@@ -193,6 +193,9 @@ end
 * [add_version](#add_version)
 * [doc_version](#doc_version)
 * [markdown](#markdown)
+* [endpoint_auth_wrapper](#endpoint_auth_wrapper)
+* [swagger_endpoint_guard](#swagger_endpoint_guard)
+* [oauth_token](#oauth_token)
 * [security_definitions](#security_definitions)
 * [models](#models)
 * [hide_documentation_path](#hide_documentation_path)
@@ -805,7 +808,7 @@ The Swagger UI on Grape could be secured from unauthorized access using any midd
   
 Below are some examples of securing the Swagger UI on Grape installed along with Ruby on Rails:
 
-- The examples are showing WineBouncer with Doorkeeper;
+- The WineBouncer and Doorkeeper gems are used in the examples;
 - 'rails' and 'wine_bouncer' gems should be required prior to 'grape-swagger' in boot.rb;
 - This works with a fresh PR to WineBouncer which is yet unmerged - [WineBouncer PR](https://github.com/antek-drzewiecki/wine_bouncer/pull/64).
 
@@ -846,7 +849,7 @@ Further on, the guard could be used, where necessary, for endpoint access protec
 ```
 
 And, finally, if you want to not only restrict the access, but to completely hide the endpoint from unauthorized 
-users, you could use pass a lambda to the :hidden key of a endpoint's description:
+users, you could pass a lambda to the :hidden key of a endpoint's description:
    
 ```ruby
   not_admins = lambda { |token=nil| token.nil? || !User.find(token.resource_owner_id).admin? }