blog: nixos-upstreaming: clarify the nixos-unstable expectation

content/blog/nixos-upstreaming.md

@@ -174,6 +174,6 @@ if you're making changes in a hot area of the codebase, the diff from your PR (w
 
 i described here the workflow i found easiest to get started with. with something as configurable as nix, many people use many different workflows. some prefer maintaining their own long-running fork of nixpkgs wherein they cherry-pick all these PRs and periodically rebase against nixos-unstable (or a release branch), and point their flake directly at their fork of nixpkgs. your workflow will surely evolve as you settle in, but hopefully this gives you enough inspiration to get started :-)
 
-finally, don't be afraid to use the `nixos-unstable` branch if you're an intermediate nix user! it's really not as unstable as the name suggests. i experience maybe one package break per month across four deployments, almost always manifesting via a build failure and hence not causing any real trouble -- just a deferred update. that tiny inconvenience is worth it to have easier access to the more rapidly moving parts of nixpkgs.
+finally, don't be afraid to use the `nixos-unstable` branch if you're an intermediate user! it might not be quite as unstable as the name suggests: i've yet to encounter any show-stopping issues, 90% of the instability is just that packages don't build and need to be pinned or fixed (or you skip the update that day). there's a (relatively early) point where the minor inconvenience of nixos-unstable is less than the inconvenience of maintaining patches that have already landed upstream.
 
 as always, don't hesitate to [contact me](@/about.md) or reach out on the [forums/chat](https://nixos.org/community/).