diff --git a/content/en/case-studies/squarespace.html b/content/en/case-studies/squarespace.html
index 95e04e6b9cc..58c5cae5cc2 100644
--- a/content/en/case-studies/squarespace.html
+++ b/content/en/case-studies/squarespace.html
@@ -1,6 +1,5 @@
 ---
 title: Squarespace Case Study
-
 case_study_styles: true
 cid: caseStudies
 css: /css/style_case_studies.css
@@ -39,7 +38,8 @@ Since Squarespace moved to Kubernetes, in conjunction with modernizing its netwo
 </section>
 <div class="banner2">
   <div class="banner2text">
-    "Once you prove that Kubernetes solves one problem, everyone immediately starts solving other problems without you even having to evangelize it."
+    <iframe width="560" height="315" src="https://www.youtube.com/embed/feQkzJkW-SA" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
+    <br><br>"Once you prove that Kubernetes solves one problem, everyone immediately starts solving other problems without you even having to evangelize it."
 <br style="height:25px"><span style="font-size:14px;letter-spacing:2px;text-transform:uppercase;margin-top:5% !important;"><br>— Kevin Lynch, Staff Engineer on the Site Reliability team at Squarespace</span>
   </div>
 </div>
@@ -74,7 +74,7 @@ Since Squarespace moved to Kubernetes, in conjunction with modernizing its netwo
   </div>
 </div>
 
-<section class="section5">
+<section class="section5" style="padding:0px !important">
 <div class="fullcol">
   There’s also been a positive impact on the application’s resilience. "When we’re deploying VMs, we have to build tooling to ensure that a service is spread across racks appropriately and can withstand failure," he says. "Kubernetes just does it. If a node goes down, it’s rescheduled immediately and there’s no performance impact."
 <br><br>