website: remove unearned totality quantifiers

Phrases such as fills every control, holding everything a run needs, and downloads all of the input layers assert completeness where the plain statement carries the meaning, and control itself was a thesaurus substitution left over from removing dial. The quantifiers that state real rules stay: a cell builds only if every check passes, and a centre seeds beyond a walk of every existing centre.

Author: songololo

website/src/pages/index.astro

@@ -69,7 +69,7 @@ const dg = (name: string) => `${base}images/${name}.svg`
     <p>
       This page explains the model, using one real town throughout. To install the plugin and
       run it yourself, the <a href={`${base}plugin/`}>plugin guide</a> covers installation, a first-run
-      walkthrough, every dialog control, the outputs and troubleshooting. Ready-made places to start
+      walkthrough, the run dialog, the outputs and troubleshooting. Ready-made places to start
       from, with data and parameters prepared, are in the
       <a href={`${base}scenarios/`}>scenario library</a>.
     </p>
@@ -78,7 +78,7 @@ const dg = (name: string) => `${base}images/${name}.svg`
   <h2 id="inputs">Step 1: Download the data</h2>
   <section>
     <p>
-      A companion <strong>Extract from OpenStreetMap</strong> tool downloads all of the input layers for an
+      A companion <strong>Extract from OpenStreetMap</strong> tool downloads the input layers for an
       area of interest, so no manual data preparation is needed. The downloaded layers are ordinary editable
       layers, though: you can adjust them before running a simulation, or use your own layers instead. The
       panels below are <strong>the downloaded layers</strong> for a 4.2 km window around Cambourne, fetched
@@ -196,7 +196,7 @@ const dg = (name: string) => `${base}images/${name}.svg`
     <p>
       A single run is one plausible outcome; a different random seed gives a different, equally valid
       layout. So the plugin runs an <strong>ensemble</strong> and does two things with it. First, it blends
-      every run into a development-<strong>likelihood</strong> map, the real probabilities over Cambourne,
+      the runs into a development-<strong>likelihood</strong> map, the real probabilities over Cambourne,
       from twenty-four runs.
     </p>
     <figure>
@@ -240,7 +240,7 @@ const dg = (name: string) => `${base}images/${name}.svg`
     </figure>
     <p>
       Either can be compared against the raw grown state at the end of <a href="#simulation">step 3</a>. The
-      raw state is always saved alongside, so everything post-processing did stays visible.
+      raw state is always saved alongside, so the effect of post-processing stays visible.
     </p>
   </section>
 

website/src/pages/plugin.md

@@ -5,8 +5,8 @@ title: Plugin guide
 
 # Plugin guide
 
-This page covers installation, a first run, the data downloader, every dialog control, the
-outputs, and troubleshooting. The [introduction](./) explains the model itself, and the
+This page covers installation, a first run, the data downloader, the run dialog, the outputs,
+and troubleshooting. The [introduction](./) explains the model itself, and the
 [scenario library](./scenarios/) provides prepared data and parameters to start from.
 
 ## Install
@@ -58,14 +58,14 @@ To start from a prepared case instead, use a scenario download, described in the
 
 <h2 id="use-a-scenario">Using a downloaded scenario</h2>
 
-Each entry in the [scenario library](./scenarios/) downloads as one ZIP holding everything a run
-needs.
+Each entry in the [scenario library](./scenarios/) downloads as one ZIP with the data and
+parameters for a run.
 
 - **Contents**: `extents*.geojson` (the study boundary), the input layers (`built`, `green`,
   `centres`, `unbuildable`, `streets`, `stops`, `stations`), the terrain bands
   (`steep.geojson`), and one or more `params*.json` presets.
 - **Layers**: drag the GeoJSON files onto the QGIS map.
-- **Local adjustment**: every layer is ordinary editable data, and the scenarios are prepared
+- **Local adjustment**: the layers are ordinary editable data, and the scenarios are prepared
   on the assumption that they will be revised. The built fabric, the extents, the green areas
   and the unbuildable land can each be corrected wherever local knowledge or stakeholder
   feedback improves on the downloaded state.
@@ -76,7 +76,7 @@ needs.
   GLO-30 elevation model. The bands at or above the scenario's maximum slope belong in the
   unbuildable layer (*Vector → Data Management Tools → Merge Vector Layers*).
 - **Parameters**: in **Isobenefit Urbanism**, *Load parameters* with the scenario's
-  `params.json` fills every control. Dnipro provides one preset per pilot area.
+  `params.json` fills in the dialog. Dnipro provides one preset per pilot area.
 - **Running**: select the layers in the *Input layers* group, confirm the suggested CRS,
   choose an output folder and run name, and press **Run**.
 - **Reproducing a published panel**: the explorer's per-run parameter files carry the exact
@@ -100,7 +100,7 @@ layers and pre-selects them.
 
 ## The run dialog, group by group
 
-**Parameters.** *Load parameters* repopulates every control from a previous run's
+**Parameters.** *Load parameters* repopulates the dialog from a previous run's
 `*_params.json` sidecar or from a scenario preset. Every run writes such a sidecar next to its
 output.