fix spelling (#132)

Author: swapdisk

2021_06_07.md

@@ -74,7 +74,7 @@ Some of the topics we hit on, in the order that we hit them:
     [Flash Storage Today](https://queue.acm.org/detail.cfm?id=1413262),
     [History of SSDs](http://dtrace.org/blogs/ahl/2010/08/17/fishworks_ssds/)
     blog entry mentioning sTec and Gnutek
-  - sTec [aquires Gnutek Ltd][gnutek]
+  - sTec [acquires Gnutek Ltd][gnutek]
   - The SEC's [complaint][sec stec] against
     Manouchehr Moshayedi of [sTec](https://en.wikipedia.org/wiki/STec,_Inc.)
   - [Channel stuffing](https://en.wikipedia.org/wiki/Channel_stuffing)

2021_08_16.md

@@ -141,7 +141,7 @@ Some of the topics we hit on, in the order that we hit them:
 
   > I think there needs to be a greater literature of software:
   > the making of it, its purpose, its vulnerabilities, its values.
-  - Tom: It's because us practitioners are too embarrased about it all..
+  - Tom: It's because us practitioners are too embarrassed about it all..
 - [@1:05:49](https://youtu.be/hlQuF75L4TE?t=3949) Josh compares and contrasts.
   > Coders don't have to test their own stuff. The second stringers do that.
   - Pascal: I would encourage people to write more about software

2021_10_18.md

@@ -62,7 +62,7 @@ Some of the topics we hit on, in the order that we hit them:
   - Languages have different audiences
 - [@27:18](https://youtu.be/D-Uzo7M-ioQ?t=1638) Human languages
   - The [Esperanto](https://en.wikipedia.org/wiki/Esperanto) con-lang
-  - [Tonal langages](https://en.wikipedia.org/wiki/Tone_(linguistics))
+  - [Tonal languages](https://en.wikipedia.org/wiki/Tone_(linguistics))
 - Learning new and different programming languages
 - [@37:06](https://youtu.be/D-Uzo7M-ioQ?t=2226) Adam's early JavaScript
   ([tweet](https://twitter.com/ahl/status/1450268016650842113))
@@ -74,7 +74,7 @@ Some of the topics we hit on, in the order that we hit them:
     - Rigid advice on how to learn
   - [ALGOL 68](https://en.wikipedia.org/wiki/ALGOL_68), planned successor
     to [ALGOL 60](https://en.wikipedia.org/wiki/ALGOL_60)
-    - ALGOL 60, was, according to [Tony Hoare](https://en.wikipedia.org/wiki/Tony_Hoare), "[An improvment on nearly all of its successors](http://web.eecs.umich.edu/~bchandra/courses/papers/Hoare_Hints.pdf)"
+    - ALGOL 60, was, according to [Tony Hoare](https://en.wikipedia.org/wiki/Tony_Hoare), "[An improvement on nearly all of its successors](http://web.eecs.umich.edu/~bchandra/courses/papers/Hoare_Hints.pdf)"
 - [@50:41](https://youtu.be/D-Uzo7M-ioQ?t=3041)
   Where does Rust belong in the progression of languages someone learns?
   > Rust is what happens when you've got 25 years of experience with C++,

2022_02_14.md

@@ -45,7 +45,7 @@ Some of the topics we hit on, in the order that we hit them:
   - Bryan's Papers We Love talk on Jails and Zones
     [video](https://youtu.be/hgN8pCMLI2U) ~100mins
   - 1963 Honeywell H200 [wiki](https://en.wikipedia.org/wiki/Honeywell_200)
-  - Bryan on harware virtualization history
+  - Bryan on hardware virtualization history
     [video](https://youtu.be/jEHO-bSbuc0?t=322) ~10mins,
     also [here](https://youtu.be/fcrepNIF_G0?t=511)
 - [@37:22](https://youtu.be/MyGgkBxz-mg?t=2242) The Greate Stirrup Controversy

2022_03_07.md

@@ -50,7 +50,7 @@ Some of the topics we hit on, in the order that we hit them:
   - Requests for discussion, as decision making tools
 - [@1:02:29](https://youtu.be/GTluipbKeII?t=3749)
   Jason: service delivery vs product delivery
-  - Class devision between "the desked" and "the un-desked"
+  - Class division between "the desked" and "the un-desked"
 - [@1:07:17](https://youtu.be/GTluipbKeII?t=4037)
   Is "back to office" about command and control?
   - Other factors: big tech companies receive substantial local subsidies

2022_04_18.md

@@ -56,7 +56,7 @@ Some of the topics we hit on, in the order that we hit them:
 - [@52:12](https://youtu.be/HCkuCkp3Zoo?t=3132)
   *Matt talks about the second, "lesser" network switch on the Sidecar board*
 - [@57:28](https://youtu.be/HCkuCkp3Zoo?t=3448)
-  *Secret 8051 cores, slew-rate woes: impedance missmatch on SPI traces that manifested in unreliable communication in full bandwidth mode of the SPI/GPIO driver*
+  *Secret 8051 cores, slew-rate woes: impedance mismatch on SPI traces that manifested in unreliable communication in full bandwidth mode of the SPI/GPIO driver*
 - [@1:03:19](https://youtu.be/HCkuCkp3Zoo?t=3799)
   *PLL config issues and Matt's verbose config tool to fix them*
 - [@1:04:26](https://youtu.be/HCkuCkp3Zoo?t=3866)

2022_07_18.md

@@ -81,7 +81,7 @@ Some of the topics we hit on, in the order that we hit them:
   + crossing the chasm moment - release of [The Rust Programming Language](https://doc.rust-lang.org/book/) and [Programming Rust](https://www.oreilly.com/library/view/programming-rust-2nd/9781492052586/) as physical books.
   + [Rust for Rustaceans](https://nostarch.com/rust-rustaceans)
   + Rust programmers go through stages: fighting the borrow checker, then crates are cool - use them everywhere, then a year later you can start to right idiomatic code
-  + smal QoL feature: [cargo add](https://doc.rust-lang.org/cargo/commands/cargo-add.html)
+  + small QoL feature: [cargo add](https://doc.rust-lang.org/cargo/commands/cargo-add.html)
   + Also: [links in rustdoc](https://doc.rust-lang.org/rustdoc/write-documentation/linking-to-items-by-name.html)
 
 If we got something wrong or missed something, please file a PR!

2022_09_26.md

@@ -21,7 +21,7 @@ Some of the topics we hit on, in the order that we hit them:
   *The aha moment for BBM*
 - [@09:42](https://youtu.be/68TVcHeBsBU?t=582)
   *Ruffled feathers from partner interactions*
-  + Bell South thought they had an exlusive deal and they didn't
+  + Bell South thought they had an exclusive deal and they didn't
   + Years later, people didn't seem to hold it against them
 - [@12:40](https://youtu.be/68TVcHeBsBU?t=760)
   *Brian's anecdote about a meeting with Balsillie and Lazaridis*

2022_10_27_special.md

@@ -54,7 +54,7 @@ Some of the topics we hit on, in the order that we hit them:
 - [@37:45](https://youtu.be/RhXYXtyPz3Y?t=2265)
   *Predictions*
 - Lots of strategies around reductions in force
-- Embarassing outage
+- Embarrassing outage
 - Shitty advertising
 - [Fedaverse and Mastadon](https://en.wikipedia.org/wiki/Fediverse)
 - Smaller communities like Discord or Matrix
@@ -71,7 +71,7 @@ Some of the topics we hit on, in the order that we hit them:
 - Every new feature got scrutiny with the question "Hey, could this be used to start a genocide?"
 - Humility was pushed down from the top
 - GDPR threw a big wrench into the systems designed to never lose data
-- Lots of work needed for essentially tech debt made iteration of product slow.  Speed increases in releses isn't necessarily related to Elon's arrival.
+- Lots of work needed for essentially tech debt made iteration of product slow.  Speed increases in releases isn't necessarily related to Elon's arrival.
 
 If we got something wrong or missed something, please file a PR!
 Our next Twitter space will likely be on Monday at 5p Pacific Time; stay tuned

2022_10_31.md

@@ -30,7 +30,7 @@ Some of the topics we hit on, in the order that we hit them:
 - [Bloomberg Super Micro story](https://www.datacenterdynamics.com/en/news/years-later-bloomberg-doubles-down-disputed-supermicro-supply-chain-hack-story/)
 - [Trammel Hudson's 'Modchips of the state' talk](https://trmm.net/Modchips/)
 - [Spectre and Meltdown](https://meltdownattack.com/)
-- Nested compoments and hidden cores and firmware hiding everywhere
+- Nested components and hidden cores and firmware hiding everywhere
 - [SOCs, systems on a chip](https://en.wikipedia.org/wiki/System_on_a_chip)
 - [@29:30](https://youtu.be/QAhHkz76NbI?t=1770)
   *OSFF*

2023_01_09.md

@@ -30,7 +30,7 @@ Tech companies unionizing become mainstream
 </td>
 <td>
 HPE acquired... (by HP?)<br>
-general pupose, open source filesystem based on FDP (flexible data placement)
+general purpose, open source filesystem based on FDP (flexible data placement)
 </td>
 <td>
 Heterogeneous cores / same ISA all on the same die for server CPUs e.g. for various power efficiency profiles.
@@ -101,7 +101,7 @@ Microsoft will have replaced the legacy Office suite with Electron versions base
 </td>
 
 <td>
-The mainstream desktop operating system from Microsoft will hvae become something resembling ChromeOS but based on Edge and bundles Electron-style Office apps and a VDI client tied to Azure capable of streaming legacy win32 apps -- but is still called Windows. "Windows Azure Cloud Desktop" or something. Windows Classic (NT) as we currently know it is primarily sold by Microsoft as a web service in Azure Desktop to run legacy enterprise apps. Microsoft will no longer sell you Exchange or other Office servers for on-prem. You must run the Azure service. Microsoft has announced that in future only special Enterprise SKUs of Windows client will be available to run on-prem and only in a VM. A bespoke Crostini-style Linux environment -- possibly still Subsystem for Linux -- is available but not the "happy path".
+The mainstream desktop operating system from Microsoft will have become something resembling ChromeOS but based on Edge and bundles Electron-style Office apps and a VDI client tied to Azure capable of streaming legacy win32 apps -- but is still called Windows. "Windows Azure Cloud Desktop" or something. Windows Classic (NT) as we currently know it is primarily sold by Microsoft as a web service in Azure Desktop to run legacy enterprise apps. Microsoft will no longer sell you Exchange or other Office servers for on-prem. You must run the Azure service. Microsoft has announced that in future only special Enterprise SKUs of Windows client will be available to run on-prem and only in a VM. A bespoke Crostini-style Linux environment -- possibly still Subsystem for Linux -- is available but not the "happy path".
 </td>
 
 <tr>

2023_02_13.md

@@ -33,7 +33,7 @@ Some of the topics we hit on, in the order that we hit them (experiment in turni
 - **Saethlin:** Wake up babe, new 0xide reading assignment dropped
 - **AaronW:** Labelled like a can of pringles --  "20% more malloc() free()!"
 - **Nahum:** Relevant to rules based accounting: https://www.schneier.com/blog/archives/2023/02/hacking-the-tax-code.html
-- **drew:** Rigorous definitions of “unsafe code” just wont cut it ig
+- **drew:** Rigorous definitions of “unsafe code” just won't cut it ig
 - **ig:** 40% less direct pointer arithmetic than the leading brand of operating systems
 - **a172:** How does principle based accounting even work? Like, how do you define if something violates the principle or not, without just turning it back into rules based?
 - **Eden:** Checkboxes are meaningful for operational checklists. Aviation and medicine use them pretty heavily. Not so meaningful for systemic work like developing a new aircraft or a new surgery.

2023_02_27.md

@@ -97,7 +97,7 @@ https://www.cs.princeton.edu/courses/archive/fall05/cos518/papers/dtrace.pdf
 - **levon** I know someone who basically polled all of the switches for buffer drops in an attempt to divine which paths were dropping packets due to micro-congestion
 - **admchl** I feel like I'm in a secret society meeting learning The Hidden Truth behind Reality of The Network
 - **wmf** I would argue if the entire hypervisor is on the smart NIC then you're no worse off than the Oxide architecture
-- **a172** I once stumbled on a bug where the vendor's custom protocol for monitoring (because snmp/syslog just cant keep up) had a trace log on the process, that could not be turned off. Some sort of race condition enabled it, and it happened on 1/3 of system boots. It was ~20k logs/s, iirc.
+- **a172** I once stumbled on a bug where the vendor's custom protocol for monitoring (because snmp/syslog just can't keep up) had a trace log on the process, that could not be turned off. Some sort of race condition enabled it, and it happened on 1/3 of system boots. It was ~20k logs/s, iirc.
 - **a172** (im going to look up those numbers)
 - **levon** I haven't worked with a SmartNIC fast enough to do this well
 - **JustinAzoff** We use a FPGA Nic in our products for fast packet capturing. the service that bootstraps it had an issue that caused it to log an error... for every single packet...

2023_03_20.md

@@ -330,9 +330,9 @@ sudo dd if=/dev/mem of=memory_dump.bin bs=1M
 - **juansebastianl**: I would be really surprised if there isn't already a basic thing like this in ChatGPT https://arxiv.org/abs/2301.10226
 - **Wizord**: the thought of outsourcing my thinking to Microsoft *terrifies* me beyond your imagination
 - **Johann-Tobias Schäg**: This has to be a post processing step. AFAIK you can not really embed it into the weights.
-- **juansebastianl**: Thats true, but no one has the weights except OpenAI
+- **juansebastianl**: That's true, but no one has the weights except OpenAI
 - **AaronW**: Related: https://twitter.com/as_w/status/541075012619231232
-- **Johann-Tobias Schäg**: Watermarks allow to detect set membership without needing acces to the cache
+- **Johann-Tobias Schäg**: Watermarks allow to detect set membership without needing access to the cache
 - **Johann-Tobias Schäg**: You can't embed it in the weights. Like math will explode when you do that.
 - **juansebastianl**: Yes, I understand lol but you can do it behind the API
 - **perplexes**: Gpt is my better Google basically
@@ -374,11 +374,11 @@ sudo dd if=/dev/mem of=memory_dump.bin bs=1M
 (ChatGPT4)
 > In the context of information theory, an LLM can be described as an efficient predictor or estimator of the probability distribution of the next token (e.g., word or character) in a sequence, given the previous tokens. By doing so, the model effectively compresses the information contained in the training data, allowing it to generate coherent and contextually relevant text based on the learned patterns.
 
-- **chadbrewbaker**: Hmm. This leads me to think that LLMs are monoids. You can efficently split the evaluation at scale and compose.
+- **chadbrewbaker**: Hmm. This leads me to think that LLMs are monoids. You can efficiently split the evaluation at scale and compose.
 - **Johann-Tobias Schäg**: It can be done in the post processing step because there we have access to a likelihood distribution of tokens and we could perturb the tie breaking according to some hypersubspace which would serve as statistical proof over many tokens.
 - **Johann-Tobias Schäg**: There are probably other approaches but doing it on the generated text least disturbs the model
 - **chadbrewbaker**: Can you use a random source to tweak the probability distribution of the next token for parallel search?
-- **chadbrewbaker**: They call this timescale parallelization in molecular dynamics - you apply some slight noice to all molecules then run the simulation in parallel until one of the models hits your desired phase change condition.
+- **chadbrewbaker**: They call this timescale parallelization in molecular dynamics - you apply some slight noise to all molecules then run the simulation in parallel until one of the models hits your desired phase change condition.
 - **juansebastianl**: I think what I'm saying is best illustrated by a kind of silly example. Suppose that I wanted to set up a pre-processing watermarking. So suppose I have an existing word embedding from an unwatermaked model. You can create a new corpus of "watermarked" training examples where you sub in nearest "allowable" tokens for all the "disallowed" ones then train your model only on the "allowable" corpus and only with "allowable" tokens as inputs and outputs. Then at inference time you have to repeat this step for new text but you still end up with the statistical properties of an include/exclude list on text you're trying to determine the provenance of. Of course such a model would be _terrible_ for a bunch of reasons, I'm simply saying it's possible.
 
 

2023_03_27.md

@@ -35,7 +35,7 @@ The (lightly) edited live chat from the show:
 - **uwaces**: Elm has a very similar model. They have even had a debugger that let you run events in reverse: https://elm-lang.org/news/time-travel-made-easy
 - **bch**: I’m joining late - 1) does this state-machine replay model have a name 2) expand on (describe ) the I/o logic separation distinction?
 - **ahl**: http://dtrace.org/blogs/ahl/2015/06/22/first-rust-program-pain/
-- **zk**: RE: logic separation in consensus protocols: the benefit of seperating out the state machine into a side-effect free function allows you to write a formally verified implementation in a pure FP lang or theorem prover, and then extract a reference program from the proof.
+- **zk**: RE: logic separation in consensus protocols: the benefit of separating out the state machine into a side-effect free function allows you to write a formally verified implementation in a pure FP lang or theorem prover, and then extract a reference program from the proof.
 - **we're going to the zoo**: lol i’m a web dev && we do UI tests via StorybookJS + snapshots of each story + snapshots of the end state of an interaction
 - **ig**: At that point you could turn the recording into an “expect test”. https://blog.janestreet.com/the-joy-of-expect-tests/
 - **we're going to the zoo**: TOFU but for tests 🥰
@@ -101,10 +101,10 @@ The (lightly) edited live chat from the show:
 - **ig**: Most DBs have a commit log, most don’t expose it externally. Event sourcing reimplements a lot of what’s in the commit log.
 - **nickik**: Maybe more practical then full datomic, datascript (https://github.com/tonsky/datascript) is datomic in a browser. Good store for React applications to build on.
 - **nickik**: Eventsourcing can scale to much larger size then you can handle with one Datomic style DB. But unless you really need it, its kind of a pain.
-- **endigma**: is there anything preventing implementing it as a data structure ontop of a more conventional db?
+- **endigma**: is there anything preventing implementing it as a data structure on top of a more conventional db?
 - **nickik**: Datomic allows you to add arbitrary data to your transactional log, so for example you can attach to a transaction that it was done by user-x, threw api versions 2.2 and so on. That quite neat.
 - **nickik**: That's exactly what datomic does, its designed to be read-scalable on big key value stores, but it works fine on SQL Databases!  See: https://docs.datomic.com/on-prem/overview/storage.html
-- **endigma**: oh thats pretty cool, i suppose the datom model would work well with hyperscale k/v
+- **endigma**: oh that's pretty cool, i suppose the datom model would work well with hyperscale k/v
 - **endigma**: from what i'm reading datoms are a sort of tuple though, k/v doesn't normally index by more than one k
 - **endigma**: i wonder how batching lookups works to get the k/v of a particular entity
 - **endigma**: or if they all just happen separately and its optimized for that
@@ -115,7 +115,7 @@ The (lightly) edited live chat from the show:
 - **endigma**: Sure, so more similar to the goal of fuzz tests than unit tests.
 - **we're going to the zoo**: https://www.bjaress.com/posts/2021-07-03-fuzz-testing-vs-property-based-testing.html a reasonable approach will use both a naive and structured generative test
 - **we're going to the zoo**: a fuzz test is just a property test that claims “for any possible input, the program should only output the types i expect / a known exception”
-- **endigma**: if thats correct it makes a lot of sense why you might want to make a framework to write these sort of assumptions, perhaps something like go-testdeep
+- **endigma**: if that's correct it makes a lot of sense why you might want to make a framework to write these sort of assumptions, perhaps something like go-testdeep
 - **endigma**: (sort of)
 - **endigma**: https://earthly.dev/blog/property-based-testing/
 

2023_05_01.md

@@ -27,7 +27,7 @@ Some of the topics we hit on, in the order that we hit them:
 - Bluesky blog [Composable Moderation](https://blueskyweb.xyz/blog/4-13-2023-moderation)
 - [Lobsters](https://lobste.rs/)
 - [Phanpy](https://phanpy.social/)
-- [So you've been publically shamed by Jon Ronson](https://en.wikipedia.org/wiki/So_You%27ve_Been_Publicly_Shamed)
+- [So you've been publicly shamed by Jon Ronson](https://en.wikipedia.org/wiki/So_You%27ve_Been_Publicly_Shamed)
 
 If we got something wrong or missed something, please file a PR!
 Our next show will likely be on Monday at 5p Pacific Time on our Discord