X-Git-Url: https://gerrit.onap.org/r/gitweb?p=multicloud%2Fframework.git;a=blobdiff_plain;f=docs%2Fspecs%2Fmulticloud-multi-region.rst;h=cabd110a440293d10d71a60a5dd18bce587c9ba9;hp=b67626f599ddc0d2a1a4b1fbc994dd779811dad9;hb=a2dcefabf7239c4687c3ab01e03796e017211285;hpb=9e3eaba3ce475451e3ad4e13c7c6d5c0512e1a14

diff --git a/docs/specs/multicloud-multi-region.rst b/docs/specs/multicloud-multi-region.rst
index b67626f..cabd110 100644
--- a/docs/specs/multicloud-multi-region.rst
+++ b/docs/specs/multicloud-multi-region.rst
@@ -13,7 +13,6 @@ Problems Statement
 ==================
 
 The ONAP functional requirement for Edge Automation aims to automate the VNF orchestration across edge stacks.
-
 ..
 https://wiki.onap.org/display/DW/Edge+Automation+through+ONAP
 
@@ -25,15 +24,16 @@ of all OpenStack secondary regions.
 Proposed Design and Workflow
 ============================
 
-**This automation assumes**:
+This automation assumes:
  - ONAP could use the same set of credentials (project, user/password) to access all OpenStack regions for orchestration.
  - ONAP user will explicitly enable the automation of discovery OpenStack secondary regions during manually on-boarding the OpenStack primary region.
  - ONAP users could manually manage the cloud regions representing those secondary regions just like a normal cloud region
 
 
-**With OpenStack primary region, the ONAP user will**:
+With OpenStack primary region, the ONAP user will:
 ..
 https://wiki.onap.org/pages/viewpage.action?pageId=25431491
+
  - Manually on-board this primary region with ESR VIM registration portal.
  - Input the {cloud-owner} and {cloud-region-id} as the ID of cloud region which is unique.
  - Specify the location id