aboutsummaryrefslogtreecommitdiff
path: root/doc/arrayrepr.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2022-07-08 22:06:05 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2022-07-08 22:06:05 -0400
commit7fa325f583a59a1999cd8ce093a49f8048a3e05c (patch)
tree5157b1cbd4af6318eb77b3fcf5d80420d0cba46d /doc/arrayrepr.md
parent9ce4441a2fec2f6bd301f9cf5ad801c9534d34eb (diff)
Simplify and update Couple/Merge docs
Diffstat (limited to 'doc/arrayrepr.md')
-rw-r--r--doc/arrayrepr.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/arrayrepr.md b/doc/arrayrepr.md
index 63dba983..1047c187 100644
--- a/doc/arrayrepr.md
+++ b/doc/arrayrepr.md
@@ -123,7 +123,7 @@ BQN's separator rules give list notation a very flexible structure. You can put
#### High-rank arrays
-Higher-rank arrays can be written with `[]`, an **array notation** that indicates each element is to be used as a [cell](array.md#cells) of its result. It's identical to forming a list and applying [Merge](couple.md#merge-and-array-theory) (`[…]` is the same as `>⟨…⟩`).
+Higher-rank arrays can be written with `[]`, an **array notation** that indicates each element is to be used as a [cell](array.md#cells) of its result. It's identical to forming a list and applying [Merge](couple.md) (`[…]` is the same as `>⟨…⟩`).
[2‿3, 4‿1, 0‿5]