fix(public): remove internal editorial and submission-prep copy from the four app pages

public/drishti/index.html

@@ -124,9 +124,9 @@ <h1>Drishti helps bring awareness to screen time before distraction takes over.<
           <aside class="page-card dark">
             <p class="eyebrow">Why this matters</p>
             <ul class="plain-list">
-              <li>Drishti already feels like a real product, not an abstract idea.</li>
-              <li>The support and privacy pages are stable enough for submission.</li>
-              <li>Future launch updates can happen without restructuring the site.</li>
+              <li>A mindful pause before distracting app opens.</li>
+              <li>Clear support and privacy pages for users.</li>
+              <li>Compassionate tracking instead of shame-based nudges.</li>
             </ul>
           </aside>
         </section>
@@ -136,45 +136,44 @@ <h1>Drishti helps bring awareness to screen time before distraction takes over.<
             <p class="eyebrow">Product page</p>
             <h2>A calmer way to interrupt the scroll reflex.</h2>
             <p>
-              This page already carries the core story: Drishti uses pauses,
-              intention, and mindful practice to change how distracting app
-              opens feel in the moment.
+              The core story is simple: Drishti uses pauses, intention, and
+              mindful practice to change how distracting app opens feel in the
+              moment.
             </p>
           </article>
 
           <article class="info-card reveal delay-2">
             <p class="eyebrow">Pause flow</p>
             <h2>Awareness before “Open Anyway.”</h2>
             <p>
-              The current product definition is explicit: Drishti intercepts
-              distraction, offers a mindful pause, and lets the user either
-              honor intention or proceed without guilt.
+              Drishti intercepts distraction, offers a mindful pause, and lets
+              the user either honor intention or proceed without guilt.
             </p>
           </article>
 
           <article class="info-card reveal delay-3">
             <p class="eyebrow">Practice layers</p>
             <h2>Built around rituals, streaks, and compassion.</h2>
             <p>
-              The app data already points to breathing exercises, streak
-              milestones, ritual rules, focus windows, accountability features,
-              and compassionate tracking language instead of shame-based nudges.
+              Drishti includes breathing exercises, streak milestones, ritual
+              rules, focus windows, accountability features, and compassionate
+              tracking language instead of shame-based nudges.
             </p>
           </article>
         </section>
 
         <section class="app-strip reveal delay-2">
           <div class="app-strip-grid">
             <article>
-              <p class="eyebrow">What Drishti already emphasizes</p>
+              <p class="eyebrow">What Drishti emphasizes</p>
               <ul class="plain-list">
                 <li>Mindful pause before opening a distracting app</li>
                 <li>Honor intention or open anyway with compassionate language</li>
                 <li>Onboarding built as a breathing and reflection experience</li>
               </ul>
             </article>
             <article>
-              <p class="eyebrow">Practice layers in the current build</p>
+              <p class="eyebrow">Practice layers</p>
               <ul class="plain-list">
                 <li>Streak milestones with haptic celebrations</li>
                 <li>Ritual rules, focus windows, and accountability flows</li>
@@ -195,11 +194,11 @@ <h2>Built around rituals, streaks, and compassion.</h2>
               </ul>
             </article>
             <article>
-              <p class="eyebrow">Launch note</p>
+              <p class="eyebrow">The practice</p>
               <p class="section-copy">
-                When the App Store listing is ready, this page can add the
-                storefront badge, visuals, and launch details without losing
-                the calmer spiritual voice the product already has.
+                Every part of Drishti points the same way: pause, check
+                intention, and choose — with streaks and rituals supporting the
+                habit instead of shaming the slip.
               </p>
             </article>
           </div>

public/drishti/support/index.html

@@ -49,12 +49,11 @@
         <section class="page-hero-card reveal">
           <div>
             <p class="eyebrow">Drishti support</p>
-            <h1>Drishti support is in place before launch day.</h1>
+            <h1>Drishti support for pauses, permissions, and tracking.</h1>
             <p class="page-lead">
-              Use this page as the public support URL for Drishti. It creates a
-              clear help path for future users while giving the app a stable
-              support destination for mindful-pause, permissions, and tracking
-              issues in the meantime.
+              This page is the support home for Drishti. If something feels off
+              with a mindful pause, permissions, or tracking, this is where to
+              start.
             </p>
             <div class="action-row">
               <a class="button" href="mailto:support@tinystudio.in">Email Drishti support</a>
@@ -76,17 +75,17 @@ <h1>Drishti support is in place before launch day.</h1>
         <section class="card-grid">
           <article class="info-card reveal delay-1">
             <p class="eyebrow">Email route</p>
-            <h2>Ready for real support traffic.</h2>
+            <h2>A single, clear support route.</h2>
             <p>
               Drishti support routes through Tiny Studio’s support inbox with an
-              app-specific subject line so the public support flow is clean and
-              easy to recognize later for pause, ritual, or awareness-related issues.
+              app-specific subject line, so questions stay easy to recognize
+              and triage for pause, ritual, or awareness-related issues.
             </p>
           </article>
 
           <article class="info-card reveal delay-2">
             <p class="eyebrow">Related pages</p>
-            <h2>Everything a launch page needs nearby.</h2>
+            <h2>Everything you need nearby.</h2>
             <p>
               Drishti’s support page is paired with an app privacy page, the
               studio contact page, and the general Tiny Studio support hub.
