Update site from docs source repo

Author: Exploding Labs Bot

superstack/migrations/index.html

@@ -589,26 +589,23 @@ <h2 id="writing-migrations">✍️ Writing Migrations</h2>
 <h2 id="applying-migrations">▶️ Applying Migrations</h2>
 <p>When the Postgres container starts with no existing data, SuperStack will
 automatically run migrations once.</p>
-<p>After the first <code>docker compose up</code>, migrations will only run if you
-manually apply them.</p>
+<p>After the first startup, migrations will only run if you manually apply
+them.</p>
 <p>To apply your migrations, run:</p>
 <div class="highlight"><pre><span></span><code>bin/postgres<span class="w"> </span>migrate
 </code></pre></div>
 <p>This will:</p>
 <ol>
 <li>Run any migration files that haven’t been applied yet (in filename order)</li>
-<li>Record each successfully applied file in <code>.applied_migrations</code></li>
+<li>Record each successfully applied file in <code>.applied_migrations</code> (this
+   file lives in the postgres data volume)</li>
 </ol>
 <p>Already-applied scripts are skipped on subsequent runs.</p>
 <blockquote>
-<p>💡 <code>bin/postgres</code> is short for <code>docker compose exec postgres</code></p>
+<p>💡 <code>bin/postgres</code> is a small script that basically aliases <code>docker compose exec postgres</code></p>
 </blockquote>
-<h2 id="transactions">🔁 Transactions</h2>
-<p>Use <code>BEGIN;</code> and <code>COMMIT;</code> to wrap migration files when all included
-statements are transactional. This ensures that all changes are applied
-atomically.</p>
-<p>For example:</p>
-<div class="highlight"><span class="filename">postgres/migrations/03-create_table_example.sql</span><pre><span></span><code><span class="k">begin</span><span class="p">;</span>
+<p>Here's an example migration script:</p>
+<div class="highlight"><span class="filename">postgres/migrations/02-create_table_example.sql</span><pre><span></span><code><span class="k">begin</span><span class="p">;</span>
 
 <span class="k">create</span><span class="w"> </span><span class="k">table</span><span class="w"> </span><span class="n">director</span><span class="w"> </span><span class="p">(</span>
 <span class="w">  </span><span class="n">id</span><span class="w"> </span><span class="nb">serial</span><span class="w"> </span><span class="k">primary</span><span class="w"> </span><span class="k">key</span><span class="p">,</span>
@@ -623,13 +620,13 @@ <h2 id="transactions">🔁 Transactions</h2>
 
 <span class="k">commit</span><span class="p">;</span>
 </code></pre></div>
-<blockquote>
-<p>💡 If your migration script only contains one statement, there's no need
-to use a transaction, the statement will be auto-committed.</p>
-</blockquote>
+<h2 id="transactions">🔁 Transactions</h2>
+<p>Use <code>begin;</code> and <code>commit;</code> to wrap statements in a transaction. This
+ensures that all changes are applied atomically. Any statements outside of
+transactions will be auto-committed.</p>
 <p>Avoid wrapping non-transactional operations in a transaction — these will
-cause errors if used inside <code>BEGIN ... COMMIT</code>.</p>
-<p>Examples of non-transactional statements include:</p>
+cause errors if used inside <code>begin ... commit</code>. Examples of
+non-transactional statements include:</p>
 <div class="highlight"><pre><span></span><code><span class="k">CREATE</span><span class="w"> </span><span class="n">EXTENSION</span>
 <span class="k">DROP</span><span class="w"> </span><span class="n">EXTENSION</span>
 <span class="k">VACUUM</span>