diff --git a/site/sigmaguides/src/embedding_01_getting_started_v3/embedding_01_getting_started_v3.md b/site/sigmaguides/src/embedding_01_getting_started_v3/embedding_01_getting_started_v3.md
index d736ef56..48a6e359 100644
--- a/site/sigmaguides/src/embedding_01_getting_started_v3/embedding_01_getting_started_v3.md
+++ b/site/sigmaguides/src/embedding_01_getting_started_v3/embedding_01_getting_started_v3.md
@@ -25,7 +25,7 @@ Sigma also provides an embed sandbox that is built into the product. For more in
 
 The local web application (e.g., native application) refers to the customer-developed application that Sigma is embedded into.
 
-We will use code from a public Git repository, VS Code, and Node.js in this QuickStart series. 
+We will use code from a public Git repository, VS Code, Node.js, Javascript and HTML in this QuickStart series. 
 
 <aside class="negative">
 <strong>NOTE:</strong><br> There are many programming languages and libraries you can use to develop a server-side application. Node.js is the one we will be using today. The sample code provided is simplified and commented to assist in your learning.
diff --git a/site/sigmaguides/src/embedding_02_federated_access_v3/embedding_02_federated_access_v3.md b/site/sigmaguides/src/embedding_02_federated_access_v3/embedding_02_federated_access_v3.md
index 79e5c21c..7b7a5af0 100644
--- a/site/sigmaguides/src/embedding_02_federated_access_v3/embedding_02_federated_access_v3.md
+++ b/site/sigmaguides/src/embedding_02_federated_access_v3/embedding_02_federated_access_v3.md
@@ -32,7 +32,7 @@ For more information, see [using SSO with Sigma](https://help.sigmacomputing.com
 
 Additional information is also available: [managing user and teams with SCIM](https://help.sigmacomputing.com/docs/manage-users-and-teams-with-scim)
 
-In this QuickStart, we will use the local node.js application framework we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
+In this QuickStart, we will use the local native application framework we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma continuously adds and enhances functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.
@@ -43,7 +43,7 @@ For more information on Sigma's product release strategy, see [Sigma product rel
 If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
 
 ### Target Audience
-The typical audience for this QuickStart includes users of Excel, common Business Intelligence or Reporting tools, and semi-technical users who want to try out or learn Sigma.
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
 
 ### Prerequisites
 
diff --git a/site/sigmaguides/src/embedding_03_parameters_ua_v3/embedding_03_parameters_ua_v3.md b/site/sigmaguides/src/embedding_03_parameters_ua_v3/embedding_03_parameters_ua_v3.md
index f8768d50..2c2c908e 100644
--- a/site/sigmaguides/src/embedding_03_parameters_ua_v3/embedding_03_parameters_ua_v3.md
+++ b/site/sigmaguides/src/embedding_03_parameters_ua_v3/embedding_03_parameters_ua_v3.md
@@ -23,7 +23,7 @@ For a full reference, see Sigma’s [Embed URL Parameters](https://help.sigmacom
 
 This QuickStart provides examples and screenshots of required and optional parameters to help developers understand their use.
 
-Before proceeding, ensure you've completed the [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_01_getting_started_v3/index.html?index=..%2F..embedding#1) QuickStart. It covers JWT in detail, so we won’t repeat that here.
+In this QuickStart, we will use the local native application we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma continuously adds and enhances functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.
@@ -34,15 +34,15 @@ For more information on Sigma's product release strategy, see [Sigma product rel
 If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
 
 ### Target Audience
-Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are required to complete this QuickStart. It assumes some basic computer skills, such as installing software, using Terminal, navigating folders, and performing copy/paste operations.
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
 
 ### Prerequisites
 
 <ul>
   <li>A computer with a current browser. It does not matter which browser you want to use.</li>
   <li>Access to your Sigma environment.</li>
-  <li>Some familiarity with Sigma is assumed. Not all steps will be shown, as the basics are assumed to be understood.</li>
- </ul>
+  <li>Embedding 01: Getting Started is required to complete this QuickStart.</li>
+</ul>
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Sigma recommends using non-production resources when completing QuickStarts.
diff --git a/site/sigmaguides/src/embedding_04_isolation_solutions_v3/embedding_04_isolation_solutions_v3.md b/site/sigmaguides/src/embedding_04_isolation_solutions_v3/embedding_04_isolation_solutions_v3.md
index ce821d7f..46986d3f 100644
--- a/site/sigmaguides/src/embedding_04_isolation_solutions_v3/embedding_04_isolation_solutions_v3.md
+++ b/site/sigmaguides/src/embedding_04_isolation_solutions_v3/embedding_04_isolation_solutions_v3.md
@@ -39,15 +39,15 @@ For more information on Sigma's product release strategy, see [Sigma product rel
 If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
 
 ### Target Audience
-Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart.
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
 
 ### Prerequisites
 
 <ul>
   <li>A computer with a current browser. It does not matter which browser you want to use.</li>
   <li>Access to your Sigma environment.</li>
-  <li>Some familiarity with Sigma is assumed. Not all steps will be shown, as the basics are assumed to be understood.</li>
- </ul>
+  <li>Embedding 01: Getting Started is required to complete this QuickStart.</li>
+</ul>
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Sigma recommends using non-production resources when completing QuickStarts.
diff --git a/site/sigmaguides/src/embedding_09_events_v3/embedding_09_events_v3.md b/site/sigmaguides/src/embedding_09_events_v3/embedding_09_events_v3.md
index 24b50852..b85f6464 100644
--- a/site/sigmaguides/src/embedding_09_events_v3/embedding_09_events_v3.md
+++ b/site/sigmaguides/src/embedding_09_events_v3/embedding_09_events_v3.md
@@ -29,35 +29,40 @@ Inbound events can be passed using either JavaScript or URL.
 **Outbound Events:**<br>
 These are variables sent from Sigma to the native application, which must have a listener coded to receive and respond to the message.
 
-This QuickStart assumes you have already taken the QuickStart [Embedding 1: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_01_prerequisites/index.html?index=..%2F..index#0) so that you have a sample environment to complete the tasks in this QuickStart.
-
-**Some steps may not be shown in detail as we assume you have taken these other two QuickStarts or are familiar with Sigma workflows.**
-
-A list of all the [available events is available here.](https://help.sigmacomputing.com/docs/inbound-and-outbound-events-in-embeds)
+In this QuickStart, we will use the local native application we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
 
 <aside class="positive">
-<strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma is continuously adding and enhancing functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.
+<strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma continuously adds and enhances functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.
 </aside>
 
-For more information on Sigma's product release strategy, see [Sigma product releases.](https://help.sigmacomputing.com/docs/sigma-product-releases)
+For more information on Sigma's product release strategy, see [Sigma product releases](https://help.sigmacomputing.com/docs/sigma-product-releases)
+
+If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
 
 ### Target Audience
-Semi-technical users who will be aiding in the planning or implementation of Sigma. Limited SQL and technical data skills are needed to do this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and edit/copy/paste operations.
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
 
 ### Prerequisites
 
 <ul>
-  <li>Any modern browser is acceptable.</li>
-  <li>Access to your Sigma environment. A Sigma trial environment is acceptable and preferred.</li>
-  <li>Completion of the Embedding 01: Getting Started QuickStart.</li>
+  <li>A computer with a current browser. It does not matter which browser you want to use.</li>
+  <li>Access to your Sigma environment.</li>
+  <li>Embedding 01: Getting Started is required to complete this QuickStart.</li>
 </ul>
 
-<button>[Free Trial](https://www.sigmacomputing.com/free-trial/)</button>
+<aside class="positive">
+<strong>IMPORTANT:</strong><br> Sigma recommends using non-production resources when completing QuickStarts.
+</aside>
+
+<button>[Sigma Free Trial](https://www.sigmacomputing.com/free-trial/)</button>
 
-![Footer](assets/sigma_footer.png)
+<aside class="negative">
+<strong>IMPORTANT:</strong><br> Some features may carry a "Beta" tag. Beta features are subject to quick, iterative changes. As a result, the latest product version may differ from the contents of this document.
+</aside>
+ 
+![Footer](assets/sigma_footer.png)ooter.png)
 <!-- END -->
 
-
 ## Sigma Workbook
 Duration: 15
 
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/1.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/1.png
new file mode 100644
index 00000000..726cde47
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/1.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/10.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/10.png
new file mode 100644
index 00000000..a88d5d8b
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/10.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/2.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/2.png
new file mode 100644
index 00000000..7087109c
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/2.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/3.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/3.png
new file mode 100644
index 00000000..aae562bf
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/3.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/4.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/4.png
new file mode 100644
index 00000000..85d1e24d
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/4.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/5.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/5.png
new file mode 100644
index 00000000..ce0d7728
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/5.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/6.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/6.png
new file mode 100644
index 00000000..b7b3cd01
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/6.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/7.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/7.png
new file mode 100644
index 00000000..b053ded8
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/7.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/8.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/8.png
new file mode 100644
index 00000000..3cf0e617
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/8.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/9.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/9.png
new file mode 100644
index 00000000..3aff50c3
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/9.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/caret.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/caret.png
new file mode 100644
index 00000000..13a132ab
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/caret.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/closeview.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/closeview.png
new file mode 100644
index 00000000..d0fbb0e4
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/closeview.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/crane.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/crane.png
new file mode 100644
index 00000000..225ecf3f
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/crane.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/facebook.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/facebook.png
new file mode 100644
index 00000000..fa3f0e02
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/facebook.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/greencheckbox.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/greencheckbox.png
new file mode 100644
index 00000000..69cb876e
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/greencheckbox.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/heart_icon.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/heart_icon.png
new file mode 100644
index 00000000..bff9ea90
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/heart_icon.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/horizonalline.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/horizonalline.png
new file mode 100644
index 00000000..7c49d872
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/horizonalline.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/linkedin.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/linkedin.png
new file mode 100644
index 00000000..d1a0636d
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/linkedin.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_1.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_1.png
new file mode 100644
index 00000000..11c2c37b
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_1.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_10.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_10.png
new file mode 100644
index 00000000..b8523771
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_10.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_2.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_2.png
new file mode 100644
index 00000000..a9e06e4e
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_2.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_3.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_3.png
new file mode 100644
index 00000000..1b2c61e1
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_3.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_4.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_4.png
new file mode 100644
index 00000000..24b53778
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_4.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_5.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_5.png
new file mode 100644
index 00000000..76ef8df9
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_5.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_6.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_6.png
new file mode 100644
index 00000000..a3cfaed2
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_6.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_7.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_7.png
new file mode 100644
index 00000000..1b149f02
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_7.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_8.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_8.png
new file mode 100644
index 00000000..fb041b2c
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_8.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_9.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_9.png
new file mode 100644
index 00000000..8a6a7a4c
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/re_9.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/responsive.gif b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/responsive.gif
new file mode 100644
index 00000000..5db63a7d
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/responsive.gif differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/scrollbars1.gif b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/scrollbars1.gif
new file mode 100644
index 00000000..9fe650bf
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/scrollbars1.gif differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/scrollbars2.gif b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/scrollbars2.gif
new file mode 100644
index 00000000..c0ac6033
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/scrollbars2.gif differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/sigma_footer.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/sigma_footer.png
new file mode 100644
index 00000000..df51d771
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/sigma_footer.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/twitter.png b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/twitter.png
new file mode 100644
index 00000000..5a827d72
Binary files /dev/null and b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/assets/twitter.png differ
diff --git a/site/sigmaguides/src/embedding_11_responsive_embeds_v3/embedding_11_responsive_embeds_v3.md b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/embedding_11_responsive_embeds_v3.md
new file mode 100644
index 00000000..2b5928e9
--- /dev/null
+++ b/site/sigmaguides/src/embedding_11_responsive_embeds_v3/embedding_11_responsive_embeds_v3.md
@@ -0,0 +1,342 @@
+author: pballai
+id: embedding_11_responsive_embeds_v3
+summary: embedding_11_responsive_embeds_v3
+categories: Embedding
+environments: web
+status: published
+feedback link: https://github.com/sigmacomputing/sigmaquickstarts/issues
+tags: embedding
+lastUpdated: 2025-05-20
+
+# Embedding 11 Responsive Embeds
+
+## Overview 
+Duration: 5 
+
+One of the many challenges developers face when building applications is usability, and a common problem is making it obvious that a user needs to scroll to see more data.
+
+This problem can be compounded when embedding content from any external application; even Sigma embeds. 
+
+Scroll bars on both parent and iframe content can significantly impact the user experience, often in a negative way. Here's why:
+
+<ul>
+      <li><strong>Confusion and difficulty navigating:</strong> When both the parent page and the iframe have scroll bars, it can be confusing for the user to navigate. They may not immediately recognize which scroll bar is active, leading to a disjointed and potentially frustrating experience.</li>
+      <li><strong>Nested scrolling:</strong> If the iframe content is longer than the parent page's height, users might have to deal with nested scrolling. This means they have to scroll down within the iframe before being able to continue scrolling on the parent page. This is generally considered poor user experience design and can be very frustrating.</li>
+      <li><strong>Aesthetically unpleasing:</strong> Multiple scroll bars can make the page look cluttered and messy, which can detract from the overall aesthetic of the website.</li>
+      <li><strong>Limited view of content:</strong> If an iframe has a scroll bar, it means that all the content isn't immediately visible to the user. This might cause users to miss important information if they don't realize they need to scroll within the iframe.</li>
+      <li><strong>Mobile unfriendly:</strong> On mobile devices, where screen real estate is limited, scroll bars within iframes can be particularly problematic. Users may accidentally scroll within the iframe when they intended to scroll on the parent page, or vice versa.</li>
+</ul>
+
+To avoid these issues, it's generally best to avoid having scroll bars on both the parent and the iframed content. This can usually be solved by making by making both the iframe and parent page responsive, so that the iframe adjusts its size based on the content it contains and the size of the viewport.
+
+ <ul>
+      <li><strong>Better user experience:</strong> A responsive iframe ensures that the content within the iframe is displayed correctly regardless of the size of the user's device or browser window. This is particularly important for users on mobile devices or tablets, as it allows the iframe content to resize and fit the smaller screen sizes.</li>
+      <li><strong>Consistency across devices:</strong> Since different users may be accessing the content on different devices (desktops, laptops, tablets, phones), it's important that the content looks good on all of these devices. A responsive iframe will resize based on the size of the user's device or browser window, ensuring that the content is always displayed in a user-friendly manner.</li>
+      <li><strong>Keeping up with modern web standards:</strong> As of the current web standards, responsiveness is a key factor in web design and development. It's almost expected that any web page or web application be responsive to provide the best user experience.</li>
+</ul>
+
+In essence, making an iframe dynamic or responsive is about ensuring that the content within the iframe is accessible, user-friendly, and looks good on all devices and window sizes. It's about creating a better, more consistent user experience.
+
+Since Sigma uses iframes for embedding, this issue is fairly easy to avoid.
+
+In this QuickStart, we will use the local native application we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
+
+<aside class="positive">
+<strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma continuously adds and enhances functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.
+</aside>
+
+For more information on Sigma's product release strategy, see [Sigma product releases](https://help.sigmacomputing.com/docs/sigma-product-releases)
+
+If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
+
+### Target Audience
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
+
+### Prerequisites
+
+<ul>
+  <li>A computer with a current browser. It does not matter which browser you want to use.</li>
+  <li>Access to your Sigma environment.</li>
+  <li>Embedding 01: Getting Started is required to complete this QuickStart.</li>
+</ul>
+
+<aside class="positive">
+<strong>IMPORTANT:</strong><br> Sigma recommends using non-production resources when completing QuickStarts.
+</aside>
+
+<button>[Sigma Free Trial](https://www.sigmacomputing.com/free-trial/)</button>
+
+<aside class="negative">
+<strong>IMPORTANT:</strong><br> Some features may carry a "Beta" tag. Beta features are subject to quick, iterative changes. As a result, the latest product version may differ from the contents of this document.
+</aside>
+ 
+![Footer](assets/sigma_footer.png)
+
+## Content to Embed
+Duration: 5
+
+Before we can dig into this topic, we need to configure an embed for our native application to use. 
+
+We’ll use one of the prebuilt templates included in all Sigma instances.
+
+After logging into Sigma, navigate to `Templates` and click the `Plugs Electronics Profit Planning Tool` example to open that template:
+
+<img src="assets/re_2.png" width="800"/>
+
+Click `Save As` and name the workbook `Embedding 11 Responsive Embeds`.
+
+<aside class="positive">
+<strong>IMPORTANT:</strong><br> Saving a workbook also publishes it automatically. A workbook must be published before it is embedded.
+</aside>
+
+<img src="assets/re_1.png" width="800"/>
+
+Make sure the workbook is in `published` mode.
+
+Share the workbook with the `Sales_People` team we created in the Getting Started QuickStart:
+
+<img src="assets/re_4.png" width="800"/>
+
+Click on the `Profit Planning Tool` page tab and copy the URL directly from the browser.
+
+Because we selected a page tab, we’ll need to adjust the URL slightly as documented in [What URL to use](https://help.sigmacomputing.com/docs/create-an-embed-api-with-json-web-tokens#what-url-to-use1)
+
+The correct URL syntax for a page is:
+
+https://app.sigmacomputing.com/{organization-slug}/workbook/{workbookname}-{workbookUrlId}/page/{pageId}
+
+<aside class="note"><strong>TIP:</strong><br>If you're unsure which part of the URL to replace, paste it into a text editor first and compare it to the expected format above. The `pageId` comes directly from the `?:nodeId=` query parameter.</aside>
+
+The key item to replace is:
+- ?:nodeId with /page/
+- The pageId is the same value as shown for nodeId
+
+Use this adjusted URL as the value for `RESPONSIVE_EMBEDS_BASE_URL` in your .env file, then save your changes.
+
+We also set the other parameters to the same values used in Getting Started and confirmed we still have values for `CLIENT_ID` and `SECRET`:
+
+<img src="assets/re_3.png" width="800"/>
+
+Open a new Terminal in VSCode, navigate to the `embedding_qs_series_2` directory, and start the Express web server by running:
+
+```code
+npm start
+```
+
+Open `http://localhost:3000/responsive_embeds/2bars.html` in a browser:
+
+The page will load the embedded content along with the `.env` parameters that are being used.
+
+Notice that both the browser and the iframe have scroll bars:
+
+<img src="assets/re_9.png" width="800"/>
+
+![Footer](assets/sigma_footer.png)
+<!-- END -->
+
+## A Quick (partial) Solution
+Duration: 20
+
+Since we are embedding content that is created in Sigma, it is not always possible to ensure that the Sigma content will "fit" inside a static iframes dimensions, since the content may vary depending on use-case.
+
+Without control over the iframe's content, it's challenging to have a fully dynamic solution that adjusts to the exact height of the content every time.
+
+Given the initial constraint, one approach might be to:
+
+1: Set a default height for the iframe that should ideally fit most of the content you expect to embed.
+
+2: Allow the iframe to scroll if its content exceeds this default height.
+
+**This ensures that:**
+
+1: The parent application remains without a scrollbar, providing a cleaner overall look.
+
+2: The iframe will only show a scrollbar when absolutely necessary (i.e., when its content exceeds its set height).
+
+This approach provides somewhat of a balance between user experience and practicality, given the constraints, but does not fully address the issue of scroll bars.
+
+In this scenario, even when the browser is full screen, the embedded content we have elected to provide from Sigma will be too long, and thus the iframe requires a scroll bar. 
+
+The parent page, however, should still avoid having a scroll bar.
+
+For this example, we will simply allow the iframe to scroll, but ensure the parent page does not. 
+
+Open this page in the browser:
+```code
+http://localhost:3000/responsive_embeds/1bar.html
+```
+
+Now we only have one scroll bar (in the embed) and the parent application does not present a scroll bar regardless of how we resize the browser:
+ 
+<img src="assets/re_10.png" width="800"/>
+
+The is because we replaced two css styles and adjusted the iframe too.
+
+The CSS adjustments made are:
+
+```code
+body {
+  display: flex;                     /* Uses Flexbox for vertical layout */
+  flex-direction: column;           /* Stacks children vertically (top to bottom) */
+  height: 100vh;                    /* Sets the body height to 100% of the viewport */
+  margin: 0;                        /* Removes default body margin (prevents scroll gap) */
+  font-family: sans-serif;         /* Applies a clean, readable font */
+}
+
+iframe {
+  width: 100%;                      /* Makes the iframe fill the full horizontal space */
+  height: 100%;                     /* Makes the iframe fill the full height of its container */
+  border: none;                    /* Removes default iframe border */
+  border-radius: 6px;              /* Applies rounded corners to the iframe */
+}
+```
+
+The iframe adjustment made is:
+
+```code
+<iframe id="sigma-embed" src=""></iframe>
+```
+
+![Footer](assets/sigma_footer.png)
+<!-- END OF SECTION-->
+
+## Alternative Method
+Duration: 20
+
+The `calc()` function in CSS can be used to dynamically compute values for various properties. This method is ideal when your page has a fixed-height topbar and you want the iframe to fill the rest of the viewport without causing scrollbars.
+
+While `calc()` can be powerful in many scenarios, it's important to understand its limitations and its applicability to your specific case.
+
+In our example, the `calc()` function can be used to compute dimensions based on various units, combinations of units, or viewport sizes.
+
+For example, if we want the iframe to take up the full viewport height minus some space for a header, we could use `calc()`.
+
+Here's how we might style the iframe using `calc()`:
+
+```code
+iframe {
+  width: 100%;
+  height: calc(100vh - 4rem); /* Adjusts for fixed header height */
+  border: none;
+  border-radius: 6px;
+}
+```
+
+When we use `height: calc(100vh - 4rem)` on the iframe, we’re telling it to take up the entire remaining viewport height beneath the header. That eliminates the need for the page itself to scroll, as long as:
+
+- The body has no extra vertical content
+- The iframe content itself is sized/responsive correctly inside the Sigma workbook
+
+To save time, we’ve pre-built a page that demonstrates this method.
+
+Browse to this URL:
+```code
+http://localhost:3000/responsive_embeds/1bar.html
+```
+
+<img src="assets/re_8.png">
+
+### A Few Things to Note:
+
+ <ul>
+      <li><strong>Content Size Unknown:</strong> The challenge with our iframe is that, since we may not control its content, we don't know its exact height. calc() helps with relative dimensions based on the viewport or other elements, but it can't determine the height of content inside an iframe from an external source.</li>
+      <li><strong>Doesn't Eliminate Scroll:</strong> Using calc() in this manner doesn't eliminate the need for a scrollbar if the content inside the iframe exceeds its height. It just helps in setting the iframe's height relative to other known dimensions.</li>
+      <li><strong>Complementary to Other CSS:</strong> calc() isn’t a replacement for other CSS tools—it’s complementary. We can use it in conjunction with other properties to achieve the desired layout.</li>
+</ul>
+ 
+In summary, while calc() is a valuable tool in CSS for dynamic calculations, it doesn't immediately solve the scrollbar issues. 
+
+It helps set dimensions based on known values based on other known dimensions or viewport sizes, but it won't "dynamically" adjust the iframe's height based on its content. 
+
+![Footer](assets/sigma_footer.png)
+<!-- END OF SECTION-->
+
+## Responsive iframes using Sigma Events
+Duration: 5
+
+Sigma emits a JavaScript event that allows us to dynamically adjust the iframe height, based on the content's actual height.
+
+This is especially useful when the content inside the iframe can change dynamically, leading to different height requirements.
+
+**This approach can fully resolve iframe scrollbar issues when used correctly.**
+
+The event we’ll use is `workbook:pageheight:onchange`, which is emitted by Sigma.
+
+We can use this event to adjust the iframe's height in real-time, ensuring that the iframe always matches the height of its content.
+
+We pre-built a page for you to save time. Browse to this URL:
+```code
+http://localhost:3000/responsive_embeds/res_event.html
+```
+
+Open your browser's developer tools (F12) and click the device toggle icon (top-left) to open the device simulation toolbar.
+
+This allows us to test different common device types as well as plain `Responsive`:
+
+<img src="assets/re_8.png">
+
+### What's involved
+
+Here are the steps required to integrate the `workbook:pageheight:onchange` event, along with the code used.
+
+**1: Listen for the Event:**<br>
+We added a global event listener to the window object to capture message events sent by the Sigma iframe using the postMessage API. This is because cross-document communication (like between a parent page and an iframe) uses the postMessage method and message event.
+
+```code
+// Global message event listener to capture messages from the Sigma iframe
+window.addEventListener("message", (event) => {
+```
+
+**2: Adjust the iframe Height:**<br>
+When the event is received, we check if its type matches 'workbook:pageheight:onchange' and then adjust the iframe height based on the pageHeight value provided.
+
+```code
+ // Respond to the Sigma event indicating the iframe content height has changed
+  if (event.data?.type === "workbook:pageheight:onchange") {
+    const newHeight = event.data.pageHeight;
+
+    // Ensure the height is a number and the iframe reference is valid
+    if (typeof newHeight === "number" && sigmaIframe) {
+      
+      // Dynamically resize the iframe to fit the embedded content
+      sigmaIframe.style.height = `${newHeight}px`;
+```
+
+<aside class="positive">
+<strong>IMPORTANT:</strong><br> For the postMessage and event listener to work, the iframe's source domain must allow cross-document messaging with the parent page's domain. Sigma already emits this event via postMessage, so it works out of the box.
+
+However, if there are any security restrictions, you might encounter issues. Always ensure that you're only accepting messages from trusted sources to prevent potential vulnerabilities.
+</aside>
+
+In the sample code:
+    <ul>
+        <li>The iframe is dynamic because it adjusts its height in real-time based on the content height, thanks to the Sigma event.</li>
+        <li>It’s also responsive in width because it adjusts to the full width of its container, ensuring it looks good on all screen sizes.</li> 
+    </ul>
+
+For more information, see [Implement inbound and outbound events in embeds](https://help.sigmacomputing.com/docs/inbound-and-outbound-events-in-embeds#actions)
+
+## What we've covered
+Duration: 5
+
+In this QuickStart, we learned how to implement a responsive Sigma embed inside an HTML page using both CSS and JavaScript.
+
+While the best approach depends on your use case, we hope this QuickStart helped you better understand how to embed Sigma responsively.
+
+**Additional Resource Links**
+
+[Blog](https://www.sigmacomputing.com/blog/)<br>
+[Community](https://community.sigmacomputing.com/)<br>
+[Help Center](https://help.sigmacomputing.com/hc/en-us)<br>
+[QuickStarts](https://quickstarts.sigmacomputing.com/)<br>
+
+Be sure to check out all the latest developments at [Sigma's First Friday Feature page!](https://quickstarts.sigmacomputing.com/firstfridayfeatures/)
+<br>
+
+[<img src="./assets/twitter.png" width="75"/>](https://twitter.com/sigmacomputing)&emsp;
+[<img src="./assets/linkedin.png" width="75"/>](https://www.linkedin.com/company/sigmacomputing)&emsp;
+[<img src="./assets/facebook.png" width="75"/>](https://www.facebook.com/sigmacomputing)
+
+![Footer](assets/sigma_footer.png)
+<!-- END OF WHAT WE COVERED -->
+<!-- END OF QUICKSTART -->
diff --git a/site/sigmaguides/src/embedding_15_public_access_v3/embedding_15_public_access_v3.md b/site/sigmaguides/src/embedding_15_public_access_v3/embedding_15_public_access_v3.md
index 32086d6d..c1d54cbd 100644
--- a/site/sigmaguides/src/embedding_15_public_access_v3/embedding_15_public_access_v3.md
+++ b/site/sigmaguides/src/embedding_15_public_access_v3/embedding_15_public_access_v3.md
@@ -70,7 +70,7 @@ For more information on Sigma's product release strategy, see [Sigma product rel
 If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
 
 ### Target Audience
-This QuickStart is designed for users familiar with Excel, Business Intelligence tools, or semi-technical users who want to try out or learn Sigma.
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
 
 ### Prerequisites
 
diff --git a/site/sigmaguides/src/embedding_dynamic_role_switching_v3/embedding_dynamic_role_switching_v3.md b/site/sigmaguides/src/embedding_dynamic_role_switching_v3/embedding_dynamic_role_switching_v3.md
index b908f399..b7bdd753 100644
--- a/site/sigmaguides/src/embedding_dynamic_role_switching_v3/embedding_dynamic_role_switching_v3.md
+++ b/site/sigmaguides/src/embedding_dynamic_role_switching_v3/embedding_dynamic_role_switching_v3.md
@@ -23,7 +23,7 @@ Many customers will use Snowflake's column masking functionality and also manage
  
 To simplify setup, we’ll use trial accounts and the provided Snowflake `ACCOUNTADMIN` role for the scripts we will run in Snowflake.
 
-In this QuickStart, we will use the local application framework we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
+In this QuickStart, we will use the local native application we created in [Embedding 01: Getting Started](https://quickstarts.sigmacomputing.com/guide/embedding_03_secure_access/index.html?index=..%2F..index#0)
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Some screens in Sigma may appear slightly different from those shown in QuickStarts. This is because Sigma continuously adds and enhances functionality. Rest assured, Sigma’s intuitive interface ensures that any differences will not prevent you from successfully completing any QuickStart.
@@ -34,24 +34,21 @@ For more information on Sigma's product release strategy, see [Sigma product rel
 If something is not working as you expect, here's how to [contact Sigma support](https://help.sigmacomputing.com/docs/sigma-support)
 
 ### Target Audience
-Semi-technical users who will be aiding in the planning or implementation of Sigma. Limited SQL and technical data skills are needed to do this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders, and performing basic edit/copy/paste operations.
+Semi-technical users who will be aiding in the planning or implementation of Sigma with embedding. No SQL or technical data skills are needed to complete this QuickStart. It does assume some common computer skills like installing software, using Terminal, navigating folders and copy/paste operations.
 
 ### Prerequisites
 
 <ul>
   <li>A computer with a current browser. It does not matter which browser you want to use.</li>
-  <li>Access to your Sigma environment. A Sigma trial environment is acceptable and preferred.</li>
-  <li>A working Node.js-based web server as demonstrated in Embedding 01: Getting Started</li>
-  <li>Some content to embed. You can embed a workbook, table, or visualization..</li>
-  <li>Downloadable project files discussed later in this document.</li>
-  <li>A Snowflake account with administrative and security admin access.</li>
+  <li>Access to your Sigma environment.</li>
+  <li>Embedding 01: Getting Started is required to complete this QuickStart.</li>
 </ul>
 
 <aside class="positive">
 <strong>IMPORTANT:</strong><br> Sigma recommends using non-production resources when completing QuickStarts.
 </aside>
 
-<button>[Sigma Free Trial](https://www.sigmacomputing.com/free-trial/)</button> <button>[Snowflake Free Trial](https://signup.snowflake.com/)</button>
+<button>[Sigma Free Trial](https://www.sigmacomputing.com/free-trial/)</button>
 
 <aside class="negative">
 <strong>IMPORTANT:</strong><br> Some features may carry a "Beta" tag. Beta features are subject to quick, iterative changes. As a result, the latest product version may differ from the contents of this document.