From d4441457bce85e63d34874cfdd2789016bb7facc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=E6=88=90=E6=AD=A6?= <bcw.5@foxmail.com>
Date: Mon, 6 Jan 2014 00:16:05 +0800
Subject: [PATCH] update 04-schema.md aliases.md

---
 cn-introduction/04-schema.md        | 10 ++++------
 cn-introduction/articles/aliases.md |  4 ++--
 2 files changed, 6 insertions(+), 8 deletions(-)

diff --git a/cn-introduction/04-schema.md b/cn-introduction/04-schema.md
index 8344e1b..9f7f3db 100644
--- a/cn-introduction/04-schema.md
+++ b/cn-introduction/04-schema.md
@@ -256,12 +256,10 @@ Example:
         }
     }
 
-> **Note:** While this is convenient at times, it should not be how you use
-> packages in the long term because it comes with a technical limitation. The
-> composer.json metadata will still be read from the branch name you specify
-> before the hash. Because of that in some cases it will not be a practical
-> workaround, and you should always try to switch to tagged releases as soon
-> as you can.
+> **注意：** 虽然这有时很方便，但不应该长期在你的包中使用，因为它有一个技术上的限制。
+> composer.json 将仍然在哈希值之前指定的分支名称读取元数据，
+> 正因为如此，在某些情况下，它不会是一个实用的解决方法，
+> 如果可能，你应该总是尝试切换到拥有标签的版本。
 
 It is also possible to inline-alias a package constraint so that it matches
 a constraint that it otherwise would not. For more information [see the
diff --git a/cn-introduction/articles/aliases.md b/cn-introduction/articles/aliases.md
index 26a9c46..f8eab03 100644
--- a/cn-introduction/articles/aliases.md
+++ b/cn-introduction/articles/aliases.md
@@ -2,9 +2,9 @@
     tagline: Alias branch names to versions
 -->
 
-# Aliases
+# 别名
 
-## Why aliases?
+## 为什么使用别名？
 
 When you are using a VCS repository, you will only get comparable versions for
 branches that look like versions, such as `2.0`. For your `master` branch, you