Update index and architecture page

Issue-ID: OPTFRA-394
Change-Id: Ib7f1270a451f59caf1047ca306949e5ca1fcb055
Signed-off-by: Jerry Flood <jflood@att.com>

1 files changed, 4 insertions, 4 deletions

diff --git a/docs/sections/consumedapis.rst b/docs/sections/consumedapis.rst
index ce4a2fc..d8d6c6c 100644
--- a/docs/sections/consumedapis.rst
+++ b/docs/sections/consumedapis.rst
@@ -26,15 +26,15 @@ Conflict avoidance requires:
 
  * Horizontal topology assets ???
 
- * Availability of the VNFs and the availability of the assets identified in the previous items.
-   This generally requires a change management
-   tracking/ticketing system system that identifies scheduled changes to all assets that contribute to the
+ * Availability of the VNFs and of the assets identified in the previous items.
+   Knowing the availability of related assests generally requires a change management
+   tracking/ticketing system system that identifies scheduled changes (unavailaibility) to all assets that contribute to the
    functioning of the network.
 
    * There is no change management ticketing system within ONAP. CMSO itself may serve as such in a very limited capacity as it
      tracks scheduled changes to VNFs. It does not track changes the all network assets which is necessarilty required for full
      conflict avoidance. For ONAP Dublin, the conflict avoidance will necessarily be limited to VNF level conflict
-     checking using CMSO as the source of asset avaialability/unavailability.
+     checking using CMSO as the source of asset (VNF) avaialability/unavailability.
 
 
 Change Management Ticketing System (TBD)