[4728451][Doc Improvement] rename Bot Framework SDK and TeamsFX SDK-4

msteams-platform/concepts/deploy-and-publish/apps-upload.md

@@ -22,7 +22,7 @@ You can upload Microsoft Teams apps without having to publish to your organizati
 > * App upload and installation are supported in Teams for desktop and web (availability depends on your organization’s app setup policies and cloud environment)
 > * We recommend you to avoid multiple uploads of your message extension app to Teams, as it results in multiple instances of the message extension.
 
-Users can't chat with bots that aren't connected to a Microsoft Teams app such as Azure bots created through the Bot Framework or Power Virtual Agents. We recommend you to create a new Teams app connected to the Azure Bot using the [Developer Portal](../build-and-test/manage-your-apps-in-developer-portal.md#configure), publish it to Teams, and allow users to install the app using the [app permission policies](/microsoftteams/teams-app-permission-policies#edit-an-app-permission-policy).
+Users can't chat with bots that aren't connected to a Microsoft Teams app such as Azure bots created through the Azure portal or Power Virtual Agents. We recommend you to create a new Teams app connected to the Azure Bot using the [Developer Portal](../build-and-test/manage-your-apps-in-developer-portal.md#configure), publish it to Teams, and allow users to install the app using the [app permission policies](/microsoftteams/teams-app-permission-policies#edit-an-app-permission-policy).
 
 If you want to test the app, you can assign users an [app setup policy](/microsoftteams/teams-app-setup-policies#manage-app-setup-policies) that allows uploading custom apps and chat with the Azure bot through a direct link to a chat.
 

msteams-platform/concepts/deploy-and-publish/appsource/prepare/teams-store-validation-guidelines.md

@@ -499,7 +499,7 @@ App packages must be correctly formatted and include all required information an
 The app manifest defines your app's configuration.
 
 * Your app manifest must conform to a publicly released app manifest schema. For more information, see [app manifest reference](/microsoft-365/extensibility/schema). Don't submit your app using a preview version of the app manifest.
-* If your app includes a bot or message extension, details in the app manifest must be consistent with Bot Framework metadata including bot name, logo, privacy policy link, and terms of service link.
+* If your app includes a bot or message extension, details in the app manifest must be consistent with bot's metadata including bot name, logo, privacy policy link, and terms of service link.
 * If your app uses Microsoft Entra ID for authentication, include the Microsoft Entra Application (client) ID in the app manifest. For more information, see the [app manifest reference](/microsoft-365/extensibility/schema/root-web-application-info-nested-app-auth-info).
 
 ### Uses of latest app manifest schema
@@ -1360,7 +1360,7 @@ Apps that consist of notification only bots provide user value by triggering use
 
 <details><summary>Bot metadata information</summary>
 
-* Bot information in the app manifest (bot name, logo, privacy link, and terms of service link) must be consistent with the Bot Framework metadata. [*Must fix*]
+* Bot information in the app manifest (bot name, logo, privacy link, and terms of service link) must be consistent with the bot's metadata. [*Must fix*]
 
 * Ensure that the bot ID in the app manifest matches with bot ID in the last Teams Store published version of your app. Changing bot IDs in an app update leads to permanent loss of all user interaction history with the bot for existing users of your app and starts a new conversation chain with the new Bot ID. [*Must fix*]
 

msteams-platform/get-started/tool-options-and-code-samples.md

@@ -51,9 +51,9 @@ To start building your Teams app, you can select the tools and SDKs based on you
 
 | App capabilities | User interactions | Recommended tools | SDKs | Languages |
 |--------|-------------|--------|--------|--------|
-| **Tabs** | A full-screen embedded web experience. | VS Code or Visual Studio with Agents Toolkit extension, or [Microsoft 365 Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) (previously known as TeamsFx CLI) if you prefer using CLI | [Teams JavaScript client library](/javascript/api/overview/msteams-client#microsoft-teams-javascript-client-library) for UI functionalities, SharePoint Framework (SPFx), and Microsoft Graph SDK | C#, TypeScript, and JavaScript (including React) |
-| **Bots** | A chat bot that converses with members. |VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [TeamsFx SDK](/javascript/api/@microsoft/teamsfx), [Bot Framework SDK](https://dev.botframework.com/), [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md), and Microsoft Graph SDK | C#, TypeScript, and JavaScript |
-| **Message extensions** | Shortcuts for inserting external content into a conversation or taking action on messages. | VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [TeamsFx SDK](/javascript/api/@microsoft/teamsfx), [Bot Framework SDK](https://dev.botframework.com/), [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md), and Microsoft Graph SDK | C#, TypeScript, and JavaScript |
+| **Tabs** | A full-screen embedded web experience. | VS Code or Visual Studio with Agents Toolkit extension, or [Microsoft 365 Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [Teams JavaScript client library](/javascript/api/overview/msteams-client#microsoft-teams-javascript-client-library) for UI functionalities, SharePoint Framework (SPFx), and Microsoft Graph SDK | C#, TypeScript, and JavaScript (including React) |
+| **Bots** | A chat bot that converses with members. |VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md) and Microsoft Graph SDK | C#, TypeScript, Python (developer preview), and JavaScript |
+| **Message extensions** | Shortcuts for inserting external content into a conversation or taking action on messages. | VS Code or Visual Studio with Agents Toolkit extension, or [Agents Toolkit CLI](../toolkit/Microsoft-365-Agents-Toolkit-CLI.md) if you prefer using CLI | [Teams AI library](../bots/how-to/teams-conversational-ai/teams-conversation-ai-overview.md) and Microsoft Graph SDK | C#, TypeScript, Python (developer preview), and JavaScript |
 
 > [!NOTE]
 >

msteams-platform/graph-api/meeting-transcripts/overview-transcripts.md

@@ -88,7 +88,7 @@ You can use the following types of change notification for your app:
 
 For more information about how your app can know when a transcript or recording is available after the online meeting or ad hoc call ends, see [get notified when transcripts and recordings are available](/graph/teams-changenotifications-callrecording-and-calltranscript).
 
-For more information about how your app can know when the meetings ends, see [subscribe to change notifications](/graph/teams-changenotifications-callrecording-and-calltranscript) and [use Bot Framework to get meeting ID and organizer ID](/graph/teams-changenotifications-callrecording-and-calltranscript).
+For more information about how your app can know when the meetings ends, see [subscribe to change notifications](/graph/teams-changenotifications-callrecording-and-calltranscript).
 
 > [!IMPORTANT]
 >

msteams-platform/graph-api/rsc/resource-specific-consent.md

@@ -59,11 +59,11 @@ A limited set of RSC permissions have been reviewed by Microsoft privacy and sec
 
 ### RSC-based data access APIs
 
-Microsoft Graph SDK, Microsoft Bot Framework SDK, and Microsoft TeamsJS client library support fine-grained data access through RSC. The supported modes and resource types vary across the API surfaces.
+Microsoft Graph SDK, Teams AI library, and Microsoft TeamsJS client library support fine-grained data access through RSC. The supported modes and resource types vary across the API surfaces.
 
 | RSC mode | Supported SDKs | App manifest version | Resource types | RSC-related controls for the entire tenant | Who can consent to RSC permissions? |
 |---------|---------|---------|---------|---------|---------|
-|Application| • Microsoft Graph  <br> • Microsoft Bot Framework | >=v1.6 | Teams, chats, and meetings | • Microsoft Graph-based controls for chats and meetings <br> • Microsoft Entra admin center-based controls for Teams |• Team: A team owner or member <br> • Chat: A chat member <br> • Meeting: A meeting organizer or presenter |
+|Application| • Microsoft Graph  <br> • Teams AI library | >=v1.6 | Teams, chats, and meetings | • Microsoft Graph-based controls for chats and meetings <br> • Microsoft Entra admin center-based controls for Teams |• Team: A team owner or member <br> • Chat: A chat member <br> • Meeting: A meeting organizer or presenter |
 | Delegated | Microsoft Teams Client | >=v1.12 | Teams, chats, meetings, and users | Always on | Any user authorized to install an app in the specific scope. |
 
 > [!NOTE]