Spelling

ponylang · Jan 30, 2024 · aa8ce36 · aa8ce36
1 parent 813fae8
commit aa8ce36
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 1 deletion.
diff --git a/.spelling-wordlist.txt b/.spelling-wordlist.txt
@@ -83,6 +83,7 @@ compositional
 conf
 COPR
 COVID
+Covo
 CPUs
 cquinn
 creational
@@ -187,6 +188,7 @@ Haxe
 HeapToStack
 HFPUG
 HighlightJS
+hoc
 homebrew
 Horwitz
 Horwitz's
@@ -408,6 +410,8 @@ RSS
 Rubyists
 runtime
 runtime's
+Sandro
+Sandro's
 scalable
 ScalaDays
 SDK

diff --git a/content/blog/last-week-in-pony-020424.md b/content/blog/last-week-in-pony-020424.md
@@ -35,7 +35,7 @@ Promises are great when the caller of your API needs an ad-hoc way to interact.
 
 If you don't need ad-hoc interaction, then Promises are not a good solution. That make the interactions between actors hard to follow. They obscure what is actually a fixed protocol. The [fork/join library](https://github.com/ponylang/fork_join) is an excellent one to study to learn more about the "fixed interaction" pattern that appears quite often in Pony programs.
 
-I recommend checking out how `[`_Coordinator`](https://github.com/ponylang/fork_join/blob/main/fork_join/_coordinator.pony), `CollectorRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/collector_runner.pony), [`Job`](https://github.com/ponylang/fork_join/blob/main/fork_join/job.pony), and [`WorkerRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/worker_runner.pony) communicate.
+I recommend checking out how [`_Coordinator`](https://github.com/ponylang/fork_join/blob/main/fork_join/_coordinator.pony), [`CollectorRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/collector_runner.pony), [`Job`](https://github.com/ponylang/fork_join/blob/main/fork_join/job.pony), and [`WorkerRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/worker_runner.pony) communicate.
 
 ## RFCs
-Original file line number
+Diff line change
@@ Expand Up @@
     If you don't need ad-hoc interaction, then Promises are not a good solution. That make the interactions between actors hard to follow. They obscure what is actually a fixed protocol. The [fork/join library](https://github.com/ponylang/fork_join) is an excellent one to study to learn more about the "fixed interaction" pattern that appears quite often in Pony programs.
-    I recommend checking out how `[`_Coordinator`](https://github.com/ponylang/fork_join/blob/main/fork_join/_coordinator.pony), `CollectorRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/collector_runner.pony), [`Job`](https://github.com/ponylang/fork_join/blob/main/fork_join/job.pony), and [`WorkerRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/worker_runner.pony) communicate.
+    I recommend checking out how [`_Coordinator`](https://github.com/ponylang/fork_join/blob/main/fork_join/_coordinator.pony), [`CollectorRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/collector_runner.pony), [`Job`](https://github.com/ponylang/fork_join/blob/main/fork_join/job.pony), and [`WorkerRunner`](https://github.com/ponylang/fork_join/blob/main/fork_join/worker_runner.pony) communicate.
     ## RFCs
@@ Expand Down @@