diff options
| author |   Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-04-04 16:36:15 +0000 |
|---|---|---|
| committer | Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-04-04 16:37:07 +0000 |
| commit | 730a098e8c2fc7e3e59a9ee0d35a61911f04ac1b (patch) | |
| tree | 64f5c02ea36ead3d1be0cf170c2107be5af91088 /docs/Chapter2.rst | |
| parent | d782ad6392583bbcc185ce04db0b2d36d7b1bb41 (diff) | |
VNFRQTS - Cleaning the format of rst files
Cleaning the rst files so doc8 results won't give so many issues.
Change-Id: Ia071baf867841fdfc29d0860c1b431e5e451ea0d
Issue-ID: VNFRQTS-200
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
Diffstat (limited to 'docs/Chapter2.rst')
| -rw-r--r-- | docs/Chapter2.rst | 19 |
1 files changed, 14 insertions, 5 deletions
diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index 0cbec53..1dd3340 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -5,15 +5,22 @@ **Scope** ============ -- The audience for this document are VNF/PNF providers, NCSPs and other interested 3rd parties who need to know the design, build and lifecycle management requirements for VNFs/PNFs to be compliant with ONAP. -- These requirements are strictly from a standpoint of what the VNF/PNF developer needs to know to operate and be compliant with ONAP. -- Requirements that are not applicable to VNF/PNF providers such as those that applicable to service providers are not included in this document. +- The audience for this document are VNF/PNF providers, NCSPs and other + interested 3rd parties who need to know the design, build and lifecycle + management requirements for VNFs/PNFs to be compliant with ONAP. +- These requirements are strictly from a standpoint of what the VNF/PNF + developer needs to know to operate and be compliant with ONAP. +- Requirements that are not applicable to VNF/PNF providers such as those + that applicable to service providers are not included in this document. - These requirements are applicable to the Amsterdam release of ONAP. - Scope of the ONAP versions/release and future functionality References ----------------------- -This section contains a list of normative and informative references along with information on acquiring the identified references. Normative references are required to be implemented by this document. Informative references are for informational purposes only. +This section contains a list of normative and informative references along +with information on acquiring the identified references. Normative references +are required to be implemented by this document. Informative references are +for informational purposes only. Normative References ^^^^^^^^^^^^^^^^^^^^^^^ @@ -35,5 +42,7 @@ Reference Acquisition ^^^^^^^^^^^^^^^^^^^^^^^ IETF Specifications: -- Internet Engineering Task Force (IETF) Secretariat, 48377 Fremont Blvd., Suite 117, Fremont, California 94538, USA; Phone: +1-510-492-4080, Fax: +1-510-492-4001. +- Internet Engineering Task Force (IETF) Secretariat, 48377 Fremont Blvd., + Suite 117, Fremont, California 94538, USA; Phone: +1-510-492-4080, + Fax: +1-510-492-4001. |