diff --git a/meetings/notes/2024/2024-02-15.md b/meetings/notes/2024/2024-02-15.md
index 0d0aad9..3e42afd 100644
--- a/meetings/notes/2024/2024-02-15.md
+++ b/meetings/notes/2024/2024-02-15.md
@@ -41,7 +41,7 @@ SYG: I don't think I will convince you to change your philosophical viewpoint
 
 MM:
 
-- non-negotiable is to introduce conventional shared memory multithreading, fully exposing the hazards of that paradigm to the JS program, such that JS programs now have the burden of maintaing consistney and avoiding deadlock within that paradigm, which is inherently a cooperative path.  concurrent agents all need to cooperate to prevent invariants.  comm event loops is already the concurrency model, and that's where we should focus building on.
+- non-negotiable is to introduce conventional shared memory multithreading, fully exposing the hazards of that paradigm to the JS program, such that JS programs now have the burden of maintaining consistency and avoiding deadlock within that paradigm, which is inherently a cooperative path.  concurrent agents all need to cooperate to prevent invariants.  comm event loops is already the concurrency model, and that's where we should focus building on.
 - rust shows that it is possible to support an underlying implementation utilizing techniques of shared mem multi threading, unified type system, in a way that still enables fault containment against time+space
 - there are good rust compilers targeting WASM
 - for JS, infeasible by any known technique to bring in sound static typing, esp for anything as sophisticated a type system as reference capabilities