diff --git a/website/assets/styles/pages/landing-pages/patch-faster.less b/website/assets/styles/pages/landing-pages/patch-faster.less
index 1040d13669..6d983d2d1a 100644
--- a/website/assets/styles/pages/landing-pages/patch-faster.less
+++ b/website/assets/styles/pages/landing-pages/patch-faster.less
@@ -315,7 +315,7 @@
     max-width: @max-content;
     margin: 0 auto;
     display: grid;
-    grid-template-columns: repeat(3, 1fr);
+    grid-template-columns: repeat(2, 1fr);
     gap: 40px;
     text-align: center;
   }
diff --git a/website/views/pages/landing-pages/patch-faster.ejs b/website/views/pages/landing-pages/patch-faster.ejs
index 02057142ce..82410603a7 100644
--- a/website/views/pages/landing-pages/patch-faster.ejs
+++ b/website/views/pages/landing-pages/patch-faster.ejs
@@ -5,8 +5,8 @@
     <div purpose="hero">
       <div purpose="hero-copy">
         <p purpose="eyebrow">Software management</p>
-        <h1>Stop waiting on your MDM</h1>
-        <p purpose="hero-subhead">When a critical patch drops, the bottleneck isn't your team. It's your toolchain. Fleet's maintained app catalog and automated patch policies push updates to your devices on a regular, predictable cadence. No manual repackaging. No osquery queries to write. No waiting.</p>
+        <h1>Automated patching is becoming inevitable</h1>
+        <p purpose="hero-subhead">When a critical patch drops, you're not always at your computer. Fleet's maintained app catalog and automated patch policies push updates to your devices on a regular, predictable cadence, even over the weekend, and without manual repackaging.</p>
       </div>
       <div purpose="hero-form-col">
         <div id="demo-form" purpose="form-card" v-if="!cloudSuccess">
@@ -65,8 +65,8 @@
     <div purpose="problem-section">
       <h2>Manual patching doesn't scale.</h2>
       <div purpose="prose">
-        <p>When a critical CVE drops, the clock starts. But for most IT and security teams, the bottleneck isn't awareness, it's the toolchain. Someone has to download the new version, validate it, package it, and get it into the catalog before a single device gets updated. If you're doing that manually, you're burning engineering time on work that doesn't have to be manual.</p>
-        <p>The alternative is a catalog that's maintained for you, and policies that trigger automatically when a device falls behind. That's the difference between patching as a project and patching as a background process.</p>
+        <p>When a critical CVE drops, the clock starts. But for most IT and security teams, the opportunity cost of packaging and automating every single app is really hard to justify, because there is other important work to do. Someone has to download the new version, validate it, package it, and get it into the catalog before a single device gets updated.</p>
+        <p>The alternative is a catalog that's maintained for you, and policies that install software updates automatically, while still respecting the exceptions, flexibility, and user experience considerations you need to take into account to keep your end users productive.</p>
       </div>
     </div><%/* problem-section */%>
 
@@ -93,7 +93,7 @@
           </div>
           <div purpose="feature-body">
             <p purpose="feature-label">Patch policies that run automatically</p>
-            <p purpose="feature-desc">A patch policy checks whether each Fleet maintained app is up to date on your hosts. Fleet auto-generates the correct osquery query for each app, so you don't write or update them. When a host fails the policy, Fleet automatically sends an install request.</p>
+            <p purpose="feature-desc">A patch policy checks whether each Fleet maintained app is up to date on your hosts. Fleet watches each app, so you don't write or update any code. When a host fails the policy, Fleet automatically sends an install request.</p>
           </div>
         </div>
 
@@ -126,10 +126,10 @@
   <div purpose="proof-strip-container">
     <div purpose="proof-strip">
       <div purpose="proof-inner">
-        <div purpose="proof-item">
+        <% /* %><div purpose="proof-item">
           <p purpose="proof-highlight">No osquery queries to write</p>
           <p purpose="proof-detail">Fleet auto-generates the correct query for each Fleet-maintained app.</p>
-        </div>
+        </div><% */ %>
         <div purpose="proof-item">
           <p purpose="proof-highlight">One-hour policy cadence</p>
           <p purpose="proof-detail">Policy checks run on a typical one-hour  cadence on all online hosts.</p>
@@ -147,7 +147,7 @@
     <%/* ─── PLATFORM CALLOUT ───────────────────────────────── */%>
     <div purpose="platform-section">
       <h2>One platform. Every OS.</h2>
-      <p purpose="platform-body">Fleet manages software across macOS, Windows, and Linux from a single place. The same patch policies, the same catalog, the same automation, whether you're supporting a Mac-first team, a Windows shop, or a mixed environment with Linux servers.</p>
+      <p purpose="platform-body">Fleet manages software across macOS, Windows, and Linux from a single place. The same patch policies, the same catalog, the same automation, whether you're supporting a Mac-first team, a Windows shop, or a mixed environment with Linux.</p>
       <div purpose="os-pills">
         <span purpose="os-pill">
           <svg width="16" height="16" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"><path d="M18.71 19.5c-.83 1.24-1.71 2.45-3.05 2.47-1.34.03-1.77-.79-3.29-.79-1.53 0-2 .77-3.27.82-1.31.05-2.3-1.32-3.14-2.53C4.25 17 2.94 12.45 4.7 9.39c.87-1.52 2.43-2.48 4.12-2.51 1.28-.02 2.5.87 3.29.87.78 0 2.26-1.07 3.8-.91.65.03 2.47.26 3.64 1.98-.09.06-2.17 1.28-2.15 3.81.03 3.02 2.65 4.03 2.68 4.04-.03.07-.42 1.44-1.38 2.83M13 3.5c.73-.83 1.94-1.46 2.94-1.5.13 1.17-.34 2.35-1.04 3.19-.69.85-1.83 1.51-2.95 1.42-.15-1.15.41-2.35 1.05-3.11z"/></svg>
@@ -165,7 +165,7 @@
     </div><%/* platform-section */%>
 
     <%/* ─── INTEGRATIONS ───────────────────────────────────── */%>
-    <div purpose="integrations-section">
+    <% /* <div purpose="integrations-section">
       <h2>Works with the tools you already use.</h2>
       <p purpose="integrations-body">Use policy automations to trigger app updates, create tickets in Jira or Zendesk, or generate webhooks to connect Fleet to your existing workflows. Patching fits into the process you already have.</p>
       <div purpose="integration-pills">
@@ -174,7 +174,7 @@
         <span purpose="integration-pill">Webhooks</span>
         <span purpose="integration-pill">GitOps</span>
       </div>
-    </div><%/* integrations-section */%>
+    </div> */ %><%/* integrations-section */%>
 
   </div><%/* below-fold-container */%>