@@ -95,10 +94,10 @@ <h2>Everything a launch page needs nearby.</h2>
 
           <article class="info-card reveal delay-3">
             <p class="eyebrow">Public role</p>
-            <h2>Stable now, useful later.</h2>
+            <h2>A lasting support destination.</h2>
             <p>
-              This support page already works for submission and will continue
-              to be the right public support destination after launch.
+              Drishti support stays at this URL, so the address you find today
+              is the same one to use later.
             </p>
           </article>
         </section>

public/promptly/index.html

@@ -122,12 +122,11 @@ <h1>Promptly keeps solo professionals booked, prepared, and harder to ghost.</h1
           </div>
 
           <aside class="page-card dark">
-            <p class="eyebrow">What this page already does</p>
+            <p class="eyebrow">Why this matters</p>
             <ul class="plain-list">
-              <li>Gives the product a stable public URL.</li>
-              <li>Explains the professional-first booking workflow clearly.</li>
-              <li>Provides a support destination for App Store Connect.</li>
-              <li>Keeps privacy and contact links one tap away.</li>
+              <li>Bookings, reminders, and payment proof in one workflow.</li>
+              <li>Clients confirm, reschedule, or cancel from a link.</li>
+              <li>Support and privacy are one tap away.</li>
             </ul>
           </aside>
         </section>
@@ -137,9 +136,9 @@ <h1>Promptly keeps solo professionals booked, prepared, and harder to ghost.</h1
             <p class="eyebrow">Product page</p>
             <h2>Built for the actual booking day.</h2>
             <p>
-              Promptly is already positioned as a tool for bookings, reminders,
-              payment proof, and cleaner day-of operations. The App Store badge
-              and launch materials can slot into that story later.
+              Promptly is a tool for bookings, reminders, payment proof, and
+              cleaner day-of operations — everything a solo professional needs
+              to run the day from one app.
             </p>
           </article>
 
@@ -157,25 +156,25 @@ <h2>Clients do not need the app.</h2>
             <p class="eyebrow">Operations</p>
             <h2>Reminders, proof, and calendar clarity.</h2>
             <p>
-              The current build data already points to reminder scheduling,
-              calendar sync, push notifications, phone OTP, and payment-proof
-              handling as part of the working product surface.
+              Promptly handles reminder scheduling, calendar sync, push
+              notifications, phone OTP, and payment-proof records as part of the
+              working product.
             </p>
           </article>
         </section>
 
         <section class="app-strip reveal delay-2">
           <div class="app-strip-grid">
             <article>
-              <p class="eyebrow">What Promptly already centers</p>
+              <p class="eyebrow">What Promptly centers</p>
               <ul class="plain-list">
                 <li>Professional onboarding by role, region, messaging, and payments</li>
                 <li>Public booking flow for new appointments</li>
                 <li>Reminder windows at 24 hours, 2 hours, and 30 minutes</li>
               </ul>
             </article>
             <article>
-              <p class="eyebrow">Operational details in the current build</p>
+              <p class="eyebrow">Operational details</p>
               <ul class="plain-list">
                 <li>Booking CRUD and services management</li>
                 <li>Calendar sync and push notifications</li>
@@ -196,11 +195,11 @@ <h2>Reminders, proof, and calendar clarity.</h2>
               </ul>
             </article>
             <article>
-              <p class="eyebrow">Launch note</p>
+              <p class="eyebrow">The workflow</p>
               <p class="section-copy">
-                Once the App Store listing is ready, this page can add the
-                badge, screenshots, and sharper proof points without changing
-                the underlying positioning.
+                Bookings, reminders, payment proof, and client action links
+                stay in one focused workflow — for the professional running the
+                day and for the client on the other end of a link.
               </p>
             </article>
           </div>

public/promptly/support/index.html

@@ -49,12 +49,11 @@
         <section class="page-hero-card reveal">
           <div>
             <p class="eyebrow">Promptly support</p>
-            <h1>Promptly support is already public and easy to use.</h1>
+            <h1>Promptly support for bookings, reminders, and client links.</h1>
             <p class="page-lead">
-              Use this page as the public support URL for Promptly. It keeps
-              the support path clean for future users while also working well as
-              an App Store support destination for booking, reminder, payment,
-              and client-link issues.
+              This page is the support home for Promptly. If something goes
+              wrong with bookings, reminders, payment proof, or client action
+              links, this is where to start.
             </p>
             <div class="action-row">
               <a class="button" href="mailto:support@tinystudio.in">Email Promptly support</a>
@@ -76,7 +75,7 @@ <h1>Promptly support is already public and easy to use.</h1>
         <section class="card-grid">
           <article class="info-card reveal delay-1">
             <p class="eyebrow">Email route</p>
-            <h2>A support address that is ready now.</h2>
+            <h2>A single, clear support route.</h2>
             <p>
               Promptly support goes directly to Tiny Studio’s public support
               inbox using an app-specific subject line for cleaner triage across
@@ -95,10 +94,11 @@ <h2>Support, privacy, and contact stay connected.</h2>
 
           <article class="info-card reveal delay-3">
             <p class="eyebrow">Public role</p>
-            <h2>Useful before launch and after it.</h2>
+            <h2>A lasting support destination.</h2>
             <p>
-              This page is already stable enough for App Store Connect and will
-              remain useful once Promptly is publicly available.
+              Promptly support stays at this URL, so the address you find today
+              is the same one to use later for booking, reminder, payment, and
+              client-link questions.
             </p>
           </article>
         </section>