replace office store with appsource (#69)

msteams-platform/TOC.yml

@@ -69,9 +69,9 @@
 - name: Publishing
   href: ./publishing/apps-publish
   items:
-  - name: Office Store checklist
+  - name: AppSource checklist
     href: ./publishing/office-store-checklist
-  - name: Office Store guidance
+  - name: AppSource guidance
     href: ./publishing/office-store-guidance
 - name: Scenarios
   href: ./scenarios/scenarios

msteams-platform/concepts/apps/apps-overview.md

@@ -19,7 +19,7 @@ An app in Teams consists of the following parts:
 * [Activity feed integrations](~/concepts/activity-feed)
 * [Outgoing web hooks](~/concepts/outgoingwebhook.md)
 
-A Microsoft Teams app is defined by its manifest (a JSON file). Place the manifest and two icons in a .zip file, and you have an *app package* that you can install into Teams or publish through the Office Store. (For details, see [Create the package for your Microsoft Teams app](~/concepts/apps/apps-package).)
+A Microsoft Teams app is defined by its manifest (a JSON file). Place the manifest and two icons in a .zip file, and you have an *app package* that you can install into Teams or publish through AppSource. (For details, see [Create the package for your Microsoft Teams app](~/concepts/apps/apps-package).)
 
 *Teams App Studio* is a new tool that will help you to configure your application. It also contains a React control library and configurable samples for cards.  See [Getting started with Teams App Studio](~/get-started/get-started-app-studio).
 

msteams-platform/concepts/apps/apps-package.md

@@ -7,7 +7,7 @@ ms.date: 01/22/2018
 
 # Create an app package for your Microsoft Teams app
 
-App experiences in Teams are defined by their app manifest, and bundled in an app package for use in uploading or Office Store submission. You'll need an app package to test your experience in Teams, via the [upload](~/concepts/apps/apps-upload) process.
+App experiences in Teams are defined by their app manifest, and bundled in an app package for use in uploading or AppSource submission. You'll need an app package to test your experience in Teams, via the [upload](~/concepts/apps/apps-upload) process.
 
 A Teams app package is a .zip file containing the following:
 
@@ -18,7 +18,7 @@ A Teams app package is a .zip file containing the following:
 
 *Teams App Studio* is a new tool that can help configure your manifest. It also contains a React control library and configurable samples for cards.  See [Getting started with Teams App Studio](~/get-started/get-started-app-studio).
 
-Your manifest file must be named "manifest.json" and be at the top level of the upload package. Note that manifests and packages built previously might support an older version of the schema. For Teams apps and especially Office Store submission, you must use the current [manifest schema](~/resources/schema/manifest-schema).
+Your manifest file must be named "manifest.json" and be at the top level of the upload package. Note that manifests and packages built previously might support an older version of the schema. For Teams apps and especially AppSource (formerly Office Store) submission, you must use the current [manifest schema](~/resources/schema/manifest-schema).
 
 > [!TIP]
 > Specify the schema at the beginning of your manifest to enable IntelliSense or similar support from your code editor:

msteams-platform/concepts/apps/apps-upload.md

@@ -4,7 +4,6 @@ description: Describes how to upload your app in Microsoft Teams
 keywords: teams apps Upload
 ms.date: 01/02/2018
 ---
-
 # Upload an app package to Microsoft Teams
 
 To test your app experience within Microsoft Teams, you need to upload your app to Teams. Uploading adds the app to the team you select, and you and your team members can interact with it like end users.
@@ -16,7 +15,7 @@ For bots designed only for 1:1 contexts, see [Adding a bot for 1:1 chat only](~/
 
 ## Create your upload package
 
-For development as well as Office Store submission you must create an uploadable package that contains the information to describe your experience. The package, a .zip file, contains the application manifest and icons that uniquely define your experience.
+For development as well as AppSource (formerly Office Store) submission you must create an uploadable package that contains the information to describe your experience. The package, a .zip file, contains the application manifest and icons that uniquely define your experience.
 
 To create an upload package, see [Create the package for your Microsoft Teams app](~/concepts/apps/apps-package).
 
@@ -58,7 +57,7 @@ If the app contains tabs, users can pin them to any channel on the team using th
 
 3. Accept the consent prompt.
 
-4. Configure your tab via its [configuration page](~/concepts/tabs/tabs-configuration) and choose **Save**. 
+4. Configure your tab via its [configuration page](~/concepts/tabs/tabs-configuration) and choose **Save**.
 
   ![The Add a tab dialog box, featuring a gallery of available tabs](~/assets/images/tab_gallery.png)
 
@@ -78,7 +77,7 @@ With the app loaded in the team, users can set up a Connector on any channel in
 
 2. Select your Connector from the **Uploaded** section at the bottom.
 
-3. Configure your Connector via its [configuration page](~/concepts/connectors) and choose **Save**. 
+3. Configure your Connector via its [configuration page](~/concepts/connectors) and choose **Save**.
 
   ![The Add a tab dialog box, featuring a gallery of available tabs.](~/assets/images/connector_gallery.png)
 

msteams-platform/concepts/bots/bots-create.md

@@ -36,7 +36,7 @@ To make your bot experience Teams-ready:
 
 1. [Create an uploadable app package](~/concepts/apps/apps-package) and [upload it to a team](~/concepts/apps/apps-upload) to test it in action.
 2. Add [tabs](~/concepts/tabs/tabs-overview) or [other capabilities](~/concepts/apps/apps-overview#map-your-scenario-to-teams-capabilities) to make your experience shine in Teams.
-3. [Submit your final app package](~/publishing/apps-publish) for publication in the Office Store.
+3. [Submit your final app package](~/publishing/apps-publish) for publication in AppSource (formerly known as Office Store).
 
 > [!NOTE]
 > ## Bots and Microsoft Azure

msteams-platform/concepts/bots/bots-overview.md

@@ -48,7 +48,7 @@ Follow these links to build a great Teams bot:
 - [Create and register your bot in the Bot Framework](~/concepts/bots/bots-create): Take advantage of the great tools, documentation, and community provided by the Bot Framework team.
 - [Develop your bot](~/concepts/bots/bots-conversations): Add basic conversation flow and leverage channel-specific functionality. If you develop in .NET or Node.js, use our [extensions for the Bot Builder SDK](~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk) to simplify your work.
 - [Test your bot](~/concepts/bots/bots-test): Add your bot for 1:1 or team conversations to see it in action.
-- [Publish your bot](~/publishing/apps-publish): Create your Teams package, add other capabilities, and submit it to the Office Store.
+- [Publish your bot](~/publishing/apps-publish): Create your Teams package, add other capabilities, and submit it to AppSource.
 
 ## What you need to know: Teams App Studio
 *Teams App Studio* is a new tool that can help configure your manifest and your app. It also contains a React control library and configurable samples for cards.  See [Getting started with Teams App Studio](~/get-started/get-started-app-studio).

msteams-platform/concepts/bots/bots-test.md

@@ -71,6 +71,6 @@ To stop your bot receiving messages, go to your Bot Dashboard and edit the Micro
 
 To remove your bot completely from Teams, go to your Bot Dashboard and edit the Microsoft Teams channel. Choose the **Delete** button at the bottom. This prevents users from discovering, adding, or interacting with your bot. Note that this does not remove the bot from other users' Teams instances, although it will cease functioning for them as well.
 
-## Removing your bot from the Office Store
+## Removing your bot from AppSource
 
-If you want to remove your bot from your Teams app in the Office Store, you must remove the bot from your app manifest and resubmit your app for validation. See [Publish your Microsoft Teams app to the Office Store](~/publishing/apps-publish) for more information.
+If you want to remove your bot from your Teams app in AppSource (formerly Office Store), you must remove the bot from your app manifest and resubmit your app for validation. See [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish) for more information.

msteams-platform/concepts/connectors.md

@@ -3,14 +3,13 @@ title: Office 365 Connectors
 description: Describes how to get started with Office 365 Connectors in Microsoft Teams
 keywords: teams o365 connector
 ---
-
 # Office 365 Connectors for Microsoft Teams
 
 Office 365 Connectors are a great way to push your app's rich content into Microsoft Teams. Any user can connect a team to services like Trello, GitHub, Bing News, or Twitter and get notified of the team's activity in that service. From tracking a team's progress in Trello to following important hashtags in Twitter, Office 365 Connectors help your team to stay in sync and get more done.
 
 You can even add actions to your content, turning them into *actionable messages*, so that users can complete tasks directly in the channel. (To learn more about actionable messages in general, see [Actionable messages in Outlook, Office 365 Groups, and Microsoft Teams](https://docs.microsoft.com/en-us/outlook/actionable-messages/).)
 
->**New:** With Microsoft Teams apps, you can add your existing Office 365 Connector or build a new one to include in Microsoft Teams. See [Build your own Connector](https://docs.microsoft.com/en-us/outlook/actionable-messages/connectors-dev-dashboard#build-your-own-connector) for more information. 
+>**New:** With Microsoft Teams apps, you can add your existing Office 365 Connector or build a new one to include in Microsoft Teams. See [Build your own Connector](https://docs.microsoft.com/en-us/outlook/actionable-messages/connectors-dev-dashboard#build-your-own-connector) for more information.
 
 ## Access existing Office 365 Connectors from Microsoft Teams
 
@@ -215,14 +214,14 @@ The following steps use PowerShell. We assume that you have this installed and a
 
 ## Registering your Connector
 
-With Microsoft Teams apps, you can distribute your registered Connector as part of your app package. Whether as a standalone solution, or one of several [capabilities](~/overview#apps-in-microsoft-teams) that your experience enables in Teams, you can [package](~/concepts/apps/apps-package) and [publish](~/publishing/apps-publish) your Connector as part of your Office Store submission, or you can provide it to users directly for uploading within Teams.
+With Microsoft Teams apps, you can distribute your registered Connector as part of your app package. Whether as a standalone solution, or one of several [capabilities](~/overview#apps-in-microsoft-teams) that your experience enables in Teams, you can [package](~/concepts/apps/apps-package) and [publish](~/publishing/apps-publish) your Connector as part of your AppSource submission, or you can provide it to users directly for uploading within Teams.
 
 To distribute your Connector, you need to register by using the [Connectors Developer Dashboard](https://go.microsoft.com/fwlink/?LinkID=780623). To have your Connector work in Microsoft Teams, select **Microsoft Teams** under **Enable this integration for**.
 
 <img alt="Screenshot of enabling the Connector for Microsoft Teams" src="~/assets/images/connectors/connector_developer_portal.png" height="185" width="336">
 
 > [!IMPORTANT]
-> After you choose **Save** in the Connectors Developer Dashboard, your Connector is registered. Do not choose **Publish to Store** (which appears after you choose **Save**); if you want to publish your Connector in the Office Store, follow the instructions in [Publish your Microsoft Teams app to the Office Store](~/publishing/apps-publish).
+> After you choose **Save** in the Connectors Developer Dashboard, your Connector is registered. Do not choose **Publish to Store** (which appears after you choose **Save**); if you want to publish your Connector in AppSource, follow the instructions in [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish).
 
 You can download the auto-generated Teams app manifest from the portal. Before you can use it to test or publish your app, though, you must do the following:
 
@@ -291,4 +290,4 @@ To verify that an `HttpPOST` action is working correctly, use your [custom incom
 > [!NOTE]
 > Currently, we do not support users configuring your Connector externally via the **Connect to Office 365** button. Users must visit Microsoft Teams first to add a Connector.
 
-When your app is ready for submission, follow the process to [publish your app to the Office Store](~/publishing/apps-publish).
+When your app is ready for submission, follow the process to [publish your app to AppSource](~/publishing/apps-publish).

msteams-platform/concepts/messaging-extensions.md

@@ -21,7 +21,7 @@ How would you use messaging extensions? Here are a few possibilities:
 
 ## Add a messaging extension to your app
 
-Building a messaging extension involves implementing familiar Microsoft Teams developer-platform concepts like bot APIs, rich cards, and tabs.
+Building a messaging extension involves implementing familiar Microsoft Teams developer platform concepts like bot APIs, rich cards, and tabs.
 
 At its core, a messaging extension is a cloud-hosted service that listens to user requests and responds with structured data, such as cards. You integrate your service with Microsoft Teams via Bot Framework `Activity` objects. Our .NET and Node.js [extensions for the Bot Builder SDK](~/get-started/code#microsoft-teams-extensions-for-the-bot-builder-sdk) can help you add messaging extension functionality to your app.
 
@@ -131,7 +131,7 @@ In the app manifest, your command item is an object with the following structure
   ]
 }
 ```
- 
+
 ### Test via uploading
 
 You can test your messaging extension by uploading your app. See [Uploading your app in a team](~/concepts/apps/apps-upload) for details.
@@ -148,7 +148,7 @@ Most of your work involves the `onQuery` event, which handles all interactions i
 If you set `canUpdateConfiguration` to `true` in the manifest, you enable the **Settings** menu item for your messaging extension and must also handle `onQuerySettingsUrl` and `onSettingsUpdate`.
 
 > [!IMPORTANT]
-> Messaging extensions that use `canUpdateConfiguration` can't be published in the Office Store at this time.
+> Messaging extensions that use `canUpdateConfiguration` can't be published in AppSource at this time.
 
 ### Handle onQuery events
 

msteams-platform/overview.md

@@ -25,7 +25,7 @@ In these topics, you'll find the information you need to bring your content, app
 | - | - |
 | [**Get Started**](~/get-started/get-started) | Develop, host and upload your first app and understand how apps work in Teams. |
 | [**Concepts**](~/concepts/concepts-overview) | Learn more about creating Teams apps, and find everything you need to know about the entire range of capabilities in Teams: tabs, bots, connectors, messaging extensions, and more. |
-| [**Publishing**](~/publishing/apps-publish) | Want to publish your Teams app in the Office Store? Look here for the steps and guidelines. |
+| [**Publishing**](~/publishing/apps-publish) | Want to publish your Teams app in AppSource? Look here for the steps and guidelines. |
 | [**Scenarios**](~/scenarios/scenarios) | Go deep into end-to-end scenarios. |
 | [**Resources**](~/resources/resource-overview) | Find all those nitty-gritty details you need to build a Teams app, such as a design topic, or a manifest schema reference. |
 | [**Troubleshooting**](~/troubleshoot/troubleshoot) | If your app isn't behaving as expected, check here. |