diff --git a/msteams-platform/tabs/what-are-tabs.md b/msteams-platform/tabs/what-are-tabs.md
index a591dd0aa6c..d317e7cedfd 100644
--- a/msteams-platform/tabs/what-are-tabs.md
+++ b/msteams-platform/tabs/what-are-tabs.md
@@ -10,16 +10,16 @@ ms.owner: ryanbliss
# Build tabs for Teams
-Tabs are client-aware webpages embedded in Microsoft Teams, Outlook, and Microsoft 365. They're simple HTML `` tags that point to domains declared in the app manifest and can be added as part of a channel inside a team, group chat, or personal app for an individual user. You can include custom tabs with your app to embed your own web content in Teams or add Teams-specific functionality to your web content. For more information, see [Teams JavaScript client library](/javascript/api/overview/msteams-client#microsoft-teams-javascript-client-library).
+Tabs are client-aware webpages embedded in Microsoft Teams, Outlook, and Microsoft 365. They use simple HTML `` tags that point to domains declared in the app manifest and can be added as a channel tab within a team, group chat tab, or personal tab for an individual developer. Developers include custom tabs with their app to embed web content in Teams or add Teams-specific functionality to existing web content. For more information, see [Teams JavaScript client library](/javascript/api/overview/msteams-client#microsoft-teams-javascript-client-library).
> [!IMPORTANT]
> Custom tabs are available in Government Community Cloud (GCC), GCC High, Department of Defense (DoD), and Teams operated by 21Vianet.
-There are two types of tabs, static and configurable tabs. These tabs can be utilized in three distinct scopes: `personal`, `groupchat`, and `teams`. [Personal (static) tabs](~/tabs/how-to/create-personal-tab.md), along with personal-scoped bots, are part of the personal apps that are scoped to a single user and pinned to the left navigation bar for easy access. Personal (static) tabs in personal scope continue to work the same way. However, you can now [extend static tabs](~/tabs/how-to/create-personal-tab.md#extend-static-tabs-to-group-chat-channels-and-meetings) to group chats, channels, or meetings with a [customizable experience.](~/tabs/how-to/create-personal-tab.md#customizing-your-static-tab-in-chats-or-meetings)
+Developers work with two types of tabs: static and configurable. Developers use these tabs in three distinct scopes: `personal`, `groupchat`, and `teams`. [Personal (static) tabs](~/tabs/how-to/create-personal-tab.md) and personal-scoped bots form part of the personal apps that serve a single developer and remain pinned to the left navigation bar for quick access. Personal (static) tabs continue to operate the same way. However, developers now [extend static tabs](~/tabs/how-to/create-personal-tab.md#extend-static-tabs-to-group-chat-channels-and-meetings) to group chats, channels, or meetings with a [customizable experience.](~/tabs/how-to/create-personal-tab.md#customizing-your-static-tab-in-chats-or-meetings)
-Tabs in chats, channels, or meetings behave more like apps, as you can pin only one tab per app. For example, you can only pin a single YouTube app tab in a meeting. Static tabs in meetings can also be prepinned in meetings by IT Admins.
+Tabs in chats, channels, or meetings operate more like apps, as developers can pin only one tab per app. For example, a single YouTube app tab appears in a meeting. Static tabs in meetings also support prepinned configurations by IT Admins.
-The following images show tabs added to different contexts in Teams:
+The following images show tabs added in various Teams contexts:
# [Personal](#tab/personal)
@@ -55,15 +55,13 @@ The following images show tabs added to different contexts in Teams:
Following are a few benefits of static tabs in chats, channels, and meetings:
-* **Pinnable and instant**: You can pin apps with static tabs from the add a tab **+** icon in chats, channels, and meetings. These tabs can be unpinned and don't have the mandatory configuration dialog, which allows you to create tabs that function more like apps.
+* **Pinnable and instant**: Developers pin apps with static tabs using the add a tab **+** icon in chats, channels, and meetings. These tabs remain unpinned and omit the mandatory configuration dialog, allowing developers to create tabs that act more like standalone apps.
+* **Unified**: Developers create one static tab that operates in personal and group scopes such as chat, channel, and meeting tabs.
+* **Optional configuration**: Developers change the default URL in the tab instance by updating the `contentUrl` property in the app after the tab is pinned in Teams.
-* **Unified**: You can create one static tab that work in personal and group scopes such as chat, channel, and meeting tabs.
+[Channel or group tabs](~/tabs/how-to/create-channel-group-tab.md) (configurable tabs) deliver content to channels and group chats and create collaborative spaces around web-based content.
-* **Optional configuration**: You can change the default URL in your tab instance by changing the `contentUrl` property of your app after it's pinned in Teams.
-
-[Channel or group tabs](~/tabs/how-to/create-channel-group-tab.md) also known as configurable tabs, deliver content to channels and group chats and is a way to create collaborative spaces around dedicated web-based content.
-
-The following table helps you determine the best fit for your app:
+The following table helps developers determine the best fit for an app:
| | Personal | Channels | Group chat | Meetings | Calling |
| --- |:---:|:---:|:---:|:---:|:---:|
@@ -71,54 +69,54 @@ The following table helps you determine the best fit for your app:
|[Configurable tabs](~/tabs/how-to/create-channel-group-tab.md)|❌|✔️|✔️|✔️|❌|
> [!NOTE]
-> If you have both [configurable tab](~/tabs/how-to/create-tab-pages/configuration-page.md) and [static tab](~/tabs/how-to/create-personal-tab.md) defined in your app manifest for a specific scope, Teams pins the static tab by default.
+> If both [configurable tab](~/tabs/how-to/create-tab-pages/configuration-page.md) and [static tab](~/tabs/how-to/create-personal-tab.md) are defined in the app manifest for a specific scope, Teams pins the static tab by default.
-You can [create a content page](~/tabs/how-to/create-tab-pages/content-page.md) as part of a personal static tab, channel or group tab, or dialog (referred as task module in TeamsJS v1.x). You can [create a configuration page](~/tabs/how-to/create-tab-pages/configuration-page.md) that enables users to configure Microsoft Teams app and use it to configure a personal, channel, or group chat tab, a messaging extension, or a connector card for Microsoft 365 Groups. You can permit users to reconfigure your tab after installation and [create a tab removal page](~/tabs/how-to/create-tab-pages/removal-page.md) for your application. When you build a Teams app that includes a tab, you must test how your [tab functions on both the Android and iOS Teams clients](~/tabs/design/tabs-mobile.md). Your tab must [get context](~/tabs/how-to/access-teams-context.md) through basic information, locale and theme information, and `entityId` or `subEntityId` that identifies what is in the tab.
+Developers create a [content page](~/tabs/how-to/create-tab-pages/content-page.md) as part of a personal static tab, channel tab, group tab, or dialog (referred to as task module in TeamsJS v1.x). Developers also build a [configuration page](~/tabs/how-to/create-tab-pages/configuration-page.md) that enables users to configure a Microsoft Teams app. This page applies to personal, channel, or group chat tabs, messaging extensions, or connector cards for Microsoft 365 Groups. Developers permit users to reconfigure a tab after installation and [create a tab removal page](~/tabs/how-to/create-tab-pages/removal-page.md) for the app. When building a Teams app that includes a tab, developers test how the [tab functions on both the Android and iOS Teams clients](~/tabs/design/tabs-mobile.md). The tab retrieves context through basic information, locale and theme details, and an `entityId` or `subEntityId` that identifies tab content.
> [!NOTE]
> **Posts** and **Files** can't be moved from their positions.
## Tab features
-The tab features are as follows:
+The tab features include:
-* If a tab is added to an app that also has a bot, the bot is also added to the team.
-* Awareness of Microsoft Entra ID of the current user.
-* Locale awareness for the user to indicate language that is `en-us`.
+* Adding a tab to an app that also has a bot automatically adds the bot to the team.
+* Awareness of Microsoft Entra ID for the current developer.
+* Locale awareness to indicate language, such as `en-us`.
* Single sign-on (SSO) capability, if supported.
-* Ability to use bots or app notifications to deep link to the tab or to a subentity within the service, for example an individual work item.
+* Support for bots or app notifications to deep link to the tab or to a subentity within the service, such as an individual work item.
* The ability to open a modal dialog from links within a tab.
-* Reuse of SharePoint web parts within the tab.
+* Reuse of SharePoint web parts within a tab.
## Tabs user scenarios
**Scenario:** Bring an existing web-based resource inside Teams.
-**Example:** You create a static tab in your Teams app that presents an informational corporate website to users.
+**Example:** Developers create a static tab in the Teams app that presents informational corporate website content to users.
-**Scenario:** Add support pages to a Teams bot or messaging extension.
-**Example:** You create static tabs that provide **about** and **help** webpage content to users.
+**Scenario:** Add support pages for a Teams bot or messaging extension.
+**Example:** Developers create static tabs that supply **about** and **help** webpage information to users.
-**Scenario:** Provide access to items that your users interact with regularly for cooperative dialogue and collaboration.
-**Example:** You create a channel or group tab with deep linking to individual items.
+**Scenario:** Provide access to items that developers and users interact with regularly for collaborative dialogue.
+**Example:** Developers build a channel or group tab with deep linking to individual items.
## Declare custom tab in app manifest
-A custom tab is declared in the app manifest of your app package. For each webpage you want included as a tab in your app, you define a URL and a scope. Additionally, add the [Teams JavaScript client library](/javascript/api/overview/msteams-client) to your page, and call `microsoftTeams.initialize()` after your page loads. This informs Teams that your app has loaded.
+A custom tab declares in the app manifest of the app package. For each webpage developers include as a tab in the app, a URL and a scope define the tab. Additionally, developers add the [Teams JavaScript client library](/javascript/api/overview/msteams-client) to the page and call `microsoftTeams.initialize()` after the page loads. This call informs Teams that the app has loaded.
-Whether you choose to expose your tab within the channel or group, or personal scope, you must present an HTML [content page](~/tabs/how-to/create-tab-pages/content-page.md) in your tab. For static tabs, the content URL is set directly in your Teams [app manifest](../resources/schema/manifest-schema.md#statictabs) by the `contentUrl` property in the `staticTabs` array. Your tab's content is the same for all users.
+When exposing a tab in either the channel or group scope or the personal scope, developers present an `