From 179f664f47fbe4d5492ae836c289a28a550abd46 Mon Sep 17 00:00:00 2001
From: Abhishek Jain <01abhishekjain@gmail.com>
Date: Tue, 20 Feb 2018 13:16:46 +0530
Subject: [PATCH] Update events.md

---
 src/v2/guide/events.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/v2/guide/events.md b/src/v2/guide/events.md
index 2611569c41..b776c3f8a5 100644
--- a/src/v2/guide/events.md
+++ b/src/v2/guide/events.md
@@ -194,7 +194,7 @@ To address this problem, Vue provides **event modifiers** for `v-on`. Recall tha
 <div v-on:click.self="doThat">...</div>
 ```
 
-<p class="tip">Order matters when using modifiers because the relevant code is generated in the same order. Therefore using `@click.prevent.self` will prevent **all clicks** while `@click.self.prevent` will only prevent clicks on the element itself.</p>
+<p class="tip">Order matters when using modifiers because the relevant code is generated in the same order. Therefore using `v-on:click.prevent.self` will prevent **all clicks** while `v-on:click.self.prevent` will only prevent clicks on the element itself.</p>
 
 > New in 2.1.4+