summaryrefslogtreecommitdiffstats
path: root/docs/guides/onap-developer/architecture/blueprint-enr.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/guides/onap-developer/architecture/blueprint-enr.rst')
-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.