Minor doc updates

README.md

@@ -9,7 +9,7 @@ Please see the [Data Connector technical reference](docs/m-extensions.md) for mo
 
 ## Quickstart
 
-> **Note:** The steps to enable extensions changed in the June 2017 version of Power BI Desktop. Please see below for instructions for the May 2017 release. 
+> **Note:** The steps to enable extensions changed in the June 2017 version of Power BI Desktop.
 
 1. Install the [Power Query SDK](https://aka.ms/powerquerysdk) from the Visual Studio Marketplace
 2. Create a new Data Connector project
@@ -117,16 +117,3 @@ Data Connectors are currently in preview. We plan to incrementally roll out a nu
 - [ ] Development experience improvements
 
 Please report issues and feature requests through our [Github issues page](https://github.com/Microsoft/DataConnectors/issues).
-
-## Instructions for Getting Started with the May 2017 version of Power BI Desktop
-
-> These instructions apply to the May 2017 release of Power BI Desktop only. 
-
-1. Install the [Power Query SDK](https://aka.ms/powerquerysdk) from the Visual Studio Marketplace
-2. Create a new Data Connector project
-3. Define your connector logic
-4. Build the project to produce an extension file
-5. Create a `C:\Program Files\Microsoft Power BI Desktop\bin\extensions` directory
-6. Create a `PQ_ExtensionDirectory` environment variable, set its value to this directory
-7. Copy the extension file into this directory
-8. Restart Power BI Desktop

docs/m-extensions.md

@@ -288,9 +288,11 @@ Extensions can optionally implement `Refresh` (exchanging a refresh token for a
 >**Note:** Power Query extensions are evaluated in applications running on client machines.
 >Data Connectors **should not** use confidential secrets in their OAuth flows, as users may
 >inspect the extension or network traffic to learn the secret.
->Please see the [OAuth 2.0 for Native Apps](https://tools.ietf.org/html/draft-ietf-oauth-native-apps-12) draft RFC for further details of providing 
+>Please see the [OAuth 2.0 for Native Apps](https://tools.ietf.org/html/draft-ietf-oauth-native-apps-12) draft RFC for further details on providing 
 >flows that do not rely on shared secrets. 
 
+>In the future we plan to support data sources that require confidential secrets (using a proxy based mechanism).
+
 Please see the [MyGraph](../samples/MyGraph) and [Github](../samples/github) samples for more details.
 
 ### Data Source Paths