cosmetic fixes (numbering, bulleting, TOC, section levels, ...)

JIRA: AUTO-26

edited files for better HTML rendering (especially, added missing blank lines to ensure proper bulleting)

Change-Id: I8165363f15f26bab2e3f72cc1435c4acf32f618b
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>

1 files changed, 4 insertions, 10 deletions

diff --git a/docs/release/userguide/UC01-feature.userguide.rst b/docs/release/userguide/UC01-feature.userguide.rst
index fd3a05f..5cf38e1 100644
--- a/docs/release/userguide/UC01-feature.userguide.rst
+++ b/docs/release/userguide/UC01-feature.userguide.rst
@@ -1,11 +1,7 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 .. SPDX-License-Identifier CC-BY-4.0
-.. (c) optionally add copywriters name
-
-.. contents::
-   :depth: 3
-   :local:
+.. (c) Open Platform for NFV Project, Inc. and its contributors
 
 
 ======================================
@@ -21,17 +17,15 @@ Description
 
 This use case aims at showcasing the benefits of using ONAP for autonomous Edge Cloud management.
 
-A high level of automation of VNF lifecycle event handling after launch is enabled by ONAP policies
-and closed-loop controls, which take care of most lifecycle events (start, stop, scale up/down/in/out,
-recovery/migration for HA) as well as their monitoring and SLA management.
+A high level of automation of VNF lifecycle event handling after launch is enabled by ONAP policies and closed-loop controls, which take care of most lifecycle events (start, stop, scale up/down/in/out, recovery/migration for HA) as well as their monitoring and SLA management.
 
-Multiple types of VNFs, for different execution environments, are first approved in the catalog thanks
-to the onboarding process, and then can be deployed and handled by multiple controllers in a systematic way.
+Multiple types of VNFs, for different execution environments, are first approved in the catalog thanks to the onboarding process, and then can be deployed and handled by multiple controllers in a systematic way.
 
 This results in management efficiency (lower control/automation overhead) and high degree of autonomy.
 
 
 Preconditions:
+
 #. hardware environment in which Edge cloud may be deployed
 #. an Edge cloud has been deployed and is ready for operation
 #. ONAP has been deployed onto a Cloud, and is interfaced (i.e. provisioned for API access) to the Edge cloud