From 4d1bd71204c8510032253b4e1dea9199435c4742 Mon Sep 17 00:00:00 2001
From: Ghost-017 <31908292+Ghost-017@users.noreply.github.com>
Date: Sun, 17 Feb 2019 16:16:02 +0800
Subject: [PATCH] grammer fixes

- add a definite article before 'outer menu' on line 111
- don't -> won't
---
 2-ui/2-events/02-bubbling-and-capturing/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/2-ui/2-events/02-bubbling-and-capturing/article.md b/2-ui/2-events/02-bubbling-and-capturing/article.md
index 287f74f2..191b2739 100644
--- a/2-ui/2-events/02-bubbling-and-capturing/article.md
+++ b/2-ui/2-events/02-bubbling-and-capturing/article.md
@@ -108,7 +108,7 @@ Sometimes `event.stopPropagation()` creates hidden pitfalls that later may becom
 
 For instance:
 
-1. We create a nested menu. Each submenu handles clicks on its elements and calls `stopPropagation` so that outer menu don't trigger.
+1. We create a nested menu. Each submenu handles clicks on its elements and calls `stopPropagation` so that the outer menu won't trigger.
 2. Later we decide to catch clicks on the whole window, to track users' behavior (where people click). Some analytic systems do that. Usually the code uses `document.addEventListener('click'…)` to catch all clicks.
 3. Our analytic won't work over the area where clicks are stopped by `stopPropagation`. We've got a "dead zone".