diff --git a/README.md b/README.md
index d25d54ba4b4681a2854e3cd0f039662449dd3a15..79b02c949104aa3ecffc0c514434c9407f483ca6 100644
--- a/README.md
+++ b/README.md
@@ -1,32 +1,22 @@
-#Pika
+# Pika
[](https://travis-ci.org/Qihoo360/pika)
-##Introduction [中文] (https://github.com/Qihoo360/pika/blob/master/README_CN.md)
+## Introduction[中文](https://github.com/Qihoo360/pika/blob/master/README_CN.md)
Pika is a persistent huge storage service , compatible with the vast majority of redis interfaces ([details](https://github.com/Qihoo360/pika/wiki/pika-支持的redis接口及兼容情况)), including string, hash, list, zset, set and management interfaces. With the huge amount of data stored, redis may suffer for a capacity bottleneck, and pika was born for solving it. Except huge storage capacity, pika also support master-slave mode by slaveof command, including full and partial synchronization. You can alse use pika in twemproxy or codis(*pika has supported data migration in codis，thanks [left2right](https://github.com/left2right)*) for distributed Redis solution
-##UserList
+## UserList
+
-
-
-
-
-
+ 
-
-
-
-
-
-
-
-
+
[More](https://github.com/Qihoo360/pika/blob/master/USERS.md)
-##Feature
+## Feature
* huge storage capacity
* compatible with redis interface, you can migrate to pika easily
@@ -103,9 +93,9 @@ The __VERSION represents the OS's version, such as 6.2, 5.4...
The RPATH is defined in pika's Makefile
-##Performance
+## Performance
-###test environment
+### test environment
2 same hardware server, one for running pika, the other for running redis-benchmark
@@ -114,17 +104,17 @@ The RPATH is defined in pika's Makefile
OS: CentOS release 6.2 (Final)
NETWORK CARD: Intel Corporation I350 Gigabit Network Connection
-###test interfaces
+### test interfaces
Set, Get
-###test method
+### test method
run pika with 16 work threads, run redis-benchmark on another server as follow:
./redis-benchmark -h ... -p ... -n 1000000000 -t set,get -r 10000000000 -c 120 -d 200
execute 1 billion Set and 1 billion Get commands altogether
-###test result
+### test result
```
Set
1000000000 requests completed in 11890.80 seconds
@@ -161,19 +151,19 @@ Get
110338.10 requests per second
```
-###pika vs ssdb ([Detail](https://github.com/Qihoo360/pika/wiki/pika-vs-ssdb))
+### pika vs ssdb ([Detail](https://github.com/Qihoo360/pika/wiki/pika-vs-ssdb))
-##pika vs redis
+## pika vs redis
-##Documents
+## Documents
1. [Wiki](https://github.com/Qihoo360/pika/wiki)
-##Contact Us
+## Contact Us
Mail: g-infra-bada@360.cn
diff --git a/README_CN.md b/README_CN.md
index 846c268ce457c3b35ad12e0de726e768d99dadd4..c0a69e3bb9278e61ea96067ef5a26d5017a7d62a 100644
--- a/README_CN.md
+++ b/README_CN.md
@@ -1,22 +1,14 @@
# Pika
## 简介 [English](https://github.com/Qihoo360/pika/blob/master/README.md)
Pika是一个可持久化的大容量redis存储服务，兼容string、hash、list、zset、set的绝大接口([兼容详情](https://github.com/Qihoo360/pika/wiki/pika-支持的redis接口及兼容情况))，解决redis由于存储数据量巨大而导致内存不够用的容量瓶颈，并且可以像redis一样，通过slaveof命令进行主从备份，支持全同步和部分同步，pika还可以用在twemproxy或者codis中来实现静态数据分片（pika已经可以支持codis的动态迁移slot功能，目前在合并到master分支，欢迎使用，感谢作者[left2right](https://github.com/left2right)同学提交pr）
-##Pika用户
-
-
-
-
-
+## Pika用户
-
-
-
-
-
+
-
-
+
+
+
[更多](https://github.com/Qihoo360/pika/blob/master/USERS.md)
@@ -91,7 +83,7 @@ RPATH在Makefile定义，表示的是程序运行的库预先加载路径
## 性能
-###测试环境：
+### 测试环境：
```
相同配置服务端、客户机各一台：
处理器：24核 Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
@@ -99,18 +91,18 @@ RPATH在Makefile定义，表示的是程序运行的库预先加载路径
操作系统：CentOS release 6.2 (Final)
网卡：Intel Corporation I350 Gigabit Network Connection
```
-###测试接口：
+### 测试接口：
```
Set、Get
```
-###测试方法：
+### 测试方法：
```
pika配16个worker，客户机执行 ./redis-benchmark -h ... -p ... -n 1000000000 -t set,get -r 10000000000 -c 120 -d 200
通过set和get接口对pika进行10亿次写入+10亿次读取
```
-###测试结果：
+### 测试结果：
```
Set
1000000000 requests completed in 11890.80 seconds
@@ -147,11 +139,11 @@ RPATH在Makefile定义，表示的是程序运行的库预先加载路径
110338.10 requests per second
```
-###与SSDB性能对比（[详情](https://github.com/Qihoo360/pika/wiki/pika-vs-ssdb)）
+### 与SSDB性能对比（[详情](https://github.com/Qihoo360/pika/wiki/pika-vs-ssdb)）
-###与Redis性能对比
+### 与Redis性能对比
## 文档