diff --git a/doc/design/python_api.md b/doc/design/python_api.md
index 395341d37ed54edba494091722789e7631bb57f2..e314d1049c1662cfd413d651dcc3c1ac2d712cfd 100644
--- a/doc/design/python_api.md
+++ b/doc/design/python_api.md
@@ -1,22 +1,20 @@
 # Design Doc: Python API
 
-<!-- 引言，说明问题 -->
-
 The top level user API in Python should be as same as API in `paddle.v2` after refactoring Paddle from a layer based framework to an operator based framework. There are many new classes in CPP in [compile time] for describing neural networks, such as `Variable`, `Operator`, `Block`. The issue about current design is how to give a proper way to wrap the C++ API to `paddle.v2` API and writing layers in Python.
 
-<!-- 说明为什么我们要先用runtime概念实现Python API。说明我们必须要同时考虑编译器API，进而让之后迁移更简单 -->
-
 This implementation of Python API includes two steps.
 
 1. Implement the Python API using current C++ runtime concepts.
 2. Replace the implementation by using compile-time concepts when they are completed.
 
-...
+The implementation of the first step is a temporary implementation. We should design our Python API concepts based on `compile-time` concepts. We just use `runtime` classes to implement it for now.
+
+
+## Python Class and compile-time protobuf
 
+As we design our Python API concepts based on `compile-time`, we try to map our Python classes to every compile-time result, i.e., the protobuf messages. They are:
 
-## Python Class about compile-time concepts
 
-<!-- 引言，引出这个表格 -->
 | Python Class | Compile-time protobuf |
 | --- | --- |
 | Block | BlockDesc |