From 80df1ada2142220195cfd8c2fb4983655905aae6 Mon Sep 17 00:00:00 2001
From: Mike Boutin <mike.boutin@gmail.com>
Date: Wed, 26 Feb 2020 14:09:56 -0500
Subject: [PATCH] Correct `--minimum-duration` spelling

---
 posts/inside-rust/2020-02-25-intro-rustc-self-profile.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/posts/inside-rust/2020-02-25-intro-rustc-self-profile.md b/posts/inside-rust/2020-02-25-intro-rustc-self-profile.md
index 83234a4cb..0968fe9b8 100644
--- a/posts/inside-rust/2020-02-25-intro-rustc-self-profile.md
+++ b/posts/inside-rust/2020-02-25-intro-rustc-self-profile.md
@@ -174,7 +174,7 @@ If the `chrome_profiler.json` file gets too large, the normal Chromium performan
 One easy way to deal with this is to tell `crox` to remove events shorter than a chosen duration:
 
 ```sh
-$ crox --minumum-duration 2 regex-17088
+$ crox --minimum-duration 2 regex-17088
 ```
 
 Filtering out events less than 2 microseconds shrinks our `chrome_profiler.js` file from 27mb to 11mb.