From f3bf27b20bcb04dd31cb275b43b9b2a32c14534c Mon Sep 17 00:00:00 2001
From: tslil clingman <>
Date: Thu, 22 Feb 2024 22:24:28 +0100
Subject: fix typos and small omissions

---
 log-240222-1.gmi | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/log-240222-1.gmi b/log-240222-1.gmi
index abb728d..d107300 100644
--- a/log-240222-1.gmi
+++ b/log-240222-1.gmi
@@ -1,4 +1,4 @@
-Time-stamp: <2024-02-22 19h21 UTC>
+Time-stamp: <2024-02-22 21h24 UTC>
 
 # Formatting strings with separators in BQN
 
@@ -68,7 +68,7 @@ which when applied dyadically, that is to two arguments, yields the arguably int
 
 BQN (and other languages) offer up an extension of this 3-train parsing rule: a 3-train may be preceded by a monadic function m and the resulting semantics are
 ```
-m f g h <===> k (f g h)                                                       ²
+m f g h <===> m (f g h)                                                       ²
 𝕨 (m f g h) 𝕩 <===> m(g(f(𝕨, 𝕩), h(𝕨, 𝕩)))
 ```
 
@@ -152,12 +152,12 @@ Here's the interesting part about about that monadic application: it's really a
 
 The crucial point here are the semantics of before (⊸):
 ```
+f⊸g 𝕩 <===> g(f(𝕩), 𝕩)
 𝕨 f⊸g 𝕩 <===> g(f(𝕨), 𝕩)
 ```
-Isn't that so cool!?
-
-Incidentally the dual of before is after (⟜):
+Isn't that so cool!? Incidentally the dual of before is after (⟜):
 ```
+g⟜f 𝕩 <===> g(𝕩, f(𝕩))
 𝕨 g⟜f 𝕩 <===> g(𝕨, f(𝕩))
 ```
 and the fun observation is that using both before and after coincides with 3-trains (almost)
-- 
cgit v1.3.1