Modify onos release doc

Change-Id: I325ddfbcfdc30f22dbeaa570bc4518c8091c62ec
Signed-off-by: CNlucius <lukai1@huawei.com>

1 files changed, 3 insertions, 6 deletions

diff --git a/docs/scenarios/os-onos-nofeature-sfc/scenario-description.rst b/docs/scenarios/os-onos-nofeature-sfc/scenario-description.rst
index 4e2e2724..b509cde3 100644
--- a/docs/scenarios/os-onos-nofeature-sfc/scenario-description.rst
+++ b/docs/scenarios/os-onos-nofeature-sfc/scenario-description.rst
@@ -31,8 +31,9 @@ Version history
 Introduction
 ============
 
-ONOSFW addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework. 
-In the Colorado release, in addition to the features in the Brahmaputra release, ONOSFW has included more functions in the Goldeneys of ONOS, and added service Function Chaining scenario by integrating the networking-sfc capability of openstack.
+ONOSFW addresses integrating an SDN controller of choice based on a target applications or use cases within the OPNFV defined NFVI and VIM framework.
+In the Colorado release, in addition to the features in the Brahmaputra release, ONOSFW has included more functions in the Goldeneys of ONOS, \
+and added service Function Chaining scenario by integrating the networking-sfc capability of openstack.
 Therefore, both features and scenarios configurations are described.
 
 ONOSFW Test Scenarios
@@ -63,8 +64,6 @@ Secenario 14 ONOS-HA :
 
       2.1.3 Related flow rule deleted when VM is deleted is OK
 
- 
-
    2.2 L3 south - north function
 
       2.2.1. Ping external network (such as google) from VM by allocating a floating IP is OK
@@ -73,8 +72,6 @@ Secenario 14 ONOS-HA :
 
       2.2.3. VM hot migration is supported
 
- 
-
    2.3 Improvements
 
       2.3.1 Add p2any vxlan config to ovs is OK