diff --git a/content/why-bare-metal-debian-and-raspberry-pi-os-is-not-a-good-choice-for-most-embedded-systems.md b/content/why-bare-metal-debian-and-raspberry-pi-os-is-not-a-good-choice-for-most-embedded-systems.md
index 86ea102..507181b 100644
--- a/content/why-bare-metal-debian-and-raspberry-pi-os-is-not-a-good-choice-for-most-embedded-systems.md
+++ b/content/why-bare-metal-debian-and-raspberry-pi-os-is-not-a-good-choice-for-most-embedded-systems.md
@@ -36,7 +36,7 @@ Then you get your good revision and try to install/compile the new `x` package a
 An addend that I'd like to make here: don't use `snapshot.debian.org`. I see a lot of companies deploying devices pinned to a good, known revision of the Debian archive using the snapshot services, but they quickly find out it's rate limited for a reason.
 
 ### Maintaining a secure package feed is hard work
-I know because I maintain one. It's a lot of work, a lot of CI/CD pipelining and testing to make sure everything works. Debian stable is pretty stable, and generally stuff doesn't break, and I would know (I maintain feeds.toradex.com/debian and some others), but that's because we spent a lot of resources to test it everyday; it's simply not economical for most medium-scale projects to do the same. And you will naturally need a package feed to keep your own `.deb` artifacts stored.
+Mostly CI/CD pipelining for the package builds and testing to make sure everything is correct (automated testing at any larger scale, which gets expensive very fast). Debian stable is pretty stable, and generally stuff doesn't break - and I would know I maintain feeds.toradex.com/debian and some others -, but that's because we spend significant of resources to test it every day; it's simply not economical for most medium-scale projects to do the same. And you will naturally need a package feed to keep your own `.deb` artifacts stored, which is not as simple to setup as say, a Docker Registry, and for sure not as safe.
 
 ### Hardware support is not that great
 If you're not familiar with the hurdles the Asahi team is going on to upstream Apple Silicon support to the kernel, it's a lot. Now take that effort and multiply for each of the different SoC families, variations, embedded GPUs, NPUs, audio drivers, bluetooth and WiFi drivers: that's what you'll be dealing with if you're trying to run upstream Debian.