diff --git a/specs/train/join-tricircle-and-trio2o.rst b/specs/train/join-tricircle-and-trio2o.rst
index 4dd7f18a..079d2c0e 100644
--- a/specs/train/join-tricircle-and-trio2o.rst
+++ b/specs/train/join-tricircle-and-trio2o.rst
@@ -5,10 +5,9 @@ Join Tricircle and Trio2o together
 Blueprint
 =========
 
-https://blueprints.launchpad.net/tricircle/
-~/+spec/join-tricircle-and-trio2o-together
+https://blueprints.launchpad.net/tricircle/+spec/join-tricircle-and-trio2o-together
 
-  At the very beginning, Tricircle and Tiro2o has the same Poc Stage
+At the very beginning, Tricircle and Tiro2o has the same Poc Stage
 Project called OpenStack Cascased Solution[1] by Huawei. After
 tests they get divided as two independent project in community.
 Tricircle focus on network automation across neutron servers in
@@ -21,7 +20,7 @@ openstack management since the beginning. This blueprint
 try to reunite Tricircle and Trio2o as a unified and complete
 project dedicated to multi-region OpenStack clouds management.
 Problem Description
-  Tricircle is one of the Community official components and kept
+Tricircle is one of the Community official components and kept
 on the pace with every Iterative version. The newest version is
 Stein. While Tio2o is out of update and management for a long time.
 The newest version is Mitaka. Also there exists a big problem is that
@@ -43,9 +42,15 @@ References
 ==========
 
 [1].https://wiki.openstack.org/wiki/OpenStack_cascading_solution
+
 [2].https://wiki.openstack.org/wiki/Tricircle
+
 [3].https://wiki.openstack.org/wiki/Trio2o
+
 [4].https://github.com/openstack/tricircle
+
 [5].https://github.com/openstack/python-tricircleclient
+
 [6].https://github.com/openstack/trio2o
+
 [7].https://docs.openstack.org/tricircle/latest/user/readme.html