Section on why BQN rejects stranding with spaces

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/index.html b/docs/index.html
index 40f5450a..3105e115 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -36,7 +36,7 @@
 </ul>
 <p>But BQN is redesigned from the ground up, with brand new ideas to make these paradigms easier to use and less likely to fail.</p>
 <ul>
-<li>The <a href="doc/based.html"><strong>based array model</strong></a> eliminates the surprise of floating arrays and the hassle of explicit boxes, while dedicated <a href="doc/arrayrepr.html#list-literals"><strong>list notation</strong></a> does away with <a href="https://aplwiki.com/wiki/Strand_notation">stranding</a> gotchas.</li>
+<li>The <a href="doc/based.html"><strong>based array model</strong></a> eliminates the surprise of floating arrays and the hassle of explicit boxes, while dedicated <a href="doc/arrayrepr.html#list-literals"><strong>list notation</strong></a> does away with the <a href="doc/arrayrepr.html#why-not-whitespace">gotchas</a> of <a href="https://aplwiki.com/wiki/Strand_notation">stranding</a>.</li>
 <li><a href="doc/context.html"><strong>Context-free grammar</strong></a> makes it easier for machines and humans to understand code, and naturally leads to <a href="doc/functional.html"><strong>first-class functions</strong></a>, which can even be used to <a href="doc/control.html">reinvent control structures</a>.</li>
 <li><a href="keymap.html"><strong>New symbols</strong></a> for built-in functionality make the syntactic role of every primitive instantly visible, and aim to be more consistent and intuitive.</li>
 <li>No-nonsense <a href="doc/namespace.html"><strong>namespace syntax</strong></a> encapsulates data and even allows for a little <a href="doc/oop.html">object-oriented programming</a>.</li>