Incorporating further review comments

Change-Id: I65fa2036f32c018c3d9cda46a82c6f1e2d4e6323
Signed-off-by: Georg Kunz <georg.kunz@ericsson.com>

1 files changed, 17 insertions, 11 deletions

diff --git a/docs/requirements/use_cases/programmable_provisioning.rst b/docs/requirements/use_cases/programmable_provisioning.rst
index 8d143f3..d66a54c 100644
--- a/docs/requirements/use_cases/programmable_provisioning.rst
+++ b/docs/requirements/use_cases/programmable_provisioning.rst
@@ -1,24 +1,27 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 
-Programmable Provisioning of Provider networks
+Programmable Provisioning of Provider Networks
 ----------------------------------------------
 Description
 ~~~~~~~~~~~
-In NFV environment the VNFM (consumer of OpenStack IaaS API) have no
-administrative rights, however in the telco domain provider networks are used in
-some cases. When a provider network is created administrative rights are needed
-what in the case of a VNFM without administrative rights needs manual work.
-It shall be possible to configure provider networks without administrative rights.
-It should be possible to assign the capability to create provider networks to
-any roles.
+
+In a NFV environment the VNFMs (Virtual Network Function Manager) are consumers
+of the OpenStack IaaS API. They are often deployed without administrative rights
+on top of the NFVI platform. Furthermore, in the telco domain provider networks
+are often used. However, when a provider network is created administrative
+rights are needed what in the case of a VNFM without administrative rights
+requires additional manual configuration work.  It shall be possible to
+configure provider networks without administrative rights.  It should be
+possible to assign the capability to create provider networks to any roles.
+
 
 Derived Requirements
 ~~~~~~~~~~~~~~~~~~~~~
    - Authorize the possibility of provider network creation based on policy
    - There should be a new entry in :code:`policy.json` which controls the provider network creation
    - Default policy of this new entry should be :code:`rule:admin_or_owner`.
-   - This policy should be respected by neutron API
+   - This policy should be respected by the Neutron API
 
 Northbound API / Workflow
 +++++++++++++++++++++++++
@@ -34,5 +37,8 @@ Only admin users can manage provider networks [OS-NETWORKING-GUIDE-ML2]_.
 
 Potential implementation
 ~~~~~~~~~~~~~~~~~~~~~~~~
-   - Policy engine shall be able to handle a new provider network creation and modification related policy
-   - When a provider network is created or modified neutron should check the authority with the policy engine instead of requesting administrative rights
+   - Policy engine shall be able to handle a new provider network creation and
+     modification related policy.
+   - When a provider network is created or modified neutron should check the
+     authority with the policy engine instead of requesting administrative
+     rights.