summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--CNAME1
-rw-r--r--ctf/index.md2
-rw-r--r--math/algebra.md2
-rw-r--r--plt/lambda-calculus.md2
-rw-r--r--tech/transit.md2
5 files changed, 4 insertions, 5 deletions
diff --git a/CNAME b/CNAME
deleted file mode 100644
index 1f67ba3..0000000
--- a/CNAME
+++ /dev/null
@@ -1 +0,0 @@
-wiki.toki.la \ No newline at end of file
diff --git a/ctf/index.md b/ctf/index.md
index 511a415..c7ca7e2 100644
--- a/ctf/index.md
+++ b/ctf/index.md
@@ -1,6 +1,6 @@
---
layout: ctf
-title: ctf
+title: capture the flag
---
<br>
diff --git a/math/algebra.md b/math/algebra.md
index 3717445..7697347 100644
--- a/math/algebra.md
+++ b/math/algebra.md
@@ -29,7 +29,7 @@ A [**ring**](ring-theory) $R$ is a set with two binary operations $+$ and $×$ s
- $(R, ×)$ is a *monoid*
- associativity: $∀a,b,c : (a×b)×c = a×(b×c)$
- multiplicative identity: $∃1, ∀a : 1×a = a×1 = a$
-- The *distributive laws* hold for + and ×:
+- The *distributive laws* hold for $+$ and $×$:
- $∀a,b,c : (a+b) × c = (a×c)+(b×c)$
- $∀a,b,c : a × (b+c) = (a×b) + (a×c)$
- An Abelian or **commutative ring** satisfies an additional axiom:
diff --git a/plt/lambda-calculus.md b/plt/lambda-calculus.md
index 7d15dbf..beb389c 100644
--- a/plt/lambda-calculus.md
+++ b/plt/lambda-calculus.md
@@ -7,7 +7,7 @@ title: computation/lambda calculus
the lambda calculus is a simple expression of computation.
-```racket
+```scheme
;; A full implementation of the untyped lambda calculus in Racket.
(define (interpret expr [ctx #hash()])
(match expr
diff --git a/tech/transit.md b/tech/transit.md
index ae21bd9..93f1d49 100644
--- a/tech/transit.md
+++ b/tech/transit.md
@@ -5,7 +5,7 @@ title: tech/transit
# Transportation Routing
-The state of transit software, particularly open-source transit software, is *atrocious*. It is a mess of mostly scattered, abandoned, half-completed projects. This is extremely weird, because a lot of people into open source are also into transit: so maybe transit apps are just hard to write and thankless to maintain? In any case, it is a bummer.
+The state of transit software, particularly open-source transit software, is *atrocious*. It is a mess of mostly scattered, abandoned, half-completed projects. This is extremely weird, because a lot of people into open source are also into transit! So maybe transit apps are just hard to write and thankless to maintain? In any case, it is a bummer.
I've collected some notes on transit information sources and transit data, for anyone looking to find a decent transit app, or looking to build one themselves. This does not include projects that I consider dead (no activity in ~2 years: API churn means these will almost certainly not function) or too specific (tooling for making maps, region-specific transit apps, etc). If you're reading this and notice any major omissions - of which there certainly are - feel free to shoot me an email.