Update site from docs source repo

Author: Exploding Labs Bot

superstack/deploying/index.html

@@ -655,9 +655,10 @@ <h2 id="3-deploy-the-compose-file">📦 3. Deploy the Compose File</h2>
 <h3 id="4-set-secrets">4. Set Secrets</h3>
 <p>The stack needs your secrets (passwords, keys, etc.). There are a few options:</p>
 <ol>
-<li>Put secrets in a <code>.env</code> file on the server (convenient but less secure).</li>
-<li>Set environment variables in the the <code>docker compose</code> command, being sure to
-   disable shell history (inconvenient).</li>
+<li>Put secrets in a <code>.env</code> file on the server. Convenient but Less secure. Be
+   sure to <code>chmod 600 .env</code>.</li>
+<li>Set environment variables in the the <code>docker compose</code> command. Inconvenient.
+   Be sure to disable shell history.</li>
 <li>Use environment injection in your CI/CD.</li>
 </ol>
 <h2 id="5-launch-your-stack">🚀 5. Launch your Stack</h2>

superstack/gettingstarted/index.html

@@ -698,12 +698,7 @@ <h2 id="2-configure-environment-variables">2. Configure Environment Variables</h
 <p>Copy the example environment file:</p>
 <div class="highlight"><pre><span></span><code>cp<span class="w"> </span>example.env<span class="w"> </span>.env
 </code></pre></div>
-<p>This <code>.env</code> file is used to configure:</p>
-<ul>
-<li><strong>Secrets</strong> – Passwords, keys, etc.</li>
-<li><strong>Ports</strong> – Adjust the exposed ports (specifically, Caddy's) depending on
-  environment or application (you may bring up multiple).</li>
-</ul>
+<p>This <code>.env</code> file is used to set secrets, passwords, keys, etc.</p>
 <blockquote>
 <p>⚠️ Never store secrets in version control.</p>
 </blockquote>