summaryrefslogtreecommitdiffstats
path: root/docs/Chapter4/Design.rst
diff options
context:
space:
mode:
authorSteven Wright <sw3588@att.com>2018-07-30 15:46:46 +0000
committerGerrit Code Review <gerrit@onap.org>2018-07-30 15:46:46 +0000
commitb01f2e62513c2fb8637865d71b2f9bbdeed5e9fa (patch)
tree5a7524c34fcb78b839deb077e518447c47641cda /docs/Chapter4/Design.rst
parente99e1863cb04530ee563086f4bf5479b63b9a82b (diff)
parenta4e0df11ff98a3a1b821f619e040506e3c3a33ed (diff)
Merge "VNFRQTS - Correcting initial release info"
Diffstat (limited to 'docs/Chapter4/Design.rst')
-rw-r--r--docs/Chapter4/Design.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/Chapter4/Design.rst b/docs/Chapter4/Design.rst
index 35acd65..70f5598 100644
--- a/docs/Chapter4/Design.rst
+++ b/docs/Chapter4/Design.rst
@@ -20,7 +20,7 @@ grouping functions in a common cloud data center to minimize
inter-component latency. The VNFs should be designed with a goal of
being modular and reusable to enable using best-in-breed vendors.
-Section 5.a VNF Design in *VNF Guidelines* describes
+Section 4.1 VNF Design in *VNF Guidelines* describes
the overall guidelines for designing VNFs from VNF Components (VNFCs).
Below are more detailed requirements for composing VNFs.