Rewrite the prose without em-dashes across docs, comments and copy

Author: meliharik

CHANGELOG.md

@@ -12,7 +12,7 @@ First release.
 
 - Force update, soft update and maintenance mode, decided by the protocol's
   evaluation order and verified against the golden vectors.
-- Remote config values in the same signed payload — no extra request.
+- Remote config values in the same signed payload, so there is no extra request.
 - Ed25519 verification of the exact response bytes, with pinned keys and
   `key_id` rotation.
 - Signed cache in localStorage, re-verified on read.

README.md

@@ -9,12 +9,12 @@
   <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue.svg" alt="License: MIT"></a>
 </p>
 
-<p align="center"><b>Remote config, update walls and maintenance mode for web apps — signed at the edge, verified in the browser, 6.5 KB gzipped.</b></p>
+<p align="center"><b>Remote config, update walls and maintenance mode for web apps. Signed at the edge, verified in the browser, 6.5 KB gzipped.</b></p>
 
 ## Installation
 
-`@ripstop/web` is not on npm yet. Until it is, install straight from GitHub —
-the package builds itself on install:
+`@ripstop/web` is not on npm yet. Until it is, install straight from GitHub.
+The package builds itself on install:
 
 ```bash
 npm install github:ripstop-dev/ripstop-web
@@ -53,12 +53,12 @@ switch (decision.type) {
 
 `appVersion` is explicit here and always will be. The Swift and Flutter SDKs
 read the installed version from the bundle, but a browser has no bundle and no
-installed version to read — the only thing that knows which build is running is
+installed version to read. The only thing that knows which build is running is
 the build itself, so it has to hand the string over. Every bundler can: Vite's
 `define`, webpack's `DefinePlugin`, or an env var read at build time.
 
 Pass a semantic version, not a commit SHA. The rules are ordered as semantic
-versions, and anything that is not one is treated as no opinion — which lets the
+versions, and anything that is not one is treated as no opinion, which lets the
 app run rather than walling it, but also means your rules do nothing.
 
 ## What `force` means on the web
@@ -70,7 +70,7 @@ response is usually `location.reload()`.
 
 That is also why the web SDK ships no prebuilt walls. On mobile, a full-screen
 update wall is the same shape in every app. On the web it is a banner, a modal,
-or a route — entirely yours. You get the decision and the copy you wrote in the
+or a route, entirely yours. You get the decision and the copy you wrote in the
 panel; the markup is your business.
 
 ## Remote config
@@ -83,15 +83,15 @@ const checkout = ripstop.value('checkout_enabled', true);
 const limit = ripstop.value('upload_limit', 10);
 ```
 
-Always pass a fallback. On a first load with no network there is no payload yet
-— that is the fail-open path working as intended.
+Always pass a fallback. On a first load with no network there is no payload
+yet. That is the fail-open path working as intended.
 
 ## API
 
 | | Default | |
 | --- | --- | --- |
-| `apiKey` | — | Your app's public SDK key. Safe to ship |
-| `appVersion` | — | The build you are running; rules evaluate against it |
+| `apiKey` | required | Your app's public SDK key. Safe to ship |
+| `appVersion` | required | The build you are running; rules evaluate against it |
 | `locale` | `en` | Which wall copy to resolve; falls back to `en` per key |
 | `minFetchInterval` | 6 hours | How long a payload is fresh enough to skip the network |
 | `timeoutMs` | 5000 | Fetch budget. After that, cache |
@@ -104,7 +104,7 @@ Always pass a fallback. On a first load with no network there is no payload yet
 | Situation | What your app does |
 | --- | --- |
 | Network unavailable | Uses the last **signed** payload from localStorage |
-| No network, no cache | `none` — your app runs, unrestricted |
+| No network, no cache | `none`, so your app runs unrestricted |
 | Edge returns 5xx, or times out | Cache, then normal |
 | Signature doesn't verify | Discarded. A forged payload can never wall your app |
 | localStorage edited in devtools | Re-verified on read, so it grants nothing |
@@ -122,7 +122,7 @@ simply doesn't persist a cache.
 
 ## Conformance
 
-Every Ripstop SDK runs the same `vectors.json` — version ordering, evaluation
+Every Ripstop SDK runs the same `vectors.json`: version ordering, evaluation
 order, message fallback, snooze accounting, the fail-open state machine.
 `npm test` runs it here. If this package and the reference implementation ever
 disagree about a single comparison, CI goes red.

package.json

