diff --git a/data/blog/efficient-nix-derivations-with-file-sets.md b/data/blog/efficient-nix-derivations-with-file-sets.md
index c9e5840..56c41c0 100644
--- a/data/blog/efficient-nix-derivations-with-file-sets.md
+++ b/data/blog/efficient-nix-derivations-with-file-sets.md
@@ -70,7 +70,7 @@ Now with this setup, we have a "base" file set of `[ ./Makefile ./src ]` then wi
 ## A Real Example
 
 Recently I started messing around with the language [Roc](https://www.roc-lang.org/). If you haven't heard of it, Roc is a new functional language heavily inspired by Elm.
-It's fast but also very nice to use (though many rough edges since it's pre-0.1.0).
+It's fast but also very nice to use (though some rough edges since it's pre-0.1.0).
 
 One of its interesting ideas is that Roc needs your app to pick what [platform](https://www.roc-lang.org/platforms) to run on.
 A platform would be written in something like rust, zig, c, etc.
@@ -79,6 +79,7 @@ Right now the two most widely used are a [cli platform](https://github.com/roc-l
 
 This is really neat but brings an issue for developing a platform along with the roc code needed to define the platform API.
 You need to compile the "platform code" (ie rust + some c), do w/e linking is needed for that, then distribute that with the roc source code.
+The roc cli will do this for you when developing but it doesn't work as nicely for a build with nix.
 
 For example, [this](https://github.com/roc-lang/roc/tree/main/examples/platform-switching/rust-platform) is one of the sample platforms