Fixed typos in these 3 files.

3 files changed, 8 insertions, 8 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.
diff --git a/docs/requirements/04-gaps.rst b/docs/requirements/04-gaps.rst
index 1d2cb61..3789755 100644
--- a/docs/requirements/04-gaps.rst
+++ b/docs/requirements/04-gaps.rst
@@ -6,10 +6,10 @@ Network  related gaps
 
 1. Terminology.
     Consider to keep upstream/downstream terminology for the traffic leaving/coming to Edge NFV. This gives
-    unambiquies names 'uplink/downlink' or 'access/network' for CPE interfaces. Inside DC this traffic is
-    calles east-west and no special meaning for interfaces on compute/network node.
+    unambiguous names 'uplink/downlink' or 'access/network' for CPE interfaces. Inside DC this traffic is
+    called east-west and no special meaning for interfaces on compute/network node.
 2. Uplink interface capacity.
-    In most cases those are 1GE as opposite to DC where 10/40G interfaces are prevaling. As result
+    In most cases those are 1GE as opposite to DC where 10/40G interfaces are prevailing. As result
     1GE interfaces are not part of CI.
 3. Tunneling technology:
     a. Case stand-alone NFVI - 802.1ad S-VLAN or MPLS.
@@ -19,10 +19,10 @@ Network  related gaps
     #. All above tunneling technology don't support payload enryption (optional).
 4. Management traffic:
     a. Management traffic should come inband with tenant traffic.
-    b. Management traffic shoud be easiliy come trough firewalls, i.e. single IP/port woudl be ideal
+    b. Management traffic should easily come through firewalls, i.e. single IP/port would be ideal
        (compare with OpenStack bunch of protocols [firewall]_).
     c. Management connection might be disrupted for a long period of time; once provisioned Edge NFV device
-       must keep its functionaly with no respect of management connection state.
+       must keep its functionality with no respect of management connection state.
 5. Resiliency:
     a. Network resiliency is based on dual-homing, service path shall be forked in that case. A VM presumable shall
        be able to select active virtual link for data forwarding
diff --git a/docs/requirements/glossary.rst b/docs/requirements/glossary.rst
index e2f0a4c..b3cf4d0 100644
--- a/docs/requirements/glossary.rst
+++ b/docs/requirements/glossary.rst
@@ -11,7 +11,7 @@ mapping/translating the OPNFV terms to terminology used in other contexts.
 .. glossary::
 
     CPE
-        Customer Premices Equipment
+        Customer Premises Equipment
     CSP
         Communication Service Provider
     DC