Regression. Remove workspace app mentions.

Author: girliemac

DIFF.md

@@ -1,41 +1,10 @@
 # What's New? - Updates from the Previous Example
 
-Now all the Blueprints examples have been updated with new Slack platform features also switched to the [workspace token](https://api.slack.com/docs/working-with-workspace-tokens) model. So what are the *diffs* in this updated example?
-
-## Creating an app
-
-To create a new "workspace app" at [https://api.slack.com/apps?new_app_token=1](https://api.slack.com/apps?new_app_token=1), instead of using the previous App creation page.
-
-## OAuth Scopes
-
-Some scopes are no longer valid with workspace apps.
-
-In previous example, these scopes were required:
-* `commands`
-* `users:read`
-* `users:read.email`
-* `chat:write:bot`
-
-In the new version, you need to enable:
-* `commands`
-* `users:read`
-* `users:read.email`
-* `chat:write`
-
-Notice that the `bot` scope is no longer supported because there is a no "bot user" for the new workspace apps.
-
-You can learn more about scopes at [https://api.slack.com/scopes](https://api.slack.com/scopes)
+Now all the Blueprints examples have been updated with new Slack platform features. So what are the *diffs* in this updated example?
 
 ## OAuth Token
 
-Your OAuth access token should begins with `-xoxa`, instead of `-xoxp`.
-
-
-## Installation and Permission
-
-When a user is installing your app, the user will be ask to choose which channel(s) to install. After the installation, the app name appears under "Apps" at the menu pane on Slack client, and this is now called `app_home`, a where your app can send DM to the user who installed your app. 
-
-Also, your slash command is only available on the channels that your app is installed, unless some user adds it on other channels.
+Your OAuth access token should begins with `-xoxb` instead of `-xoxp`. The bot tokens will be the defaul token in future.
 
 
 ## Sigining Secret