diff options
author | Prayson Pate <ppate@advaoptical.com> | 2016-03-13 17:41:05 -0400 |
---|---|---|
committer | Prayson Pate <ppate@advaoptical.com> | 2016-03-13 17:41:05 -0400 |
commit | 70c11fd27c55cf835f658494bb540eac7446cd27 (patch) | |
tree | e08ea26487a7fce2af5bd78cb469a736b1a8c60a /docs/requirements/02-use_cases.rst | |
parent | 39f1ef9331490bc166ad588c04a3f8e83766e453 (diff) |
Fixed typos in these 3 files.
Diffstat (limited to 'docs/requirements/02-use_cases.rst')
-rw-r--r-- | docs/requirements/02-use_cases.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/requirements/02-use_cases.rst b/docs/requirements/02-use_cases.rst index b70cc0f..6777a02 100644 --- a/docs/requirements/02-use_cases.rst +++ b/docs/requirements/02-use_cases.rst @@ -4,7 +4,7 @@ Use cases and scenarios There are several use cases related to Edge NFV: 1. vE-CPE. - [vE-CPE]_ is related to most popupar NFV use case where NFVI compute node is + [vE-CPE]_ is related to most popular NFV use case where NFVI compute node is located at customer premises. Typical applications are virtual Firewall and Virtual BGP router; VNF chain can be hosted in vE-CPU host and/or DC @@ -13,7 +13,7 @@ There are several use cases related to Edge NFV: 3. Residential GW. Similar to vE-CPE, the major difference is scale. Typical VNFs are "WAN fault monitoring", - "Performance monitoring". Ratio between deplyed vE-CPE + "Performance monitoring". Ratio between deployed vE-CPE and Residential GW might reach 1:100 or even 1:1000, thus VNF management overhead must be minimized. For instance, self-termination after predefined activity period seems preferable over explicit VNF removing via management system. |