CORTX-33702: Codacy cleanup of markdown files

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

Author: Rohan Dhodare

doc/FOPFOM-Programming-Guide.md

@@ -38,7 +38,7 @@ A .ff file should be compiled using ff2c compiler.
 After writing FOPs and creating .ff file for a particular module, we need to make an entry for the same in the module's Makefile.am file. This would automatically invoke ff2c on the .ff files and create corresponding “C” format structures.
 
 ** A FOP, containing native data types in file fom_io_xc.ff:**  
-```  
+```C  
 record {
         u64 f_seq;
         u64 f_oid

doc/HLD-OF-Motr-LNet-Transport.md

@@ -140,7 +140,7 @@ See Support for multiple message delivery in a single network buffer.
 
 The design provides an API for the higher level application to associate the internal threads used by a transfer machine with a set of processors. In particular the API guarantees that buffer and transfer machine callbacks will be made only on the processors specified.
 
-```
+```C
 #include “lib/processor.h”
 
 ...

doc/HLD-of-Catalogue-Service.md

@@ -147,7 +147,7 @@ Deathrow catalogue contains all large catalogues which are in the process of bei
 
 GET	cfid, input: array of {key	rc, output: array of {exists, val}
 
-```
+```C
 cat = catalogue_get(req.cfid);
 
 foreach key in req.input {

doc/Motr-Epochs-HLD.md

@@ -74,7 +74,7 @@ EpochTransitionRequest { service :: ServiceId
                        , targetEpoch  :: EpochId }
 ```
 HA services that wrap Motr services must be able to accept the following additional messages:
-```
+```Text
 EpochTransition { targetEpoch            :: EpochId
 
                 , epochTransitionPayload :: a }  

doc/Motr-Lnet-Transport.md

@@ -140,7 +140,7 @@ See Support for multiple message delivery in a single network buffer.
 
 The design provides an API for the higher level application to associate the internal threads used by a transfer machine with a set of processors. In particular the API guarantees that buffer and transfer machine callbacks will be made only on the processors specified.
 
-```
+```C
 #include “lib/processor.h”
 
 ...

doc/Running_Motr_Across_a_Cluster.md

@@ -102,8 +102,8 @@ This document provides information on how to build motr from source and then run
 	                 #  - name: default
 	                 #    pools: [ the pool ]
                 ```
-            > Whereas a CDF with 3 nodes should look like this:
-               
+             Whereas a CDF with 3 nodes should look like this:
+               	```sh
                 # Cluster Description File (CDF).
                 # See `cfgen --help-schema` for the format description.
                 nodes:
@@ -201,8 +201,7 @@ This document provides information on how to build motr from source and then run
 	                 #profiles:
 	                 #  - name: default
 	                 #    pools: [ the pool ]
-                      
-
+         ```
 4. ### Disable the firewall on each node:
     This is needed by s3 server, no need to do this if you don't have s3 client (`s3: 0`) on the CDF (at `m0_clients` section).
     ```sh

doc/Seagate-FDMI-HLD.md

@@ -121,7 +121,7 @@ the data to plug-in instance.
 
 Successful data processing results in returning acknowledge along with confirmation allowing data release, if required.  
 
-### 1.9.3 De-initialization  
+### 1.9.3 De-initialization ###
 ![image](./images/Image4_sequenceDiagram.PNG)    
 
 Plug-in initiates de-initialization by calling local FDMI. The latter deregisters plug-in’s filter set with filtered service. After

doc/motr-kv-app.md

@@ -17,7 +17,7 @@ Init the m0\_idx struct with m0\_idx\_init().
 
 Init the index create operation with m0\_entity\_create().
 
-```
+```Text
 An ID is needed for this index. In this example, ID is configured from command line.
 Developers are responsible to generate an unique ID for their indices.
 ```

doc/motr-object-app.md

@@ -31,7 +31,7 @@ Motr applications. Please refer to source code "lib/"
 
 Define necessary variables (global or in main() function)
 
-```
+```C
     static struct m0_client         *m0_instance = NULL;
     static struct m0_container       motr_container;
     static struct m0_config          motr_conf;
@@ -40,7 +40,7 @@ Define necessary variables (global or in main() function)
 
 Get configuration arguments from command line
 
-```
+```C
 
 #include "motr/client.h"
 

scripts/provisioning/README.md

@@ -333,7 +333,7 @@ which is more convenient:
     ```
 
 The `m0vg` helper script is a wrapper around _Vagrant_ and _Ansible_ commands
-that can be *symlinked* somewhere into the `PATH` and be called from any
+that can be **symlinked** somewhere into the `PATH` and be called from any
 directory. Check out `m0vg --help` for more info.
 
 It will spawn a VM and configure it using _Ansible_ "playbook"
@@ -354,7 +354,9 @@ below for the list of other useful _Vagrant_ commands.
 
 If a cluster-like environment is needed, more machines can be provisioned:
 
-    ./scripts/m0vg up cmu /ssu/ /client/
+```Text
+./scripts/m0vg up cmu /ssu/ /client/
+```
 
 The additional parameters are also explained in the _Vagrant basics_ section
 below.