From b503618d3dc1439523dc7d253b56e6655106c7f8 Mon Sep 17 00:00:00 2001
From: Vladimir Ponomarev <dajnz@users.noreply.github.com>
Date: Fri, 25 Mar 2016 23:05:22 +0300
Subject: [PATCH] Fix a minor typo in file

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

diff --git a/src/guide/components.md b/src/guide/components.md
index c3cf030abd..4b9ca3534b 100644
--- a/src/guide/components.md
+++ b/src/guide/components.md
@@ -145,7 +145,7 @@ Vue.js template engine is DOM-based and uses native parser that comes with the b
 - `table` can only contain `thead`, `tbody`, `tfoot` and `tr`, and these elements should be direct cildren of `table`
 - `tr` can only contain `th` and `td`, and these elements should be direct children of `tr`
 
-In practive these restriction can cause unexpected behavior. Although in simple cases it might appear to work, you can not rely on custom elements being expanded before browser validation. E.g. `<my-select><option>...</option></my-select>` is not a valid template even if `my-select` component eventually expands to `<select>...</select>`.
+In practice these restriction can cause unexpected behavior. Although in simple cases it might appear to work, you can not rely on custom elements being expanded before browser validation. E.g. `<my-select><option>...</option></my-select>` is not a valid template even if `my-select` component eventually expands to `<select>...</select>`.
 
 Another consequence is that you can not use custom tags (including custom elements and special tags like `<component>`, `<template>` and `<partial>`) inside of `ul`, `select`, `table` and other elements with similar restrictions. Custom tags will be hoisted out and thus not render properly.