aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEuAndreh <eu@euandre.org>2020-10-20 08:21:50 -0300
committerEuAndreh <eu@euandre.org>2020-10-20 08:21:50 -0300
commitcd53902956e419ea05c678b51557df5a24822f54 (patch)
treeda8659e605e7fc117580e38cb8c4063fbc358c67
parentswift2nix article: typo by reader (diff)
downloadeuandre.org-cd53902956e419ea05c678b51557df5a24822f54.tar.gz
euandre.org-cd53902956e419ea05c678b51557df5a24822f54.tar.xz
s/instrinsic/intrinsic/
-rw-r--r--_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md b/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md
index 7b7570f..7b6e462 100644
--- a/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md
+++ b/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md
@@ -76,7 +76,7 @@ Package managers want to do too much, or assume too much, or just want to take
control of the entire build of the dependencies.
This is a recurrent problem in package managers, but I don't see it as an
-instrinsic one. There's nothing about a "package manager" that prevents it from
+intrinsic one. There's nothing about a "package manager" that prevents it from
*declaring* what it expects to encounter and in which format. The *declaring*
part is important: it should be data, not code, otherwise you're back in the
same problem, just like lockfiles are just data. Those work in any language, and