From f720956d3e17d61b9b71d3af3f65a4c92303b931 Mon Sep 17 00:00:00 2001
From: Mitar <mitar.github@tnode.com>
Date: Sat, 16 Apr 2016 19:43:53 -0700
Subject: [PATCH] Sync names for child component.

---
 src/guide/components.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/guide/components.md b/src/guide/components.md
index f4501c60ba..e22242a570 100644
--- a/src/guide/components.md
+++ b/src/guide/components.md
@@ -549,9 +549,9 @@ To make the composition work, we need a way to interweave the parent "content" a
 Before we dig into the API, let's first clarify which scope the contents are compiled in. Imagine a template like this:
 
 ``` html
-<child>
+<child-component>
   {{ msg }}
-</child>
+</child-component>
 ```
 
 Should the `msg` be bound to the parent's data or the child data? The answer is parent. A simple rule of thumb for component scope is:
@@ -562,7 +562,7 @@ A common mistake is trying to bind a directive to a child property/method in the
 
 ``` html
 <!-- does NOT work -->
-<child v-show="someChildProperty"></child>
+<child-component v-show="someChildProperty"></child-component>
 ```
 
 Assuming `someChildProperty` is a property on the child component, the example above would not work as intended. The parent's template should not be aware of the state of a child component.