MicrosoftDocs · NormSohl · Jan 31, 2018 · Jan 31, 2018 · Jan 31, 2018 · Jan 31, 2018
diff --git a/msteams-platform/assets/images/bots/bfregister.png b/msteams-platform/assets/images/bots/bfregister.png
diff --git a/msteams-platform/concepts/activity-feed.md b/msteams-platform/concepts/activity-feed.md
@@ -2,13 +2,11 @@
 title: Activity feed
 description: Describes the activity feed and how to use it in your apps
 keywords: teams activity feed
+msdate: 01/31/2018
 ---
 
 # Notify users through the activity feed in Microsoft Teams
 
-> [!NOTE]
-> Activity feed support is available only in the [Public Developer Preview](~/resources/general/developer-preview). Additionally, many features in this document are under construction and subject to change.
-
 The activity feed in Microsoft Teams is the user's single inbox for all activity across Teams. The feed aggregates important content from the following:
 
 * Teams/channels
@@ -17,16 +15,14 @@ The activity feed in Microsoft Teams is the user's single inbox for all activity
 
 If your app posts cards and other messages into a channel, they'll automatically show up in the user's feed if he or she has followed that channel.
 
-> [!NOTE]
-> The following features are coming soon to the Public Developer Preview.
-
 Additionally, you can also send personal (1:1 chat) messages into the feed as preview cards summarizing your app's activity. You can construct the message such that choosing the card navigates the user straight to the message or object that triggered the notification, such as an entity in a tab. This allows the user to see the full content of the activity.
 
 ## Sending content to the activity feed
 
 Activity feed notification leverages your existing integration with the Bot Framework APIs.  You can flag specific messages to generate notifications which appear in the activity feed. This allows generating higher levels of engagement by creating alerts on web/desktop and mobile apps.
 
 When constructing your message, the following fields should be populated so that the correct preview content can be shown in the feed:
+
 * `message.text`, which shows up as the activity title
 * `message.summary`, which shows up as the activity text
 
@@ -35,7 +31,7 @@ When constructing your message, the following fields should be populated so that
 
 In addition to simply appearing in the feed, your app can also encode a deep link URL to an entity, such as your app’s tab. This drives user engagement to your app’s tab by allowing "one-click" navigation to that tab’s content.
 
-#### REST API sample
+### REST API sample
 
 For a message to be eligible to be included in the feed, simply mark an existing bot message with a special property, which indicates it should generate a notification:
 

diff --git a/msteams-platform/concepts/messaging-extensions.md b/msteams-platform/concepts/messaging-extensions.md
@@ -3,13 +3,10 @@ title: Develop messaging extensions
 description: Describes how to get started with messaging extensions in Microsoft Teams
 keywords: teams messaging extensions messaging extensions
 ---
-# Preview: Develop messaging extensions for Microsoft Teams
+# Develop messaging extensions for Microsoft Teams
 
 Messaging extensions are a powerful new way for users to engage with your app within Microsoft Teams. With this capability, users can query for information from your service and post that information, in the form of rich cards, right into the channel conversation.
 
