cargo2nix post: Proofread again

1 files changed, 6 insertions, 6 deletions

diff --git a/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md b/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md
index a7d6850..7db2754 100644
--- a/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md
+++ b/_posts/2020-10-05-cargo2nix-dramatically-simpler-rust-in-nix.md
@@ -49,14 +49,14 @@ in pkgs.stdenv.mkDerivation {
 That `cargo test` part on line 20 is what I have been fighting with every
 "\*2nix" available for Rust out there. I don't want to bash any of them. All I
 want is to have full control of what Cargo commands to run, and the "*2nix" tool
-should only setup the environment for me. Let me run Cargo however I want, no
-need to parameterize how the tool runs Cargo for me, or even replicate Cargo
-commands by calling the Rust compiler directly.
+should only setup the environment for me. Let me drive Cargo myself, no need to
+parameterize how the tool runs it for me, or even replicate its internal
+behaviour by calling the Rust compiler directly.
 
 Sure it doesn't support private registries or Git dependencies, but how much
-bigger does it has to be to support it? Also, it doesn't support those **yet**,
-there's no reason it can't be extended to support them. I just haven't needed it
-yet, so I haven't added. Patches welcome.
+bigger does it has to be to support them? Also, it doesn't support those **yet**,
+there's no reason it can't be extended. I just haven't needed it yet, so I
+haven't added. Patches welcome.
 
 The layout of the `vendor/` directory is more explicit and public then what
 swift2nix does: it is whatever the command `cargo vendor` returns. However I