diff options
author | 2018-05-25 16:59:51 +0000 | |
---|---|---|
committer | 2018-05-25 17:01:12 +0000 | |
commit | 287fb30dce754ae1d02342d35afb6edf180d196d (patch) | |
tree | a88b3e2e3423f2398e437721ce18c70e2b92935f | |
parent | 107bef4e0a9f9552849e6adffa6122120b9e965f (diff) |
VNFRQTS - Update Chapter 2 Scope
Changing the release to refer to the current release.
Change-Id: I57018866aa955a0977e9471c07e41ce88fe0304c
Issue-ID: VNFRQTS-218
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
-rw-r--r-- | docs/Chapter2.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Chapter2.rst b/docs/Chapter2.rst index 805aa66..fcc4f45 100644 --- a/docs/Chapter2.rst +++ b/docs/Chapter2.rst @@ -12,7 +12,7 @@ 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. +- These requirements are applicable to the current release of ONAP. - Scope of the ONAP versions/release and future functionality - The VNF Requirements should include support for the functionality of the ONAP E-E use cases. |