diff --git a/CHANGELOG.md b/CHANGELOG.md
index 94962d10c3..bc43e84db7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -152,6 +152,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 -  `bundle`: Webpack will now use `webpack-stats-plugin` instead of `webpack-visualizer-plugin`, by [@compulim](https://github.com/compulim) in PR [#2584](https://github.com/microsoft/BotFramework-WebChat/pull/2584)
    -  This will fix [#2583](https://github.com/microsoft/BotFramework-WebChat/issues/2583) by not bringing in transient dependency of React
    -  To view the bundle stats, browse to https://chrisbateman.github.io/webpack-visualizer/ and drop the file `/packages/bundle/dist/stats.json`
+-  Resolves [#2674](https://github.com/microsoft/BotFramework-WebChat/issues/2674). Update embed docs, by [@corinagum](https://github.com/corinagum), in PR [#2696](https://github.com/microsoft/BotFramework-WebChat/pull/2696)
 
 ### Samples
 
diff --git a/DIRECT_LINE_SPEECH.md b/DIRECT_LINE_SPEECH.md
index 3d16a26217..1e1a4f4d9c 100644
--- a/DIRECT_LINE_SPEECH.md
+++ b/DIRECT_LINE_SPEECH.md
@@ -10,7 +10,7 @@ We assume you have already set up a bot and have Web Chat running on a page.
 
 ## What is Direct Line Speech?
 
-Direct Line Speech is designed for Voice Assistant scenario. For example, smart display, automotive dashboard, navigation system with low-latency requirement on *single-page application* and *progressive web apps* (PWA). These apps usually are made with highly-customized UI and do not show conversation transcripts.
+Direct Line Speech is designed for Voice Assistant scenario. For example, smart display, automotive dashboard, navigation system with low-latency requirement on _single-page application_ and _progressive web apps_ (PWA). These apps usually are made with highly-customized UI and do not show conversation transcripts.
 
 You can look at our sample [13.a.customization-speech-ui](https://microsoft.github.io/BotFramework-WebChat/samples/13.a.customization-speech-ui) and [13.b.smart-display](https://microsoft.github.io/BotFramework-WebChat/samples/13.b.customization-smart-display) for target scenarios.
 
@@ -247,8 +247,8 @@ Please look at our sample `06.i.direct-line-speech` to embedding Web Chat on you
 
 After setting up Direct Line Speech on Azure Bot Services, there are two steps for using Direct Line Speech:
 
-- [Retrieve your Direct Line Speech credentials](#retrieve-your-direct-line-speech-credentials)
-- [Render Web Chat using Direct Line Speech adapters](#render-web-chat-using-direct-line-speech-adapters)
+-  [Retrieve your Direct Line Speech credentials](#retrieve-your-direct-line-speech-credentials)
+-  [Render Web Chat using Direct Line Speech adapters](#render-web-chat-using-direct-line-speech-adapters)
 
 ### Retrieve your Direct Line Speech credentials
 
@@ -260,17 +260,20 @@ In the following code snippets, we assume sending a HTTP POST request to https:/
 
 ```js
 const fetchCredentials = async () => {
-  const res = await fetch('https://webchat-mockbot-streaming.azurewebsites.net/speechservices/token', {
-    method: 'POST'
-  });
+   const res = await fetch(
+      'https://webchat-mockbot-streaming.azurewebsites.net/speechservices/token',
+      {
+         method: 'POST'
+      }
+   );
 
-  if (!res.ok) {
-    throw new Error('Failed to fetch authorization token and region.');
-  }
+   if (!res.ok) {
+      throw new Error('Failed to fetch authorization token and region.');
+   }
 
-  const { authorizationToken, region } = await res.json();
+   const { authorizationToken, region } = await res.json();
 
-  return { authorizationToken, region };
+   return { authorizationToken, region };
 };
 ```
 
@@ -281,13 +284,15 @@ const fetchCredentials = async () => {
 After you have the `fetchCredentials` function set up, you can pass it to `createDirectLineSpeechAdapters` function. This function will return a set of adapters that is used by Web Chat. It includes DirectLineJS adapter and Web Speech adapter.
 
 ```js
-const adapters = await window.WebChat.createDirectLineSpeechAdapters({ fetchCredentials });
+const adapters = await window.WebChat.createDirectLineSpeechAdapters({
+   fetchCredentials
+});
 
 window.WebChat.renderWebChat(
-  {
-    ...adapters
-  },
-  document.getElementById('webchat')
+   {
+      ...adapters
+   },
+   document.getElementById('webchat')
 );
 ```
 
@@ -301,13 +306,13 @@ window.WebChat.renderWebChat(
 
 You can specify user ID when you instantiate Web Chat.
 
-- If you specify user ID
-   - `conversationUpdate` activity will be send on connect and every reconnect. And with your user ID specified in the `membersAdded` field.
-   - All `message` activities will be sent with your user ID in `from.id` field.
-- If you do not specify user ID
-   - `conversationUpdate` activity will be send on connect and every reconnect. The `membersAdded` field will have an user ID of empty string.
-   - All `message` activities will be sent with a randomized user ID
-      - The user ID is kept the same across reconnections
+-  If you specify user ID
+   -  `conversationUpdate` activity will be send on connect and every reconnect. And with your user ID specified in the `membersAdded` field.
+   -  All `message` activities will be sent with your user ID in `from.id` field.
+-  If you do not specify user ID
+   -  `conversationUpdate` activity will be send on connect and every reconnect. The `membersAdded` field will have an user ID of empty string.
+   -  All `message` activities will be sent with a randomized user ID
+      -  The user ID is kept the same across reconnections
 
 ### Connection idle and reconnection
 
diff --git a/packages/embed/README.md b/packages/embed/README.md
index 23ec567e06..14448172b5 100644
--- a/packages/embed/README.md
+++ b/packages/embed/README.md
@@ -2,19 +2,19 @@
 
 This package contains the source code for the embed page at https://webchat.botframework.com/.
 
-> For transparency and completeness, we are maintaining the code here. This code is coupled to our servers. In order to host this page on your own website, you will need to decouple it or provide the same set of REST APIs.
+> For transparency and completeness, we are maintaining the code in the Web Chat repository. This code is coupled to our servers. In order to host this page on your own website, you will need to decouple it or provide the same set of REST APIs.
 
 ## Background
 
-Web Chat offers multiple levels of integration options. In this package, we focus on embedding `<iframe>` element in your web page.
+Web Chat offers multiple levels of integration options. In this package, we focus on embedding an `<iframe>` element in your web page.
 
-`<iframe>` is the simplest way to connect your website to Azure Bot Services. If you prefer more advanced features or customization options, please refer to [this migration guide](https://github.com/microsoft/botframework-webchat/blob/master/README.md#migrating-from-v3-to-v4-of-web-chat) for details.
+`<iframe>` is the simplest way to connect your website to Azure Bot Services. If you prefer more advanced features or customization options, please refer to the [migration guide](https://github.com/microsoft/botframework-webchat/blob/master/README.md#migrating-from-v3-to-v4-of-web-chat) for details.
 
 There are a few features unique to `<iframe>`:
 
 -  Reading configurations from Azure Bot Services
 -  Simplified version selection
-   -  Based on the versions you selected (latest, specific major, or specific minor), we will serve the Web Chat client with latest security fixes
+   -  Based on the versions you selected (latest, specific major, or specific minor), the most recent Web Chat client of that major and minor version will be served with the latest security fixes
    -  Please refer to the [I want to go back documentation](#i-want-to-go-back-to-previous-versions-of-web-chat) to specify the version you want to use
 -  This creates the same experience as the "Test in Web Chat" blade in Azure Portal
 
@@ -26,7 +26,7 @@ To use the embed page, you will need the site secret from your Azure Bot Service
 <iframe src="https://webchat.botframework.com/embed/your-bot-id?s=your-site-secret"></iframe>
 ```
 
-**For production use, we strongly prefer you to use token instead of secret.** Please refer to [this article](https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-direct-line-3-0-authentication) for how to generate token out of secret.
+**For production use, we strongly recommend that you use token retrieval instead of your secret.** Please refer to [this article](https://docs.microsoft.com/en-us/azure/bot-service/rest-api/bot-framework-rest-direct-line-3-0-authentication) for how to generate token from your secret.
 
 With a token (instead of a secret), your `<iframe>` will look like the following:
 
@@ -34,28 +34,28 @@ With a token (instead of a secret), your `<iframe>` will look like the following
 <iframe src="https://webchat.botframework.com/embed/your-bot-id?t=your-site-token"></iframe>
 ```
 
-Please look at [this table](#what-url-parameters-are-supported) for list of URL parameters supported.
+Please refer to the [supported parameters](#what-url-parameters-are-supported) for list of URL parameters supported.
 
 ## Development
 
 ### Building the page
 
-Follow steps below to build the embed page locally.
+Follow the steps below to build the embed page locally.
 
 1. `npm install`
 1. `npm run prepublishOnly`
 1. Publishes the build artifact at `/dist/index.html`
    1. Verifies the file size. It should be less than 30 KB
 
-### Updating servicing plan
+### Updating the servicing plan
 
 `servicingPlan.json` is the deployment plan. It provides details about where to locate assets, how to set up, and when to deprecate our older bits.
 
-When modifying the servicing plan to point to newer assets, make sure it is pointing to immutable copies on CDN. For example, you want to use assets with hashed filenames. Since we are using subresource integrity, this will make sure the servicing plan and assets can be invalidated on CDN cache asynchronously.
+When modifying the servicing plan to point to newer assets, make sure it is pointing to immutable copies on CDN. For example, you want to use assets with hashed filenames. Since Web Chat is using subresource integrity, this will make sure the servicing plan and assets can be invalidated on CDN cache asynchronously.
 
 #### Generating hash for subresource integrity
 
-For traceability of deployment, we are using [subresource integrity](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity).
+For traceability of deployment, Web Chat uses [subresource integrity](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity).
 
 To generate SHA384 for a specific asset from an URL, run the following command in [Ubuntu](https://www.microsoft.com/en-us/p/ubuntu/9nblggh4msv6).
 
@@ -63,38 +63,36 @@ To generate SHA384 for a specific asset from an URL, run the following command i
 curl https://cdn.botframework.com/botframework-webchat/4.3.0/webchat.js | openssl dgst -sha384 -binary | openssl base64 -A
 ```
 
-[This script](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity#Tools_for_generating_SRI_hashes) will fetch the asset from CDN, pipe it into OpenSSL for digest, and output as BASE64.
+[Generating SRI hashes script](https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity#Tools_for_generating_SRI_hashes) will fetch the asset from CDN, pipe it into OpenSSL for digest, and output as BASE64.
 
 ### Test locally
 
-There are two public surfaces we need to test:
+There are two public surfaces to test:
 
--  Embed page, i.e. https://webchat.botframework.com/embed/your-bot-id
+-  Embed page (i.e. https://webchat.botframework.com/embed/your-bot-id)
 -  Azure Portal "Test in Web Chat" blade
 
-<!-- #### Testing the embed page
+#### Testing the embed page locally
 
-In order to test your local build, you can use Fiddler to modify the traffic to serve the Gemini page locally.
+In order to test your local build, you can use Fiddler to modify the traffic to serve the Web Chat page locally.
 
 Append the following code in the FiddlerScript `OnBeforeRequest` function.
 
 ```js
-if (oSession.uriContains('https://webchat.botframework.com/embed/your-bot-id/gemini')) {
+if (oSession.uriContains('https://webchat.botframework.com/embed/your-bot-id/')) {
    oSession['x-replywithfile'] =
       'C:\\Users\\JohnDoe\\Source\\Repos\\BotFramework-WebChat\\packages\\embed\\dist\\index.html';
    oSession['ui-backcolor'] = 'Yellow';
 }
 ```
 
-This code snippet will intercept all requests destinated to https://webchat.botframework.com/embed/your-bot-id/gemini. Instead of serving the request from webchat.botframework.com, with the script, Fiddler will serve the content from local file at C:\Users\JohnDoe\...\index.html instead.
+This code snippet will intercept all requests designated for https://webchat.botframework.com/embed/your-bot-id/. Instead of serving the request from webchat.botframework.com, with the script, Fiddler will serve the content from your local file at C:\Users\JohnDoe\...\index.html instead.
 
 #### Testing on Azure Portal
 
-Until migration to v4 has completed worldwide, your bot may not immediately update to the new embed page on Azure Portal.
+Append the following code in the FiddlerScript `OnPeekAtResponseHeaders` function. It will allow your local bot to use the latest (or your chosen version) of Web Chat, regardless of the deployment phase.
 
-Append the following code in the FiddlerScript `OnPeekAtResponseHeaders` function. It will force your bot to use Gemini regardless of the deployment phase.
-
-When combined with the FiddlerScript above, "Test in Web Chat" in Azure Portal will point to the locally-developed version of the Gemini page.
+When combined with the FiddlerScript above, "Test in Web Chat" in Azure Portal will point to the locally-developed version of the Web Chat page.
 
 ```js
 if (oSession.uriContains('https://webchat.botframework.com/embed/your-bot-id?features=webchatpreview&t=')) {
@@ -103,16 +101,14 @@ if (oSession.uriContains('https://webchat.botframework.com/embed/your-bot-id?fea
    oSession.oResponse.headers.HTTPResponseStatus = '302 Moved';
    oSession.oResponse.headers.Add(
       'location',
-      oSession.PathAndQuery.replace('your-bot-id?', 'your-bot-id/gemini?b=your-bot-id&v=4.3&')
+      oSession.PathAndQuery.replace('your-bot-id?', 'your-bot-id/?b=your-bot-id&v=4.3&')
    );
 }
 ```
 
-This code snippet will intercept requests to the original embed page and forward it to the new Gemini embed page. -->
-
 ## FAQs
 
-Below are common questions about the new Gemini deployment of Web Chat.
+Below are common questions about the embed deployment of Web Chat.
 
 ### Why use `<iframe>` instead of other integration options?
 
@@ -128,40 +124,33 @@ Press <kbd>F12</kbd> and look at the console. It should say something similar to
 Web Chat: Selecting version "default" -> "4" -> "4.3" -> "4.3.0".
 ```
 
-In the above code, the version specifier is not specified. Web Chat is using the "default" version, which forwards to major version 4, then minor version 4.3, then patch version 4.3.0. You can select version by appending the URL query parameter `v` with the version number. For example, if you prefer 4.3, you should append `&v=4.3` to the URL.
-
-<!-- ### Why I am not seeing Web Chat v4 on my page?
-
-Look at the console log on your web page by pressing <kbd>F12</kbd> to see view the version of Web Chat.
+Without manual configuration, Web Chat will use the "default" version, which forwards to major version (e.g. 4), then minor version (e.g. 4.3), then patch version (e.g. 4.3.0). You can select a version by appending the URL query parameter `v` with the version number. For example, if you prefer 4.3, you should append `&v=4.3` to the URL.
 
-If you don't see the above line, this probably means that the new Gemini page has not completely rolled out. If your bot is using Gemini, the URL will be https://webchat.botframework.com/embed/your-bot-id/gemini. If your bot is not in, it will not have `/gemini` appended. -->
+You can use `<iframe>` to host any published version 4.x of v4 Web Chat
 
 ### I want to go back to previous versions of Web Chat
 
-There are a handful of versions we support:
+You can specify any `<iframe>` 4.x version of Web Chat on your app.
 
 -  Majors
    -  `4` will serve the latest minor version of `4.*`. At the time this document was created, that version was `4.3.0`
-   -  `3` will serve the latest minor version of `0.*`.At the time this document was created, it is `0.15.1-v3.748a85f`
-   -  `scorpio` will serve the version before Gemini page was introduced. At the time this document was created, `scorpio` is version `0.11.4-ibiza.f373b1d`
-      -  This is the as having the "Enable preview" checkbox checked
-   -  `aries` will serve the version before Gemini page was introduced
-      -  This is the same as having the "Enable preview" checkbox unchecked
-      -  This version will show a bot icon and welcome message at the top of the page
 -  Minors
    -  `4.2` will serve the latest patch version of `4.2.*`. At the time this document was created, it is `4.2.0`
+-  Other
 
-However, we do not support specifying patch versions, e.g. `4.2.1`. This is because patch versions are for important security fixes. We will roll it out to users who are on the same minor version and we guarantee that security fixes will not introduce breaking changes.
+   -  versions `3` and older are no longer available via embed. To use one of these versions on your app, please use the CDN of Web Chat in your HTML. See samples [01.a.getting-started-full-bundle](https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/01.a.getting-started-full-bundle) and [01.c.getting-started-migration](https://github.com/microsoft/BotFramework-WebChat/tree/master/samples/01.c.getting-started-migration) to learn more.
+
+   -  Pre-v3, legacy versions of Web Chat are maintained at [`botframework-webchat@legacy`](https://www.npmjs.com/package/botframework-webchat/v/legacy), latest is 0.15.1
+
+Specifying patch versions (e.g. `4.2.1`) is not supported. This is because patch versions are for important security fixes. Patches will be rolled out to users who are on the same minor version, and we guarantee that security fixes will not introduce breaking changes.
 
 ### I really don't like the versioning system
 
-We understand that sometimes, you will want to lock down to every single bit of code. Feel free to clone our code and build your own copy. This will ensure that your bits are locked down and controlled by your system. But it also means we will not be able to serve you any new features or security fixes.
+Feel free to clone Web Chat's code and build your own copy if you prefer to be in complete control of your code. This will ensure that your bits are locked down by your system. But it also means your version of Web Chat will not receive any new features or security fixes.
 
 ### How does staged deployment work?
 
-From time to time, when we release a new version of Web Chat, we will update the servicing plan in this repository and upload it to our server. This gives our users transparency on when we push out a new version and how it is done.
-
-We gradually migrate customers' sites to our new version using a mechanism we call a dial. When we finish turning the dial from 0% to 100%, all customers have been switched to the latest version. We can also cherry-pick specific sites into specific version, or out.
+When a new version of Web Chat is released, the servicing plan in this repository will be updated and uploaded to the Bot Framework server. This gives users transparency on when a new version is pushed out and how it is done.
 
 ### What URL parameters are supported?
 
@@ -176,19 +165,14 @@ We gradually migrate customers' sites to our new version using a mechanism we ca
 | `?username=WW`     | Username to show, only for v3 or lower. This parameter is accepted in v4, but will not be shown.          |
 | `?v=4`             | Specify version                                                                                           |
 
-### What is Gemini, Scorpio and Aries?
-
-Historically, we use Zodiac signs as code name to version the embed page.
+### Embed history
 
--  Gemini: the latest version of embed page
-   -  Supports multiple versions of Web Chat, backwards- and forwards-compatible
-      -  Latest version is maintained at [`botframework-webchat@latest`](https://www.npmjs.com/package/botframework-webchat/)
-      -  v3 is maintained at [`botframework-webchat@legacy`](https://www.npmjs.com/package/botframework-webchat/v/legacy), latest is 0.15.1
-   -  Supports falling back to previous versions of embed page include Scorpio and Aries
--  Scorpio: Web Chat v3 of version 0.11.4
-   -  Adaptive Cards 0.6.1
+-  Web Chat v4 embed supports multiple versions of Web Chat (backwards- and forwards-compatible)
+   -  The latest version is maintained at [`botframework-webchat@latest`](https://www.npmjs.com/package/botframework-webchat/)
+   -  v3 is maintained at [`botframework-webchat@legacy`](https://www.npmjs.com/package/botframework-webchat/v/legacy), and latest is 0.15
+-  Legacy Web Chat 0.11.4:
+   -  Uses Adaptive Cards 0.6.1
    -  OAuth card is not supported
-   -  This is maintained at [`botframework-webchat@ibiza`](https://www.npmjs.com/package/botframework-webchat/v/ibiza)
+   -  Is maintained at [`botframework-webchat@ibiza`](https://www.npmjs.com/package/botframework-webchat/v/ibiza)
    -  Note: 0.11.4 is not the latest version of Web Chat v3, the latest is 0.15.1
--  Aries: Web Chat v1
-   -  Written in ASP.NET and Angular
+-  Web Chat v1 was written in ASP.NET and Angular
diff --git a/samples/06.i.direct-line-speech/README.md b/samples/06.i.direct-line-speech/README.md
index 24b20732d0..188466d78e 100644
--- a/samples/06.i.direct-line-speech/README.md
+++ b/samples/06.i.direct-line-speech/README.md
@@ -32,7 +32,7 @@ Direct Line Speech is a channel for communicating with a bot via a low-latency s
 
 This sample starts with the [full-bundle CDN sample](./../01.a.getting-started-full-bundle/README.md) as the base template.
 
-In this sample, we will switch the Web Chat protocol. Direct Line Speech is a channel for communicating with a bot via a low-latency speech-focused protocol. The channel is designed for real-time speech. Thus, *not all features in Web Chat are supported in this channel.*
+In this sample, we will switch the Web Chat protocol. Direct Line Speech is a channel for communicating with a bot via a low-latency speech-focused protocol. The channel is designed for real-time speech. Thus, _not all features in Web Chat are supported in this channel._
 
 (TBD, list of limitations)
 
@@ -48,7 +48,7 @@ You will also need to update your bot to use 4.6 SDK. You can follow [this artic
 
 ### Using subscription key
 
-We will start by using subscription key to connect to the Direct Line Speech channel. *Please note that a subscription key is not recommended to use in production environment.* In this sample, we will use it to verify if our configuration is correct. In the latter section, we will upgrade the sample to use an authorization token.
+We will start by using subscription key to connect to the Direct Line Speech channel. _Please note that a subscription key is not recommended to use in production environment._ In this sample, we will use it to verify if our configuration is correct. In the latter section, we will upgrade the sample to use an authorization token.
 
 We are replacing the existing code by creating an adapter set using the new `createDirectLineSpeechAdapters` function. We will pass the adapter set to Web Chat using the [spread operator](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax).
 
@@ -85,17 +85,17 @@ First, create an async function `fetchCredentials`. When called, it will fetch t
 
 ```js
 const fetchCredentials = async () => {
-  const res = await fetch('https://webchat-mockbot-streaming.azurewebsites.net/speechservices/token', {
-    method: 'POST'
-  });
+   const res = await fetch('https://webchat-mockbot-streaming.azurewebsites.net/speechservices/token', {
+      method: 'POST'
+   });
 
-  if (!res.ok) {
-    throw new Error('Failed to fetch authorization token and region.');
-  }
+   if (!res.ok) {
+      throw new Error('Failed to fetch authorization token and region.');
+   }
 
-  const { region, token: authorizationToken } = await res.json();
+   const { region, token: authorizationToken } = await res.json();
 
-  return { authorizationToken, region };
+   return { authorizationToken, region };
 };
 ```