diff options
| author |   Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-08-23 20:59:23 +0000 |
|---|---|---|
| committer | Bozawglanian, Hagop (hb755d) <hb755d@att.com> | 2018-08-23 21:02:27 +0000 |
| commit | 9d264b91c4f8f7acf10b7a3978b991b58b38b60f (patch) | |
| tree | 9ebd3d23c5ee65a754684782ad270fe3a9a23203 | |
| parent | d70844edb9220d92114a182a098612791de12309 (diff) | |
VNFRQTS - Updating reference to Beijing
Updating wording from Beijing
Change-Id: If7375d9a87a099cc31c5c3955abd535b85b3235e
Issue-ID: VNFRQTS-285
Signed-off-by: Bozawglanian, Hagop (hb755d) <hb755d@att.com>
| -rw-r--r-- | docs/vnf_guidelines/vnf_guidelines.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/vnf_guidelines/vnf_guidelines.rst b/docs/vnf_guidelines/vnf_guidelines.rst index 8be1e35..3394fc6 100644 --- a/docs/vnf_guidelines/vnf_guidelines.rst +++ b/docs/vnf_guidelines/vnf_guidelines.rst @@ -45,7 +45,7 @@ VNF/PNF Guidelines what the VNF developer needs to know to operate and be compliant with ONAP. - These guidelines contains high level expectations and references to specific requirements documentation for VNFs/PNFs which are applicable - to the Beijing release of ONAP. + to the current release of ONAP. - Part of the guidelines also contains visionary recommendations for future functionality that could be desirable for ONAP future releases. - Conformance requirements are in the `VNF/PNF Requirements |