Merge "VNFRQTS - R-26371 wording update to clarify req"

diff --combined docs/Chapter4.rst
index 745be04,8727ff9..bc4733a
--- 1/docs/Chapter4.rst
--- 2/docs/Chapter4.rst
+++ b/docs/Chapter4.rst
@@@ -1,9 -1,4 +1,9 @@@
 -**4. VNF Development Requirements**
 +.. This work is licensed under a Creative Commons Attribution 4.0 International License.
 +.. http://creativecommons.org/licenses/by/4.0
 +.. Copyright 2017 AT&T Intellectual Property.  All rights reserved.
 +
 +
 +**4. VNF Development Requirements**
  ====================================
  
  a. VNF Design
@@@ -113,11 -108,11 +113,11 @@@ applications
  
  Application Resilient Error Handling Requirements
  
- * R-26371 The VNF **MUST** detect connectivity failure for inter VNFC instance and intra/inter VNF and re-establish connectivity automatically to maintain the VNF without manual intervention to provide service continuity.
+ * R-26371 The VNF **MUST** detect communication failure for inter VNFC instance and intra/inter VNF and re-establish communication automatically to maintain the VNF without manual intervention to provide service continuity.
  * R-18725 The VNF **MUST** handle the restart of a single VNFC instance without requiring all VNFC instances to be restarted.
  * R-06668 The VNF **MUST** handle the start or restart of VNFC instances in any order with each VNFC instance establishing or re-establishing required connections or relationships with other VNFC instances and/or VNFs required to perform the VNF function/role without requiring VNFC instance(s) to be started/restarted in a particular order.
  * R-80070 The VNF **MUST** handle errors and exceptions so that they do not interrupt processing of incoming VNF requests to maintain service continuity.
 -* R-32695 The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior.
 +* R-32695 The VNF **MUST** provide the ability to modify the number of retries, the time between retries and the behavior/action taken after the retries have been exhausted for exception handling to allow the NCSP to control that behavior,where the interface and/or functional specification allows for altering behaviour.
  * R-48356 The VNF **MUST** fully exploit exception handling to the extent that resources (e.g., threads and memory) are released when no longer needed regardless of programming language.
  * R-67918 The VNF **MUST** handle replication race conditions both locally and geo-located in the event of a data base instance failure to maintain service continuity.
  * R-36792 The VNF **MUST** automatically retry/resubmit failed requests made by the software to its downstream system to increase the success rate.