@@ -1,7 +1,7 @@
 {
   "name": "@ripstop/web",
   "version": "0.1.0",
-  "description": "Remote config, update walls and maintenance mode for web apps — signed at the edge, verified in the browser.",
+  "description": "Remote config, update walls and maintenance mode for web apps. Signed at the edge, verified in the browser.",
   "license": "MIT",
   "type": "module",
   "repository": {

src/client.ts

@@ -1,7 +1,7 @@
 /**
  * The client: fetch, verify, cache, decide.
  *
- * Web differs from mobile in one way that shapes everything here — there is no
+ * Web differs from mobile in one way that shapes everything here: there is no
  * app store and no "old build in the field", because a reload gets the latest
  * code. So `force` on web is not about a binary being stale, it is about a tab
  * that has been open for three days while you shipped a breaking change. The
@@ -178,8 +178,8 @@ export class Ripstop {
 
   /**
    * Adopts a payload only if it still verifies. Cached payloads get the same
-   * scrutiny as fresh ones — localStorage is editable from the console, so
-   * trusting it would make every wall a suggestion.
+   * scrutiny as fresh ones, because localStorage is editable from the console
+   * and trusting it would make every wall a suggestion.
    */
   private async adopt(
     body: string,

src/evaluate.ts

@@ -51,7 +51,7 @@ export function evaluate(config: RipstopConfig, ctx: EvaluateContext): Decision
   const locale = ctx.locale ?? FALLBACK_LOCALE;
   const version = parseVersion(ctx.appVersion);
 
-  // 1. Maintenance — `active` is server-evaluated at fetch time; starts_at/ends_at are display-only.
+  // 1. Maintenance. `active` is server-evaluated at fetch time; starts_at/ends_at are display-only.
   const maintenance = config.maintenance;
   if (maintenance.active) {
     return {
@@ -65,7 +65,7 @@ export function evaluate(config: RipstopConfig, ctx: EvaluateContext): Decision
     };
   }
 
-  // 2–3. Force / soft — need a platform entry and a parseable version; otherwise fail open.
+  // 2–3. Force / soft need a platform entry and a parseable version; otherwise fail open.
   const entry = config.update[ctx.platform];
   if (entry === undefined || version === null) return { type: 'none' };
 

src/index.ts

@@ -1,5 +1,5 @@
 /**
- * Ripstop for the web — remote config, update walls and maintenance mode,
+ * Ripstop for the web: remote config, update walls and maintenance mode,
  * signed at the edge and verified in the browser.
  *
  * ```ts

src/storage.ts

@@ -2,7 +2,7 @@
  * Where the last signed payload and the snooze ledger live.
  *
  * The payload is stored *with* its signature and re-verified on read, so a
- * cached config carries exactly as much authority as a fresh one — and no more.
+ * cached config carries exactly as much authority as a fresh one, and no more.
  * On the web this matters more than on mobile: localStorage is two keystrokes
  * away in devtools, so a cache that were trusted would make every wall a
  * polite request.

src/types.ts

@@ -5,7 +5,7 @@
  * ~14 KB gzipped and would be the largest thing in a package whose whole point
  * is to be small enough that nobody thinks twice about adding it. The server
  * already guarantees the shape, the signature guarantees the bytes came from
- * the server, and anything unreadable falls open — so a schema library here
+ * the server, and anything unreadable falls open, so a schema library here
  * would buy a nicer error message on a path that is already safe.
  */
 

src/verify.ts

@@ -6,7 +6,7 @@
  * silently degrades on older Safari is worse than one that carries 4 KB.
  *
  * The signature covers the raw response body, so verification happens before
- * anything is parsed — `JSON.parse` then `JSON.stringify` would produce
+ * anything is parsed. `JSON.parse` then `JSON.stringify` would produce
  * different bytes for the same document and reject payloads that were genuine.
  */
 import { verifyAsync } from '@noble/ed25519';
@@ -22,9 +22,9 @@ export class SignatureVerifier {
   constructor(private readonly keys: Record<string, string>) {}
 
   /**
-   * True only for a genuine signature by the named pinned key. Every failure —
-   * unknown key, malformed base64, wrong length, bad signature — is a plain
-   * false, and callers then fall back to cache.
+   * True only for a genuine signature by the named pinned key. Every failure
+   * is a plain false: an unknown key, malformed base64, the wrong length, a
+   * bad signature. Callers then fall back to cache.
    */
   async verify(body: string, signature: string, keyId: string): Promise<boolean> {
     const encoded = this.keys[keyId];

test/client.test.ts

@@ -1,6 +1,6 @@
 /**
- * What the client promises when things go wrong — the only time anybody finds
- * out whether a config SDK was written carefully.
+ * What the client promises when things go wrong, which is the only time
+ * anybody finds out whether a config SDK was written carefully.
  *
  * These sign with a real key pair and stub `fetch`, so the verification path is
  * exercised for real. A verifier that is mocked in tests is a verifier nobody