From 9d264b91c4f8f7acf10b7a3978b991b58b38b60f Mon Sep 17 00:00:00 2001 From: "Bozawglanian, Hagop (hb755d)" Date: Thu, 23 Aug 2018 20:59:23 +0000 Subject: VNFRQTS - Updating reference to Beijing Updating wording from Beijing Change-Id: If7375d9a87a099cc31c5c3955abd535b85b3235e Issue-ID: VNFRQTS-285 Signed-off-by: Bozawglanian, Hagop (hb755d) --- docs/vnf_guidelines/vnf_guidelines.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') 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 -- cgit 1.2.3-korg