summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorRich Bennett <rb2745@att.com>2018-07-26 02:01:48 +0000
committerGerrit Code Review <gerrit@onap.org>2018-07-26 02:01:48 +0000
commit4477b8daf9076a96687942e9ee055f5f90509961 (patch)
tree948fd9cf8f846f45f40a48158f2f61a589f3c962 /docs
parent015b460eb37735c9183308ce885427eeeb211ff6 (diff)
parentddaa529938163597b4e189dda2f0fdbfa15a15bb (diff)
Merge "bugfix in blueprint-enr.rst"
Diffstat (limited to 'docs')
-rw-r--r--docs/guides/onap-developer/architecture/blueprint-enr.rst2
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.