From 2bbbd7624052699746f4752ea961b6e1adb376c7 Mon Sep 17 00:00:00 2001
From: Chris Donley <christopher.donley@huawei.com>
Date: Wed, 6 Jun 2018 09:25:29 -0700
Subject: Fix Arch/blueprint Doc formatting
Issue-ID: DOC-275
Change-Id: Id281489f36ff1b66bed416ae45a0961502c42caf
Signed-off-by: Chris Donley <christopher.donley@huawei.com>
---
docs/guides/onap-developer/architecture/blueprint-enr.rst | 8 ++++----
docs/guides/onap-developer/architecture/onap-architecture.rst | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
(limited to 'docs/guides')
diff --git a/docs/guides/onap-developer/architecture/blueprint-enr.rst b/docs/guides/onap-developer/architecture/blueprint-enr.rst
index 404f7d0df..a3018a195 100644
--- a/docs/guides/onap-developer/architecture/blueprint-enr.rst
+++ b/docs/guides/onap-developer/architecture/blueprint-enr.rst
@@ -1,5 +1,5 @@
ONAP Blueprint Enrichment
-~~~~~~~~~~~~~~~~~~~~~~~~~
+-------------------------
The ONAP Beijing release includes four functional enhancements in the
areas of manually triggered scaling, change management, and hardware
@@ -9,7 +9,7 @@ applicable to any use case; however, to showcase them in a concrete
manner, they have been incorporated into VoLTE and vCPE blueprints.
Manually Triggered Scaling
-^^^^^^^^^^^^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~~~~~~~~~~~~
Scale-out and scale-in are two primary benefits of NFV. Scaling can be
triggered manually (e.g., by a user or OSS/BSS) or automatically via a
@@ -41,7 +41,7 @@ APPC over DMaaP, where APPC picks it up and executes the configuration
scale out action on the requested VNF.
Change Management
-^^^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~~~
NFV will bring with it an era of continuous, incremental changes instead
of periodic step-function software upgrades, in addition to a constant
@@ -69,7 +69,7 @@ the SDN-C controller in terms of running the pre-check, post-check and
upgrade through Ansible playbooks.
Hardware Platform Awareness (HPA)
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Many VNFs have specific hardware requirements to achieve their
performance and security goals. These hardware requirements may range
diff --git a/docs/guides/onap-developer/architecture/onap-architecture.rst b/docs/guides/onap-developer/architecture/onap-architecture.rst
index 9bd6d0512..de921a884 100644
--- a/docs/guides/onap-developer/architecture/onap-architecture.rst
+++ b/docs/guides/onap-developer/architecture/onap-architecture.rst
@@ -587,7 +587,7 @@ faster than any one product could on its own.
.. |image3| image:: media/ONAP-oom.png
:width: 2.28472in
:height: 2.30625in
-.. |image4| image:: media/ONAP-closedloop.jpeg
+.. |image4| image:: media/ONAP-closedloop.png
:width: 6in
:height: 2.6in
.. |image5| image:: media/ONAP-vcpe.png
--
cgit