diff --git a/dotnet/packages/Microsoft.TeamsAI/README.md b/dotnet/packages/Microsoft.TeamsAI/README.md
index bba31d306..4812dc7d7 100644
--- a/dotnet/packages/Microsoft.TeamsAI/README.md
+++ b/dotnet/packages/Microsoft.TeamsAI/README.md
@@ -9,6 +9,11 @@ Requirements:
 *   [.NET 6.0 SDK](https://dotnet.microsoft.com/download/dotnet/6.0)
 *   (Optional) [Azure OpenAI](https://azure.microsoft.com/en-us/products/ai-services/openai-service) resource or an account with [OpenAI](https://platform.openai.com/)
 
-## Getting Started: Migration vs New Project
 
-If you're migrating an existing project, switching to add on the Teams AI Library layer is quick and simple. See the [migration guide](https://github.com/microsoft/teams-ai/blob/main/getting-started/MIGRATION/02.DOTNET.md).
\ No newline at end of file
+## Getting Started
+
+To get started, take a look at the [getting started docs](https://github.com/microsoft/teams-ai/blob/main/getting-started/00.OVERVIEW.md).
+
+## Migration
+
+If you're migrating an existing project, switching to add on the Teams AI Library layer is quick and simple. See the [migration guide](https://github.com/microsoft/teams-ai/blob/main/getting-started/MIGRATION/02.DOTNET.md).
diff --git a/dotnet/samples/README.md b/dotnet/samples/README.md
index c8c2e389f..269290e34 100644
--- a/dotnet/samples/README.md
+++ b/dotnet/samples/README.md
@@ -28,7 +28,7 @@ There are a few ways to get the application up and running. The latest way is us
 #### Steps
 
 1. Open the solution in Visual Studio. (For example `EchoBot.sln`).
-   - Ensure that you set the appropriate config values (ex Azure OpenAI API key). You can find specific instructions in the sample readme under the `Set up instructions` section. If you can't find this section, then it means that the bot does not need them.
+   - Ensure that you set the appropriate config values (ex Azure OpenAI API key). You can find specific instructions in the sample readme under the `Set up instructions` section. If you can't find this section, then it means there is no required config values to set.
 2. In the debug dropdown menu, select `Dev Tunnels > Create A Tunnel` (Tunnel type: `Persistent` & Access: `Public`) or select an existing public dev tunnel.
 
    ![image](https://github.com/microsoft/teams-ai/assets/115390646/d7246d38-8276-4b2a-bc22-b72f36aa41b9)
diff --git a/js/packages/teams-ai/README.md b/js/packages/teams-ai/README.md
index e04b3c327..90bba12a9 100644
--- a/js/packages/teams-ai/README.md
+++ b/js/packages/teams-ai/README.md
@@ -8,4 +8,13 @@ Requirements:
 -   node v16.x
 -   node v18.x
 
-To get started with the SDK [see](../../../getting-started/00.OVERVIEW.md). 
\ No newline at end of file
+To get started with the SDK [see](../../../getting-started/00.OVERVIEW.md). 
+
+
+## Getting Started
+
+To get started, take a look at the [getting started docs](https://github.com/microsoft/teams-ai/blob/main/getting-started/00.OVERVIEW.md).
+
+## Migration
+
+If you're migrating an existing project, switching to add on the Teams AI Library layer is quick and simple. See the [migration guide](https://github.com/microsoft/teams-ai/blob/main/getting-started/MIGRATION/02.JS.md).