diff options
| author |   Yan Yang <yangyanyj@chinamobile.com> | 2019-08-08 13:53:11 +0000 |
|---|---|---|
| committer |   Gerrit Code Review <gerrit@onap.org> | 2019-08-08 13:53:11 +0000 |
| commit | e76a3f2154c45d43f75013c7e85c6d9bec65c32a (patch) | |
| tree | 2fb7886b2f2f7694c578b02ace5463a83bf60ddb | |
| parent | d2527b550552b3647a06ca983b6c57b422bdc727 (diff) | |
| parent | 563ce1bac61110fbf92a3bb6efb15d078ff3a501 (diff) | |
Merge "fix for index"
| -rw-r--r-- | docs/platform/index.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/platform/index.rst b/docs/platform/index.rst index f9d0a2da..d9f6feea 100644 --- a/docs/platform/index.rst +++ b/docs/platform/index.rst @@ -34,14 +34,14 @@ VF-C as one controller in ONAP includes two components NFV-O and GVNFM. * compliant with ETSI NFV MANO architecture and information model, * providing resource orchestration and full life cycle management and FCAPS for NS, * providing standard south bound interface to VNFMs, - * providing north bound interface to SO, to take part in fulfilling the orchestraion and operation of end2end service, + * providing north bound interface to SO, to take part in fulfilling the orchestration and operation of end2end service, * providing interface and work with DCAE and Policy for Close Loop Automation. * GVNFM component * compliant with ETSI NFV MANO architecture and information model * providing full life cycle management and FCAPS for VNFs which do not require a vendor VNFM, - * providing interface and work with NFV-O component, to take part in fulfiiling the LCM and FCAPS management of NS, + * providing interface and work with NFV-O component, to take part in fulfilling the LCM and FCAPS management of NS, * providing interface and work with DCAE and Policy for Close Loop Automation. |