Update website

Author: mbloch

docs/examples/data/globe.msx

@@ -85,15 +85,15 @@ <h2 id="what-is-a-javascript-expression">What is a JavaScript expression?</h2>
   -each <span class="hljs-string">&#x27;SIZE = classify(POPULATION)&#x27;</span> \
   -o out.geojson
 </code></pre>
-<h2 id="quoting-expressions-in-the-shell">Quoting expressions in the shell</h2>
-<p>Expression arguments must be quoted in the shell. The most common style is single quotes, which prevent the shell from interpreting special characters inside the expression:</p>
+<h2 id="quoting-expressions">Quoting expressions</h2>
+<p>An expression containing spaces or special characters needs to be quoted, otherwise mapshaper will interpret the parts as separate arguments and produce a syntax error. Single quotes are the most common style:</p>
 <pre><code class="hljs language-bash">mapshaper data.geojson -filter <span class="hljs-string">&#x27;POPULATION &gt; 1000000&#x27;</span> -o out.geojson
 </code></pre>
 <p>If the expression itself contains single quotes — for example, a string literal — wrap it in double quotes instead, and vice versa:</p>
 <pre><code class="hljs language-bash">mapshaper data.geojson -filter <span class="hljs-string">&quot;TYPE == &#x27;inner&#x27;&quot;</span> -o out.geojson
 </code></pre>
 <p>Backtick quoting is also available as a third option when both single and double quotes appear in the expression.</p>
