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>

diff --git a/docs/vnf_guidelines/vnf_guidelines.rst b/docs/vnf_guidelines/vnf_guidelines.rst
index 8be1e35..3394fc6 100644 (file)
--- 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