Fixed Codacy issues of Markdown files

Signed-off-by: Rohan Dhodare <[email protected]>

Author: Rohan Dhodare

doc/CORTX-MOTR-ARCHITECTURE.md

@@ -1,4 +1,5 @@
-![image](./Images/1_EOS_Core_Architecture_Overview.png)  
+
+![image](./Images/1_EOS_Core_Architecture_Overview.png)
 
 # Outline  
 +  This presentation is a beginner's guide to the CORTX core architecture
@@ -12,7 +13,7 @@
 +  FDMI
 +  ADDB  
 
-## What is CORTX 
+# What is CORTX?  
 +  CORTX core is a component of the new cloud software stack developed by Seagate
 +  CORTX provides basic functionality through its Motr client interface:
    +  object store

doc/Seagate-FDMI-HLD.md

@@ -1,38 +1,39 @@
 # High Level Design Specification  
-## Seagate FDMI  
 
-## Revision History
+## Seagate FDMI ##
+
+## Revision History ##
 |Date  | Revision History | Revision # | Comments         | Initials|
 |------| -----------------|------------| -----------------| --------|  
 |08/29/2014 | Major       | 1.0        |                  | IV      |  
 |         |  
 |         |  
 
 
-# Introduction
-## 1.1 Document's Purpose
+# Introduction #
+## 1.1 Document's Purpose ##
 The document is intended to specify the design of Mero FDMI interface. FDMI is a part of Mero product. FDMI provides interface for Mero plugins and allows horizontally extending the features and capabilities of the system.   
 
-## 1.2 Intended Audience
+## 1.2 Intended Audience ##
 * Product Architect
 * Developers
 * QA Engineers   
 
-## 1.3 Definitions, Acronyms, and Abbreviations
+## 1.3 Definitions, Acronyms, and Abbreviations ##
 FDMI: File data manipulation interface
 
-## 1.4 References
+## 1.4 References ##
 1. “Mero Object Store Architecture: Technical” MeroTechnicalWhitepaper.pdf
-1. “mero a scalable storage platform” Mero technical (toi).pdf
-1. fdmihighleveldecomposition.pdf	   
+2. “mero a scalable storage platform” Mero technical (toi).pdf
+3. fdmihighleveldecomposition.pdf	   
 
-# Overview
+# Overview #
 Mero is a storage core capable of deployment for a wide range of large scale storage regimes, from cloud and enterprise systems to exascale HPC installations. FDMI is a part of Mero core, providing interface for plugins implementation. FDMI is build around the core and allows for horizontally extending the features and capabilities of the system in a scalable and reliable manner.
 
-## 1.5 Product Purpose
+## 1.5 Product Purpose ##
 TBD
 
-## 1.6 Assumptions and Limitations
+## 1.6 Assumptions and Limitations ##
 TBD   
 
 # Architecture  
@@ -51,7 +52,7 @@ In this section only architectural information like the following is displayed b
 
 
 
-## 1.7 FDMI position in overall Mero Core design
+## 1.7 FDMI position in overall Mero Core design ##
 
 FDMI is an interface allowing Mero Core scale horizontally. The scaling includes two aspects:
 
@@ -74,7 +75,7 @@ Considering the amount of data Mero Core operates with it obvious that plug-in t
 
 Source in its turn refreshes its own subset of filters against the database. The subset is selected from overall filter set based on the knowledge about data types the source is able to feed FDMI with as well as operation with the data the source supports.   
 
-## 1.8 FDMI Roles
+## 1.8 FDMI Roles ##
 FDMI consists of APIs implementing particular roles in accordance with FDMI use cases. The roles are:
 
 * Plug-in dock, responsible for:
@@ -94,8 +95,8 @@ FDMI consists of APIs implementing particular roles in accordance with FDMI use
 
 ![image](./images/Image1.PNG)  
 
-## 1.9 FDMI Plugin dock  
-### 1.9.1 initialization   
+## 1.9 FDMI Plugin dock ##
+### 1.9.1 initialization ###
 
 ![image](./images/Image2_sequenceDiagram.PNG)    
 
@@ -111,7 +112,7 @@ Further initialization consists of registering a number of filters in  **filterd
     **NB:**
     TBD if we really need to determine the moment when all sources appear to be running filter sets consistent across the whole system. Currently we need to consider if Plug-in should be notified about this point.
 
-### 1.9.2 Data Processing  
+### 1.9.2 Data Processing ###
 ![image](./images/Image3_sequenceDiagram.PNG)   
 
 Remote FDMI instance running Source Dock role provides data payload via RPC channel. RPC sink calls back local FDMI
@@ -128,8 +129,8 @@ confirmation it deregisters the associated RPC sink and plug-in’s callback fun
 
 All registered sources are notified about changes in filter set, if any occurred as the result of plug-in coming off
 
-## 1.10  FDMI Source Dock  
-### 1.10.1 Initialization  
+## 1.10  FDMI Source Dock ##
+### 1.10.1 Initialization ###
 ![image](./images/Image5_sequenceDiagram.PNG)    
 
 * TBD where to validate, on Source side or inside FDMI  
@@ -138,7 +139,7 @@ Source registration starts with registering source callbacks in local FDMI insta
 As an optimization, execution plan could be built for every added filter to be kept along with the one. As an option, execution
 plan can be built on every data filtering action to trade off memory consumption for CPU ticks.  
 
-### 1.10.2 Input Data Filtering  
+### 1.10.2 Input Data Filtering ###
 ![image](./images/Image6_sequenceDiagram.PNG)  
 
 *In case of RPC channel failure, input data reference counter has to be decremented. TBD if this to be done explicitly or in context of
@@ -162,7 +163,7 @@ When done with traversing, FDMI engine calculates final Boolean result for the f
 
     The method “get next filter” is the place where the behavior is to be implemented.  
 
-### 1.10.3 Deferred Input Data Release  
+### 1.10.3 Deferred Input Data Release ###
 ![image](./images/Image7_DeferredInputDataRelease.PNG)   
 
 Input data may require to remain locked in the Source until the moment when plug-in does not need it anymore. The data processing inside plug-in is an asynchronous process in general, and plug-in is expected to notify corresponding source allowing it to release the data. The message comes from plug-in to FDMI instance hosting the corresponding source.  
@@ -171,7 +172,7 @@ Input data may require to remain locked in the Source until the moment when plug
     TBD: We need to establish a way to resolve resource id to FDMI instance hosting particular source. Most probably
     resource id itself may contain the information, easily deduced or calculated.  
 
-### 1.10.4 FDMI Service Found Dead  
+### 1.10.4 FDMI Service Found Dead ###
 ![image](./images/Image8_FDMIserviceFoundDead.PNG)