style: remove hyphens from compound adjectives in comments and messages

Remove hyphens from compound adjectives such as "logged-in", "one-time", "password-protected", "full-height", "multi-file", and "S3-compatible" in comments, test error messages, and UI labels to improve readability and consistency.

backend/templates/pages/api.html

@@ -152,12 +152,13 @@
       <article id="ep-resumable" class="endpoint card">
         <div class="card-content">
           <h3>Resumable uploads</h3>
-          <p>For large files. Browser uploads use this by default. Create a session with file metadata, <code>PUT</code> exact-sized chunks, then complete. Chunks are temporary and cleaned if the session expires. Send the same <code>Authorization</code> header on every request for authenticated sessions.</p>
+          <p>For large files. Browser uploads use this by default. Create a session with file metadata, <code>PUT</code> exact sized chunks, then complete. Chunks are temporary and cleaned if the session expires. Send the same <code>Authorization</code> header on every request for authenticated sessions.</p>
           <div class="endpoint-list">
             <div><span class="method method-post">POST</span><code>/api/v1/uploads/resumable</code><em>Create a session</em></div>
             <div><span class="method method-get">GET</span><code>/api/v1/uploads/resumable/{sessionID}</code><em>Session status</em></div>
             <div><span class="method method-put">PUT</span><code>/api/v1/uploads/resumable/{sessionID}/files/{fileID}/chunks/{index}</code><em>Upload one chunk</em></div>
             <div><span class="method method-post">POST</span><code>/api/v1/uploads/resumable/{sessionID}/complete</code><em>Finalize (returns the upload JSON)</em></div>
+            <div><span class="method method-delete">DELETE</span><code>/api/v1/uploads/resumable/{sessionID}</code><em>Cancel and delete an unfinished session</em></div>
           </div>
           <figure class="code-block">
             <pre><code># 1. Create a session.
@@ -173,7 +174,11 @@ dd if=./report.pdf bs=8388608 count=1 skip=0 2>/dev/null | \
 
 # 3. Complete after all chunks are present. The response is the normal upload JSON.
 curl -X POST -H 'Accept: application/json' \
-  {{.Data.BaseURL}}/api/v1/uploads/resumable/SESSION_ID/complete</code></pre>
+  {{.Data.BaseURL}}/api/v1/uploads/resumable/SESSION_ID/complete
+
+# Optional: cancel an unfinished session.
+curl -X DELETE -H 'X-Warpbox-Resume-Token: TOKEN' \
+  {{.Data.BaseURL}}/api/v1/uploads/resumable/SESSION_ID</code></pre>
           </figure>
           <p class="muted-copy">Incomplete chunks are stored under <code>data/tmp/uploads</code> before finalizing into the selected storage backend.</p>
         </div>
@@ -257,7 +262,7 @@ Add-Content $PROFILE 'function warpbox { &amp; "$HOME\warpbox.ps1" @args }'
           <div class="field-grid">
             <span><code>-p, --password</code></span><p>Require a password to open the box.</p>
             <span><code>-e, --expiry</code></span><p>Lifetime: <code>30m</code>, <code>6h</code>, <code>2d</code>, <code>1w</code> (or bare minutes).</p>
-            <span><code>-n, --max-downloads</code></span><p>Expire after N downloads.</p>
+            <span><code>-n, --max downloads</code></span><p>Expire after N downloads.</p>
             <span><code>-o, --obfuscate</code></span><p>Hide names/counts until unlock (needs <code>--password</code>).</p>
             <span><code>--json</code></span><p>Print the full JSON response instead of just the URL.</p>
             <span><code>--host</code></span><p>Server to upload to. Defaults to your <code>WARPBOX_HOST</code>.</p>
@@ -476,11 +481,15 @@ $resp.boxUrl</code></pre>
         </details>
         <details class="faq-item">
           <summary>How do I get file URLs and a delete link back?</summary>
-          <p>Send <code>Accept: application/json</code>. The response includes <code>boxUrl</code>, per-file <code>url</code>s, and the private <code>manageUrl</code>/<code>deleteUrl</code> (shown only once). See <a href="#responses" data-doc-link>the JSON response</a>.</p>
+          <p>Send <code>Accept: application/json</code>. The response includes <code>boxUrl</code>, per file <code>url</code>s, and the private <code>manageUrl</code>/<code>deleteUrl</code> (shown only once). See <a href="#responses" data-doc-link>the JSON response</a>.</p>
         </details>
         <details class="faq-item">
           <summary>How do I upload one big file reliably?</summary>
-          <p>Use the <a href="#ep-resumable" data-doc-link>resumable endpoints</a>: create a session, PUT chunks, then complete. Interrupted uploads can resume from the last chunk.</p>
+          <p>Use the <a href="#ep-resumable" data-doc-link>resumable endpoints</a>: create a session, PUT chunks, then complete. Interrupted uploads can resume from the last chunk, and unfinished sessions can be deleted with <code>DELETE /api/v1/uploads/resumable/{sessionID}</code>.</p>
+        </details>
+        <details class="faq-item">
+          <summary>Can clients show exact download progress?</summary>
+          <p>Yes. Individual file downloads and whole box <code>zipUrl</code> downloads include a precise <code>Content-Length</code>; range-capable responses also advertise <code>Accept-Ranges</code>.</p>
         </details>
         <details class="faq-item">
           <summary>Can I upload several files into one shareable link?</summary>