@@ -41,7 +41,7 @@ <h1>The production worker for Django Tasks</h1>
           development only. <strong><span data-brand>Oxpull</span></strong> stores the queue in the
           database you already run and executes tasks with a separate worker process. No broker,
           no Redis, nothing new to operate.</p>
-        <p class="hero-sub">The part that matters: <code>enqueue()</code> is a plain INSERT on your
+        <p class="hero-sub"><code>enqueue()</code> is a plain INSERT on your
           default connection, so a task enqueued inside <code>transaction.atomic()</code> commits
           or rolls back together with your business data. A broker cannot share your database
           transaction. There is no window where an order exists without its email task, and no
@@ -70,8 +70,8 @@ <h2>Measured, not promised</h2>
           37,804 tasks, including nine minutes in which a worker was SIGKILLed every 20 to
           45 seconds. Every task reached a terminal state, no task ran twice in this run,
           and every interrupted execution was re-executed inside the documented bound.
-          Execution is at-least-once: a worker killed after the work finished but before
-          the result was recorded leaves that task to run again, and the harness asserts
+          Execution is at-least-once. A worker killed after the work finished but before
+          the result was recorded leaves that task to run again. The harness asserts
           that a second execution is only ever attributable to a kill.</p>
         <p class="caveat">No-op benchmarks flatter every queue, so read these as relative, not as
           capacity planning. The full methodology, every run, and the raw per-sample data ship in
@@ -89,12 +89,12 @@ <h3><span data-package>django-ox</span> <span class="tag">BSD-3 &middot; free fo
             <ul>
               <li>Durable queue in your existing database</li>
               <li>Transactional enqueue</li>
-              <li>At-least-once execution, SKIP LOCKED claiming</li>
+              <li>At-least-once execution, SKIP LOCKED claiming on PostgreSQL and MySQL 8</li>
               <li>Retries with backoff, per-attempt tracebacks</li>
               <li>Reaper for tasks from dead workers</li>
               <li>Graceful drain on SIGTERM</li>
               <li>Priorities, deferred tasks, multiple queues</li>
-              <li>Recurring schedules, cron syntax</li>
+              <li>Recurring schedules, cron or fixed interval, in settings or the Django admin</li>
               <li>Pruning command for finished rows</li>
               <li>Stats API and health command</li>
             </ul>
@@ -108,15 +108,15 @@ <h3><span data-package>django-ox</span> <span class="tag">BSD-3 &middot; free fo
           <div class="tier pro-tier">
             <h3><span data-brand>Oxpull</span> Pro <span class="tag">commercial license</span></h3>
             <ul>
-              <li>Batches: enqueue many, track as one</li>
+              <li>Batches: group tasks, with a callback when every member is settled</li>
               <li>Unique tasks (deduplication)</li>
               <li>Rate limiting</li>
               <li>Email support from the maintainer</li>
               <li>Requires Django 6.0 or later</li>
             </ul>
-            <p class="note">All three are built and tested. Not yet on sale: the purchase path is still
-              being set up, and the waitlist below is how to hear when it opens. Delivered from a private
-              package index using credentials issued per company, with no licence key and no runtime check
+            <p class="note">All three are built and tested. Pro is not on sale yet, and the waitlist
+              below is how to hear when it opens. Delivered from a private
+              package index using credentials issued per company, with no license key and no runtime check
               to break your production. Install stays <code>pip install</code>.</p>
           </div>
         </div>
@@ -136,7 +136,8 @@ <h2>Pricing, and the waitlist</h2>
           </form>
           <p id="form-error" hidden>That didn't go through. Check the address and try again.</p>
           <p class="privacy">Your email is used only to tell you when Pro launches. Reply
-            "remove" and it is deleted.</p>
+            "remove", or write to <a href="mailto:[email protected]">[email protected]</a>,
+            and it is deleted.</p>
         </div>
       </section>
 
@@ -146,28 +147,29 @@ <h2>Questions you should ask</h2>
         <h3>What is the license situation?</h3>
         <p>The worker itself, <span data-package>django-ox</span>, is BSD 3-Clause and stays
           that way. Pro is separate code under a commercial license, sold per company. The free
-          tier is not a demo; it is the backend the docs mean when they say production systems
+          tier is not a demo. It is the backend the docs mean when they say production systems
           need a durable queue and a worker process.</p>
 
         <h3>When does this ship?</h3>
         <p>The open source worker is live: <code>pip install django-ox</code>, with
           <a href="https://oxpull.com/django-ox/">documentation here</a>. Pro is built and
-          tested; what is left is the purchase path. Waitlist email is the announcement channel.</p>
+          tested. What is left is the purchase path. Waitlist email is the announcement channel.</p>
 
         <h3>Who is behind it?</h3>
         <p>An independent software vendor with one product: this one. You will know who
           maintains it, contracts get signed under the company name, and support answers come
           from the person who wrote the code.</p>
 
         <h3>What does support look like?</h3>
-        <p>Open source: GitHub issues, taken seriously. Pro: email support from
-          the maintainer. If your procurement needs a PO and an invoice instead of a card,
-          say so on the waitlist; invoiced purchasing is planned alongside self-serve.</p>
+        <p>Open source support is on GitHub issues. Pro comes with email support from
+          the maintainer at <a href="mailto:[email protected]">[email protected]</a>. If your
+          procurement needs a PO and an invoice instead of a card, write to that address.
+          Invoiced purchasing is planned alongside self-serve.</p>
 
         <h3>Do I need Pro to run production?</h3>
         <p>No. Durability, retries, the reaper, and graceful shutdown are all in the free
           worker, and so are the stats API and the health command. Pro adds three
-          things the free tier does not do: batching, deduplication and rate limiting.
+          things the free tier does not do: batches, deduplication and rate limiting.
           Support comes with it. Pro needs Django 6.0 or later. The free worker also
           runs on Django 5.2 LTS through the <code>django-tasks</code> backport, and
           Pro does not.</p>
 
@@ -19,8 +19,9 @@
 
     <main class="thanks">
       <h1>You're on the list</h1>
-      <p>Expect one email: when Pro opens. Nothing else, ever, and a reply
-        saying "remove" deletes your address. Meanwhile the open source worker is live:
+      <p>You'll get one email, when Pro opens, and nothing else, ever. Reply "remove" to it, or
+        write to <a href="mailto:[email protected]">[email protected]</a> at any time, and your
+        address is deleted. Meanwhile the open source worker is live:
         <code>pip install django-ox</code>.</p>
       <p><a href="index.html">Back to the page</a></p>
     </main>