From fb9f4ad68f6d9d226006f65a9cec9c71049d0b01 Mon Sep 17 00:00:00 2001 From: Matthew Cale Date: Fri, 11 May 2018 14:46:30 -0500 Subject: [PATCH] Typo fix "which mean blah" should be "which means blah" --- locale/en/docs/guides/event-loop-timers-and-nexttick.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locale/en/docs/guides/event-loop-timers-and-nexttick.md b/locale/en/docs/guides/event-loop-timers-and-nexttick.md index cc1d948b447b..f0896b04ee20 100644 --- a/locale/en/docs/guides/event-loop-timers-and-nexttick.md +++ b/locale/en/docs/guides/event-loop-timers-and-nexttick.md @@ -408,7 +408,7 @@ In essence, the names should be swapped. `process.nextTick()` fires more immediately than `setImmediate()`, but this is an artifact of the past which is unlikely to change. Making this switch would break a large percentage of the packages on npm. Every day more new modules are being -added, which mean every day we wait, more potential breakages occur. +added, which means every day we wait, more potential breakages occur. While they are confusing, the names themselves won't change. *We recommend developers use `setImmediate()` in all cases because it's