Update README.md

gueldner · web-flow · commit 32fbea86a10c · 2019-02-11T17:31:32.000-08:00
diff --git a/README.md b/README.md
@@ -35,7 +35,7 @@ Unless there is a compelling reason, you should use browser-based authentication
 
 ### 2.1. Browser-based authentication
 
-First you must register an application through your [settings page](https://medium.com/me/settings) on Medium. Then we will supply you a `clientId` and a `clientSecret` with which you may access Medium’s API. Each integration should have its own `clientId` and `clientSecret`. The `clientSecret` should be treated like a password and stored securely.
+First you must request access by emailing yourfriends@medium.com. Then we will then grant you access to a `clientId` and a `clientSecret` on your [settings page](https://medium.com/me/settings) with which you may access Medium’s API. Each integration should have its own `clientId` and `clientSecret`. The `clientSecret` should be treated like a password and stored securely.
 
 The first step is to acquire a short term authorization code by sending the user to our authorization URL so they can grant access to your integration.
 
@@ -170,7 +170,7 @@ With the following parameters:
 
 Self-issued access tokens (described in user-facing copy as integration tokens) are explicitly designed for desktop integrations where implementing browser-based authentication is non-trivial, or software like plugins where it is impossible to secure a client secret. You should not request that a user give you an integration token if you don’t meet these criteria. Users will be cautioned within Medium to treat integration tokens like passwords, and dissuaded from making them generally available.
 
-Users can generate an access token from the [Settings page](https://medium.com/me/settings) of their Medium account.
+Users can request an access token by emailing yourfriends@medium.com. We will then grant access on the [Settings page](https://medium.com/me/settings) of their Medium account.
 
 You should instruct your user to visit this URL and generate an integration token from the `Integration Tokens` section. You should suggest a description for this
 token - typically the name of your product or feature - and use it consistently for all users.