-> [!IMPORTANT]
-> messaging extensions are available only in [Public Developer Preview](~/resources/general/developer-preview). Many details in this document are subject to change.
-
 ![Example of messaging extension card](~/assets/images/compose-extensions/ceexample.png)
 
 Messaging extensions appear along the bottom of the compose box. A few are built in, such as Emoji, Giphy, and Sticker. Choose the **More Options** (**&#8943;**) button to see other messaging extensions, including those that you add from the app gallery or upload yourself.

diff --git a/msteams-platform/resources/dev-preview/developer-preview-features.md b/msteams-platform/resources/dev-preview/developer-preview-features.md
@@ -2,26 +2,11 @@
 title: Features in the Public Developer Preview
 description: Describes the features in the Public Developer Preview of Microsoft Teams
 keywords: teams preview developer features
-ms.date: 01/20/2018
+ms.date: 01/31/2018
 ---
 # Features in the Public Developer Preview for Microsoft Teams
 
-The following are available to users of the Public Developer Preview ring. See [What is the Public Developer Preview for Microsoft Teams?](~/resources/general/developer-preview) for more information on enabling it for your development tenant.
+As of January 31, 2018 there are no new features in Developer Preview. When this changes new items will be added here.
 
-The following features are available in the Public Developer Preview as of December 12, 2017.
+See [What is the Public Developer Preview for Microsoft Teams?](~/resources/general/developer-preview) for more information on enabling it for your development tenant.
 
-## Apps in Microsoft Teams
-
-Apps in Microsoft Teams allow you to make your service available to users through a single Teams App package, which includes bots, tabs, connectors and messaging extensions. Learn more [here](~/overview).
-
-### AppSource (formerly Office Store)
-
-AppSource provides a listing of all apps available in Microsoft Teams spanning various categories. Developers can add their apps by [submitting their apps to AppSource](~/publishing/apps-publish).
-
-### Messaging extensions
-
-Messaging extensions make it easy for users to query for information from your service and post them into conversations in the form of rich cards. Learn more [here](~/concepts/-extensimessaging-extensions).
-
-### Activity feed
-
-Activity feed support allows apps to send messages using the Bot Framework without having to implement a conversational bot. It also enables your apps to mark messages as important and to post messages to the activity feed. Learn more [here](~/concepts/activity-feed).
diff --git a/msteams-platform/resources/schema/manifest-schema.md b/msteams-platform/resources/schema/manifest-schema.md
@@ -232,7 +232,7 @@ The value must be a valid HTML color code starting with '#', for example `#4464e
 
 ## configurableTabs
 
-*Optional*
+**Optional**
 
 Used when your app experience has a team channel tab experience that requires extra configuration before it is added.  Configurable tabs are supported only in the teams scope, and currently only one tab per app is supported.
 
@@ -246,7 +246,7 @@ The object is an array with all elements of the type `object`.  This block is re
 
 ## staticTabs
 
-*Optional*
+**Optional**
 
 Defines a set of tabs that can be "pinned" by default, without the user adding them manually. Static tabs declared in `personal` scope are always pinned to the app's personal experience. Static tabs declared in the `team` scope are currently not supported. 
 
@@ -262,7 +262,7 @@ The object is an array (maximum of 16 elements) with all elements of the type `o
 
 ## bots
 
-*Optional*
+**Optional**
 
 Defines a bot solution, along with optional information such as default command properties.
 
@@ -286,23 +286,20 @@ An optional list of commands that your bot can recommend to users. The object is
 
 ## connectors
 
-*Optional*
-App support for connectors is only available in the [Public Developer Preview](~/resources/general/developer-preview). Connectors themselves are generally available.
+**Optional**
 
 The `connectors` block defines an Office 365 Connector for the app.
 
 The object is an array (maximum of 1 element) with all elements of type `object`. This block is required only for solutions that provide a Connector.
-     
+
 |Name| Type| Maximum size | Required | Description|
 |---|---|---|---|---|
 |`connectorId`|String|64 characters|✔|A unique identifier for the Connector that matches its ID in the Connectors Developer Portal.|
 |`scopes`|Array of enum|1|✔|Specifies whether the Connector offers an experience in the context of a channel in a `team`, or an experience scoped to an individual user alone (`personal`). Currently, only the `team` scope is supported.|
 
 ## composeExtensions
 
-*Optional*
-
->[Public Developer Preview](~/resources/general/developer-preview) only
+**Optional**
 
 Defines a messaging extension for the app.
 
@@ -318,6 +315,7 @@ The object is an array (maximum of 1 element) with all elements of type `object`
 |`commands`|Array of object|1|✔|Array of commands the messaging extension supports|
 
 ### composeExtensions.commands
+
 Your messaging extension should declare one or more commands. Each command appears in Microsoft Teams as a potential interaction from the UI-based entry point.
 
 Each command item is an object with the following structure:
@@ -335,7 +333,7 @@ Each command item is an object with the following structure:
 
 ## permissions
 
-*Optional*
+**Optional**
 
 An array of `string` which specifies which permissions the app requests, which lets end users know how the extension will perform. The following options are non-exclusive:
 
@@ -344,7 +342,7 @@ An array of `string` which specifies which permissions the app requests, which l
 
 ## validDomains
 
-*Optional*, except **Required** for apps with tabs
+**Optional**, except **Required** for apps with tabs
 
 A list of valid domains from which the extension expects to load any content. Domain listings can include wildcards, for example `*.example.com`. If your tab configuration or content UI needs to navigate to any other domain besides the one use for tab configuration, that domain must be specified here.