review comment fixes

msteams-platform/includes/deprecation-note.md

@@ -10,19 +10,17 @@
 >
 > **If you've already built O365 Connectors**
 >
-> * Create a Power Automate connector: Power Automate enhances the widely used **Workflows** apps in Teams. It's the scalable and secure approach to transmit data programmatically into and out of Teams. If you adopt this method, you can create one or two workflow templates for posting alerts from your product to Teams channels. This approach simplifies user adoption of the new method. For more information, see [Power Automate for enterprise developers, ISVs, and partners.](/power-automate/developer/dev-enterprise-intro)
+> * Create a Power Automate connector: Power Automate enhances the widely used **Workflows** apps in Teams. It's the scalable and secure approach to transmit data programmatically into and out of Teams. If you adopt this method, you can create workflow templates for posting alerts from your product to Teams channels. This approach simplifies user adoption of the new method. For more information, see [Power Automate for enterprise developers, ISVs, and partners.](/power-automate/developer/dev-enterprise-intro)
 >
 > * Update your Teams app: You can enhance your current Teams app. For example, you can enable users to set up proactive messages based on trigger events within your system. For more information, see [how bots can post to channels through proactive messages.](../bots/how-to/conversations/send-proactive-messages.md#send-the-message)
 >
 > **Known issues**
 >
-> * Workflows app can't post in private channels.
-> * Workflows can't post messages using the payload or format of O365 Connectors. Workflows support only Adaptive Cards and don't support the older message card format. For more information, see [how to convert connector message card format to Adaptive Card.](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/tools/message-card-to-ac-transformation)
-> * Workflows aren't available in Government community cloud (GCC) High.
-> * Workflows don't include connectors such as, Jenkins, DataDog, and so on.
+> * Workflows app can't post in private channels as a flow bot. However, it can post on behalf of a user.
+> * Workflows support Adaptive Cards only. It doesn't support the older message card format that O365 Connectors use. The support for the use of message card format within Workflows becomes available from mid-October. For more information, see [how to convert connector message card format to Adaptive Card.](https://github.com/OfficeDev/Microsoft-Teams-Samples/tree/main/tools/message-card-to-ac-transformation).
+> * Workflows don't yet offer third-party connectors such as DataDog, Jenkins, and so on.
 > * Workflows can only be created in your default environment.
 >
 > **Limitations**
 >
-> * Workflows don't allow you to upgrade users to premium connectors.
-> * Workflows are linked only to specific users and not to Teams team or channel.
+> Workflows are linked only to specific users (referred to as owners of the workflow) and not to Teams team or channel. Workflows can become orphan flows in the absence of an owner if no co-owners assigned. Admins can maintain continuity on the business process automated by the flow. Admins can add one or more co-owners to the workflow and grant them full control over it. They can also add authentication for connections, if any, and enable the flow if it has been disabled. For more information, see [manage orphan flows](/troubleshoot/power-platform/power-automate/flow-management/manage-orphan-flow-when-owner-leaves-org).