-<p>Backslash escapes (<code>\&quot;</code>, <code>\&#39;</code>) can also resolve quoting conflicts, but the shell processes them before passing the expression to mapshaper, which can strip the backslashes and produce a JS syntax error. This gets particularly confusing inside shell scripts and Makefiles, where an additional level of escaping may be needed. When possible, switching the outer quote style is simpler than relying on backslash escapes.</p>
+<p>Backslash escapes (<code>\&quot;</code>, <code>\&#39;</code>) can also resolve quoting conflicts, but when running commands in a shell the shell processes them before passing the expression to mapshaper, which can strip the backslashes and produce a JS syntax error. This gets particularly confusing inside shell scripts and Makefiles, where an additional level of escaping may be needed. When possible, switching the outer quote style is simpler than relying on backslash escapes.</p>
 <h2 id="where-expressions-appear">Where expressions appear</h2>
 <table>
 <thead>
@@ -636,7 +636,7 @@ <h2 id="see-also">See also</h2>
   </main>
 
   <aside class="docs-toc">
-    <div class="docs-toc-title">On this page</div><ul><li class="lvl-2"><a href="#what-is-a-javascript-expression">What is a JavaScript expression?</a></li><li class="lvl-2"><a href="#quoting-expressions-in-the-shell">Quoting expressions in the shell</a></li><li class="lvl-2"><a href="#where-expressions-appear">Where expressions appear</a></li><li class="lvl-2"><a href="#the-execution-context">The execution context</a></li><li class="lvl-3"><a href="#field-assignment">Field assignment</a></li><li class="lvl-3"><a href="#multiple-statements">Multiple statements</a></li><li class="lvl-2"><a href="#feature-properties-this">Feature properties (this)</a></li><li class="lvl-3"><a href="#all-layer-types">All layer types</a></li><li class="lvl-3"><a href="#polygon-polyline-and-point-layers-with-geometry">Polygon, polyline and point layers (with geometry)</a></li><li class="lvl-3"><a href="#polygon-only">Polygon-only</a></li><li class="lvl-3"><a href="#polyline-only">Polyline-only</a></li><li class="lvl-3"><a href="#point-only">Point-only</a></li><li class="lvl-2"><a href="#layer-level-properties-thislayer">Layer-level properties (this.layer)</a></li><li class="lvl-2"><a href="#helper-functions">Helper functions</a></li><li class="lvl-2"><a href="#calc-expressions">Calc expressions</a></li><li class="lvl-2"><a href="#pair-expressions-a-and-b">Pair expressions (A and B)</a></li><li class="lvl-2"><a href="#layer-level-expressions--if--define">Layer-level expressions (-if, -define)</a></li><li class="lvl-2"><a href="#template-expressions--run">Template expressions (-run)</a></li><li class="lvl-2"><a href="#loading-helpers">Loading helpers</a></li><li class="lvl-2"><a href="#sharing-state-across-commands">Sharing state across commands</a></li><li class="lvl-2"><a href="#common-pitfalls">Common pitfalls</a></li><li class="lvl-2"><a href="#examples">Examples</a></li><li class="lvl-2"><a href="#see-also">See also</a></li></ul>
+    <div class="docs-toc-title">On this page</div><ul><li class="lvl-2"><a href="#what-is-a-javascript-expression">What is a JavaScript expression?</a></li><li class="lvl-2"><a href="#quoting-expressions">Quoting expressions</a></li><li class="lvl-2"><a href="#where-expressions-appear">Where expressions appear</a></li><li class="lvl-2"><a href="#the-execution-context">The execution context</a></li><li class="lvl-3"><a href="#field-assignment">Field assignment</a></li><li class="lvl-3"><a href="#multiple-statements">Multiple statements</a></li><li class="lvl-2"><a href="#feature-properties-this">Feature properties (this)</a></li><li class="lvl-3"><a href="#all-layer-types">All layer types</a></li><li class="lvl-3"><a href="#polygon-polyline-and-point-layers-with-geometry">Polygon, polyline and point layers (with geometry)</a></li><li class="lvl-3"><a href="#polygon-only">Polygon-only</a></li><li class="lvl-3"><a href="#polyline-only">Polyline-only</a></li><li class="lvl-3"><a href="#point-only">Point-only</a></li><li class="lvl-2"><a href="#layer-level-properties-thislayer">Layer-level properties (this.layer)</a></li><li class="lvl-2"><a href="#helper-functions">Helper functions</a></li><li class="lvl-2"><a href="#calc-expressions">Calc expressions</a></li><li class="lvl-2"><a href="#pair-expressions-a-and-b">Pair expressions (A and B)</a></li><li class="lvl-2"><a href="#layer-level-expressions--if--define">Layer-level expressions (-if, -define)</a></li><li class="lvl-2"><a href="#template-expressions--run">Template expressions (-run)</a></li><li class="lvl-2"><a href="#loading-helpers">Loading helpers</a></li><li class="lvl-2"><a href="#sharing-state-across-commands">Sharing state across commands</a></li><li class="lvl-2"><a href="#common-pitfalls">Common pitfalls</a></li><li class="lvl-2"><a href="#examples">Examples</a></li><li class="lvl-2"><a href="#see-also">See also</a></li></ul>
   </aside>
 
 </div>

docs/examples/data/us-states.msx

@@ -77,9 +77,9 @@ mapshaper data.geojson \
   -o out.geojson
 ```
 
-## Quoting expressions in the shell
+## Quoting expressions
 
-Expression arguments must be quoted in the shell. The most common style is single quotes, which prevent the shell from interpreting special characters inside the expression:
+An expression containing spaces or special characters needs to be quoted, otherwise mapshaper will interpret the parts as separate arguments and produce a syntax error. Single quotes are the most common style:
 
 ```bash
 mapshaper data.geojson -filter 'POPULATION > 1000000' -o out.geojson
@@ -93,7 +93,7 @@ mapshaper data.geojson -filter "TYPE == 'inner'" -o out.geojson
 
 Backtick quoting is also available as a third option when both single and double quotes appear in the expression.
 
-Backslash escapes (`\"`, `\'`) can also resolve quoting conflicts, but the shell processes them before passing the expression to mapshaper, which can strip the backslashes and produce a JS syntax error. This gets particularly confusing inside shell scripts and Makefiles, where an additional level of escaping may be needed. When possible, switching the outer quote style is simpler than relying on backslash escapes.
+Backslash escapes (`\"`, `\'`) can also resolve quoting conflicts, but when running commands in a shell the shell processes them before passing the expression to mapshaper, which can strip the backslashes and produce a JS syntax error. This gets particularly confusing inside shell scripts and Makefiles, where an additional level of escaping may be needed. When possible, switching the outer quote style is simpler than relying on backslash escapes.
 
 ## Where expressions appear
 

docs/guides/expressions.html

@@ -2333,9 +2333,9 @@ mapshaper data.geojson \
   -o out.geojson
 ```
 
-## Quoting expressions in the shell
+## Quoting expressions
 
-Expression arguments must be quoted in the shell. The most common style is single quotes, which prevent the shell from interpreting special characters inside the expression:
+An expression containing spaces or special characters needs to be quoted, otherwise mapshaper will interpret the parts as separate arguments and produce a syntax error. Single quotes are the most common style:
 
 ```bash
 mapshaper data.geojson -filter 'POPULATION > 1000000' -o out.geojson
@@ -2349,7 +2349,7 @@ mapshaper data.geojson -filter "TYPE == 'inner'" -o out.geojson
 
 Backtick quoting is also available as a third option when both single and double quotes appear in the expression.
 
-Backslash escapes (`\"`, `\'`) can also resolve quoting conflicts, but the shell processes them before passing the expression to mapshaper, which can strip the backslashes and produce a JS syntax error. This gets particularly confusing inside shell scripts and Makefiles, where an additional level of escaping may be needed. When possible, switching the outer quote style is simpler than relying on backslash escapes.
+Backslash escapes (`\"`, `\'`) can also resolve quoting conflicts, but when running commands in a shell the shell processes them before passing the expression to mapshaper, which can strip the backslashes and produce a JS syntax error. This gets particularly confusing inside shell scripts and Makefiles, where an additional level of escaping may be needed. When possible, switching the outer quote style is simpler than relying on backslash escapes.
 
 ## Where expressions appear