diff options
author | 2018-07-23 15:25:07 +0100 | |
---|---|---|
committer | 2018-07-24 23:36:59 +0100 | |
commit | ddaa529938163597b4e189dda2f0fdbfa15a15bb (patch) | |
tree | 6c3d35a5943d2099ebede69fe7aa780369d42a62 /docs | |
parent | 09c5ec28f71d5603938861ea47d50b4ce72046b8 (diff) |
bugfix in blueprint-enr.rst
scaleing->scaling. some minor rephrasing.
Issue-ID: DOC-289
Change-Id: I38282c0f2ed0c677f1463b323aab2a6d048a95e3
Signed-off-by: kevinmcdonnell <kevin.mcdonnell@huawei.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/guides/onap-developer/architecture/blueprint-enr.rst | 2 |
1 files changed, 1 insertions, 1 deletions
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. |