clean up some sphinx warnings

[dcaegen2.git] / docs / sections / services / datalake-handler / overview.rst

diff --git a/docs/sections/services/datalake-handler/overview.rst b/docs/sections/services/datalake-handler/overview.rst
index fc14f99..f2d361a 100644 (file)
--- a/docs/sections/services/datalake-handler/overview.rst
+++ b/docs/sections/services/datalake-handler/overview.rst
@@ -1,6 +1,6 @@
-.. This work is licensed under a Creative Commons Attribution 4.0\r
-   International License. http://creativecommons.org/licenses/by/4.0\r
-   \r
+.. This work is licensed under a Creative Commons Attribution 4.0 International License.\r
+   http://creativecommons.org/licenses/by/4.0\r
+\r
 .. _docs_Datalake_Handler_MS:\r
 \r
 Architecture\r
@@ -9,12 +9,12 @@ Architecture
 \r
 Background\r
 ~~~~~~~~~~\r
-There are large amount of data flowing among ONAP components, mostly via DMaaP and Web Services. \r
-For example, all events/feed collected by DCAE collectors go through DMaaP. \r
-DMaaP is backed by Kafka, which is a system for Publish-Subscribe, \r
-where data is not meant to be permanent and gets deleted after certain retention period. \r
+There are large amount of data flowing among ONAP components, mostly via DMaaP and Web Services.\r
+For example, all events/feed collected by DCAE collectors go through DMaaP.\r
+DMaaP is backed by Kafka, which is a system for Publish-Subscribe,\r
+where data is not meant to be permanent and gets deleted after certain retention period.\r
 Kafka is not a database, means that data there is not for query.\r
-Though some components may store processed result into their local databases, most of the raw data will eventually lost. \r
+Though some components may store processed result into their local databases, most of the raw data will eventually lost.\r
 We should provide a systematic way to store these raw data, and even the processed result,\r
 which will serve as the source for data analytics and machine learning, providing insight to the network operation.\r
 \r
@@ -31,15 +31,15 @@ Note that not all data storage systems in the picture are supported. In R6, the
   - Elasticsearch and Kibana\r
   - HDFS\r
 \r
-Depending on demands, new systems may be added to the supported list. In the following we use the term database for the storage, \r
+Depending on demands, new systems may be added to the supported list. In the following we use the term database for the storage,\r
 even though HDFS is a file system (but with simple settings, it can be treats as a database, e.g. Hive.)\r
 \r
-Note that once the data is stored in databases, other ONAP components and systems will directly query data from the databases, \r
+Note that once the data is stored in databases, other ONAP components and systems will directly query data from the databases,\r
 without interacting with DataLake Handler.\r
 \r
 Description\r
 ~~~~~~~~~~~\r
-DataLake Handler's main function is to monitor and persist data flow through DMaaP and provide a query API for other component or external services. The databases are outside of ONAP scope, \r
+DataLake Handler's main function is to monitor and persist data flow through DMaaP and provide a query API for other component or external services. The databases are outside of ONAP scope,\r
 since the data is expected to be huge, and a database may be a complicated cluster consisting of thousand of nodes.\r
 \r
 Admin UI\r