Updated:Typo

Issue-ID: DOC-389

Change-Id: I32e5b934056b85f5e94ca299492a4bbedf3713fb
Signed-off-by: Manish Kumar <manishjpiet@gmail.com>

diff --git a/docs/architecture.rst b/docs/architecture.rst
index f78db7b..74cb0c4 100644 (file)
--- a/docs/architecture.rst
+++ b/docs/architecture.rst
@@ -7,7 +7,7 @@ Architecture
 Project Description
 -------------------
 
-To achieve 5 9s of availability on 3 9s or lower software and infrastructure in a cost-effective manner, ONAP components need to work in a reliable, active-active manner across multiple sites (platform-maturity resiliency level 3). A fundamental aspect of this is  state management across geo-distributed sites in a reliable, scalable, highly available and efficient manner. This is an important and challenging problem because of three fundamental reasons:
+To achieve five 9s of availability on three 9s or lower software and infrastructure in a cost-effective manner, ONAP components need to work in a reliable, active-active manner across multiple sites (platform-maturity resiliency level 3). A fundamental aspect of this is  state management across geo-distributed sites in a reliable, scalable, highly available and efficient manner. This is an important and challenging problem because of three fundamental reasons:
 
 - Current solutions for state-management of  ONAP components like MariaDB clustering, that work very effectively within a site, may not scale across geo-distributed sites (e.g., Beijing, Amsterdam and Irvine) or allow partitioned operation (thereby compromising availability). This is mainly because WAN latencies are much higher across sites and frequent network partitions can occur.
 

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index d764ced..df83ace 100644 (file)
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -13,7 +13,7 @@ Version: 3.0.24
 
 **New Features**
 
-- MUSIC as a Service: while MUSIC was consumed internally by components in the Beijing release, in Cassablanca MUSIC can be deployed as an independent multi-site clustered service
+- MUSIC as a Service: while MUSIC was consumed internally by components in the Beijing release, in Casablanca MUSIC can be deployed as an independent multi-site clustered service
 
 - Designed MUSIC to be a fully sharded, scale out system, where as many ONAP sites/component replicas can be added as required for performance