aboutsummaryrefslogtreecommitdiff
path: root/doc/transpose.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2020-09-05 12:56:39 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2020-09-05 12:56:39 -0400
commit6408f52bdb80b0b79191675481bf59739ec3ad5b (patch)
tree2c9895bd1d9def10c7cf7b05b1c7d357fbf2c849 /doc/transpose.md
parent053d9b3038977db5cbf1921a144366ebaf774cfe (diff)
Prefer ˙ to ˜ for constant functions
Diffstat (limited to 'doc/transpose.md')
-rw-r--r--doc/transpose.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/transpose.md b/doc/transpose.md
index ae72d889..1a870347 100644
--- a/doc/transpose.md
+++ b/doc/transpose.md
@@ -68,13 +68,13 @@ In particular, the case with only one argument specified is interesting. Here, t
≢ 2 ⍉ a23456 # Restrict Transpose to the first three axes
-Finally, it's worth noting that, as monadic Transpose moves the first axis to the end, it's equivalent to dyadic Transpose with a "default" left argument: `(=-1˜)⊸⍉`.
+Finally, it's worth noting that, as monadic Transpose moves the first axis to the end, it's equivalent to dyadic Transpose with a "default" left argument: `(=-1˙)⊸⍉`.
## Definitions
Here we define the two valences of Transpose more precisely.
-Monadic transpose is identical to `(=-1˜)⊸⍉`, except that for scalar arguments (including atoms) it returns the array unchanged rather than giving an error.
+Monadic transpose is identical to `(=-1˙)⊸⍉`, except that for scalar arguments (including atoms) it returns the array unchanged rather than giving an error.
An atom right argument to dyadic Transpose is always enclosed to get a scalar array before doing anything else.