From: kevinmcdonnell Date: Mon, 23 Jul 2018 14:25:07 +0000 (+0100) Subject: bugfix in blueprint-enr.rst X-Git-Tag: elalto.1.5.2~12305^2 X-Git-Url: https://gerrit.onap.org/r/gitweb?a=commitdiff_plain;h=ddaa529938163597b4e189dda2f0fdbfa15a15bb;p=doc.git bugfix in blueprint-enr.rst scaleing->scaling. some minor rephrasing. Issue-ID: DOC-289 Change-Id: I38282c0f2ed0c677f1463b323aab2a6d048a95e3 Signed-off-by: kevinmcdonnell --- diff --git a/docs/guides/onap-developer/architecture/blueprint-enr.rst b/docs/guides/onap-developer/architecture/blueprint-enr.rst index 404f7d0df..8c1616dd8 100644 --- a/docs/guides/onap-developer/architecture/blueprint-enr.rst +++ b/docs/guides/onap-developer/architecture/blueprint-enr.rst @@ -27,7 +27,7 @@ The Beijing release provides the initial support for these capabilities. The community has implemented manually triggered scale-out and scale-in in combination with a specific VNF manager (sVNFM) and demonstrated this with the VoLTE blueprint. An operator uses the Usecase UI (UUI) project -to trigger a scaleing operation. UUI communicates with the Service +to trigger a scaling operation. UUI communicates with the Service Orchestrator (SO). SO uses the VF-C controller, which in turn instructs a vendor-provided sVNFM to implement the scale-out action.