Fix markdown warnings

Signed-off-by: Cervenka Dusan <[email protected]>

Author: Hadatko

CONTRIBUTING.md

@@ -1,3 +1,3 @@
-#Contribution
+# Contribution
 
 Contribution details are described in our [wiki/Contributing](https://github.com/EmbeddedRPC/erpc/wiki/Contributing)

README.md

@@ -1,11 +1,11 @@
+# eRPC
+
 [![Version](https://img.shields.io/github/v/release/EmbeddedRPC/erpc)](https://github.com/EmbeddedRPC/erpc/releases/latest)
 [![Contributors](https://img.shields.io/github/contributors/EmbeddedRPC/erpc)](https://github.com/EmbeddedRPC/erpc/graphs/contributors)
 [![Issues](https://img.shields.io/github/issues/EmbeddedRPC/erpc)](https://github.com/EmbeddedRPC/erpc/issues)
 [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](https://github.com/EmbeddedRPC/erpc/pulls)
 [![Gitpod ready-to-code](https://img.shields.io/badge/Gitpod-ready--to--code-blue?logo=gitpod)](https://gitpod.io/#https://github.com/EmbeddedRPC/erpc)
 
-# eRPC
-
 eRPC (Embedded RPC) is an open source Remote Procedure Call (RPC) system for multichip embedded systems and heterogeneous multicore SoCs.
 
 Unlike other modern RPC systems, such as the excellent [Apache Thrift](http://thrift.apache.org), eRPC distinguishes itself by being designed for tightly coupled systems, using plain C for remote functions, and having a small code size (<5kB). It is not intended for high performance distributed systems over a network.
@@ -16,7 +16,7 @@ A code generator tool called `erpcgen` is included. It accepts input IDL files,
 
 Example `.erpc` file:
 
-~~~~~{java}
+```java
 // Define a data type.
 enum LEDName { kRed, kGreen, kBlue }
 
@@ -25,10 +25,11 @@ interface IO {
     // Simple function declaration with an empty reply.
     set_led(LEDName whichLed, bool onOrOff) -> void
 }
-~~~~~
+```
 
 Client side usage:
-~~~~~{c}
+
+```C
 void example_client(void) {
     // Initialize client running over UART.
     erpc_client_init(
@@ -38,10 +39,11 @@ void example_client(void) {
     // Now we can call the remote function to turn on the green LED.
     set_led(kGreen, true);
 }
-~~~~~
+```
 
 Server side usage:
-~~~~~{c}
+
+```C
 // Implement the remote function.
 void set_led(LEDName whichLed, bool onOrOff) {
     // implementation goes here
@@ -59,7 +61,7 @@ void example_server(void) {
     // Run the server.
     erpc_server_run();
 }
-~~~~~
+```
 
 A number of transports are supported, and new transport classes are easy to write.
 
@@ -90,16 +92,23 @@ eRPC is available with an unrestrictive BSD 3-clause license. See the [LICENSE f
 
 [Example IDL](examples/README.md) is available in the `examples/` folder.
 
-Plenty of eRPC multicore and multiprocessor examples can be also found in NXP MCUXpressoSDK packages. Visit [https://mcuxpresso.nxp.com](https://mcuxpresso.nxp.com) to configure, build and download these packages.<br>
-To get the board list with multicore support (eRPC included) use filtering based on Middleware and search for 'multicore' string. Once the selected package with the multicore middleware is downloaded, see<br>
-<MCUXpressoSDK_install_dir>/boards/<board_name>/multicore_examples for eRPC multicore examples (RPMsg_Lite or Messaging Unit transports used) or<br>
-<MCUXpressoSDK_install_dir>/boards/<board_name>/multiprocessor_examples for eRPC multiprocessor examples (UART or SPI transports used).<br>
+Plenty of eRPC multicore and multiprocessor examples can be also found in NXP MCUXpressoSDK packages. Visit [https://mcuxpresso.nxp.com](https://mcuxpresso.nxp.com) to configure, build and download these packages.
+
+To get the board list with multicore support (eRPC included) use filtering based on Middleware and search for 'multicore' string. Once the selected package with the multicore middleware is downloaded, see
+
+<MCUXpressoSDK_install_dir>/boards/<board_name>/multicore_examples for eRPC multicore examples (RPMsg_Lite or Messaging Unit transports used) or
+
+<MCUXpressoSDK_install_dir>/boards/<board_name>/multiprocessor_examples for eRPC multiprocessor examples (UART or SPI transports used).
+
 eRPC examples use the 'erpc_' name prefix.
 
 Another way of getting NXP MCUXpressoSDK eRPC multicore and multiprocessor examples is using the [mcux-sdk](https://github.com/NXPmicro/mcux-sdk) Github repo. Follow the description how to use the West tool
-to clone and update the mcuxsdk repo in [readme Overview section](https://github.com/NXPmicro/mcux-sdk#overview). Once done the armgcc eRPC examples can be found in<br>
-mcuxsdk/examples/<board_name>/multicore_examples or in<br>
-mcuxsdk/examples/<board_name>/multiprocessor_examples folders.<br>
+to clone and update the mcuxsdk repo in [readme Overview section](https://github.com/NXPmicro/mcux-sdk#overview). Once done the armgcc eRPC examples can be found in
+
+mcuxsdk/examples/<board_name>/multicore_examples or in
+
+mcuxsdk/examples/<board_name>/multiprocessor_examples folders.
+
 You can use the evkmimxrt1170 as the board_name for instance. Similar to MCUXpressoSDK packages the eRPC examples use the 'erpc_' name prefix.
 
 ## References
@@ -132,7 +141,6 @@ This section provides links to interesting erpc-based projects, articles, blogs
 
 `utilities` - Holds utilities which bring additional benefit to eRPC apps developers.
 
-
 ## Building and installing
 
 These build instructions apply to host PCs and embedded Linux. For bare metal or RTOS embedded environments, you should copy the `erpc_c` directory into your application sources.
@@ -153,6 +161,7 @@ Steps are described in [`erpcgen/VisualStudio_v14/readme_erpcgen.txt`](erpcgen/V
 #### Linux and Cygwin
 
 Install these packages:
+
 * bison: GNU yacc-compatible parser generator
 * flex: A fast lexical analyzer generator
 * libboost-dev, libboost-filesystem-dev, libboost-system-dev: Boost C++ libraries (Linux needs to use libboost version 1.65.0)
@@ -162,12 +171,14 @@ Install these packages:
 * g++-7: GNU C++ compiler (recommended version)
 
 Mandatory for case, when build for different architecture is needed
+
 * gcc-multilib, g++-multilib
 * boost libraries: for target architecture like libboost-filesystem-dev:i386 libboost-system-dev:i386
 
 #### Mac OS X
 
 Install these packages with [homebrew](http://brew.sh/):
+
 * bison: GNU yacc-compatible parser generator (version 3.7.3 is recommended)
 * flex: A fast lexical analyzer generator (version 2.6.4 is recommended)
 * boost: Boost C++ libraries (version 1.74 is recommended)
@@ -176,24 +187,31 @@ Install these packages with [homebrew](http://brew.sh/):
 
 To build the library and erpcgen, run from the repo root directory:
 
-    % make
+```sh
+make
+```
 
 To install the library, erpcgen, and include files, run:
 
-    % make install
+```sh
+make install
+```
 
 You may need to sudo the `make install`.
 
 By default this will install into `/usr/local`. If you want to install elsewhere, set the `PREFIX` environment variable. Example for installing into `/opt`:
 
-    % make install PREFIX=/opt
+```sh
+make install PREFIX=/opt
+```
 
 List of top level Makefile targets:
-- `erpc`: build the liberpc.a static library
-- `erpcgen`: build the erpcgen tool
-- `test`: build the unit tests under the `test/` directory
-- `all`: build all of the above
-- `install`: install liberpc.a, erpcgen, and include files
+
+* `erpc`: build the liberpc.a static library
+* `erpcgen`: build the erpcgen tool
+* `test`: build the unit tests under the `test/` directory
+* `all`: build all of the above
+* `install`: install liberpc.a, erpcgen, and include files
 
 eRPC code is validated with respect to the C++ 11 standard.
 
@@ -202,7 +220,8 @@ eRPC code is validated with respect to the C++ 11 standard.
 To install the Python infrastructure for eRPC see instructions in the [erpc_python folder readme](erpc_python/readme.md).
 
 ## Known issues and limitations
-- Static allocations controlled by the ERPC_ALLOCATION_POLICY config macro are not fully supported yet, i.e. not all erpc objects can be allocated statically now. It deals with the ongoing process and the full static allocations support will be added in the future.
+
+* Static allocations controlled by the ERPC_ALLOCATION_POLICY config macro are not fully supported yet, i.e. not all erpc objects can be allocated statically now. It deals with the ongoing process and the full static allocations support will be added in the future.
 
 ## Code providing
 

doxygen/mainpage_erpcgen.md

@@ -1,4 +1,3 @@
-About eRPC generator                         {#mainpage}
-====================
+# About eRPC generator                         {#mainpage}
 
 The eRPC generator (erpcgen) is a tool which generates the shim code for a server and client side. The generated shim code handles marshaling and unmarshaling a request. On the server side after unmarshaling, it implements a function call to the appropriate function based on request. An IDL (Interface Definition Language) is used to tell the generator tool about data types and RPC services.

erpc_python/README_Pypi.md

@@ -1,9 +1,8 @@
-eRPC Python Infrastructure
-==========================
+# eRPC Python Infrastructure
 
 This folder contains the Python implementation of the eRPC infrastructure.
 
-The eRPC project is stored on Github: https://github.com/EmbeddedRPC/erpc
+The eRPC project is stored on Github: [github.com/EmbeddedRPC/erpc](https://github.com/EmbeddedRPC/erpc)
 
 The Python implementation of eRPC is fully compatible with the C/C++ implementation at the
 protocol level. Also, the classes mirror those in the C++ infrastructure.
@@ -12,12 +11,14 @@ Installation:
 
    To install the eRPC Python infrastructure, run the setup.py script like this:
 
-       pip install erpc
-
+```sh
+pip install erpc
+```
 
    Once installed, you can access the infrastructure via a standard import statement.
 
-       import erpc
-       xport = erpc.transport.SerialTransport("/dev/ttyS1", 115200)
-       client = erpc.client.ClientManager(xport, erpc.basic_codec.BasicCodec)
-
+```python
+import erpc
+xport = erpc.transport.SerialTransport("/dev/ttyS1", 115200)
+client = erpc.client.ClientManager(xport, erpc.basic_codec.BasicCodec)
+```

erpc_python/readme.md

@@ -1,12 +1,10 @@
-eRPC Python Infrastructure
-==========================
+# eRPC Python Infrastructure
 
 This folder contains the Python implementation of the eRPC infrastructure.
 
 The Python implementation of eRPC is fully compatible with the C/C++ implementation at the
 protocol level. Also, the classes mirror those in the C++ infrastructure.
 
-
 ## Contents
 
 `erpc` - Python package for eRPC infrastructure.
@@ -19,22 +17,28 @@ protocol level. Also, the classes mirror those in the C++ infrastructure.
 
 Pip package installer needs to be installed in your Python version. Use following way for Python3 pip installation:
 
-    sudo apt-get install python3-pip
-    /usr/bin$ sudo rm python
-    /usr/bin$ sudo ln -s python3 python
+```sh
+sudo apt-get install python3-pip
+/usr/bin$ sudo rm python
+/usr/bin$ sudo ln -s python3 python
+```
 
 To install the eRPC Python infrastructure, run the setup.py script like this (based on your system admin rights are required):
 
-    python setup.py install
+```sh
+python setup.py install
+```
 
 Alternatively, you may use pip to install the package, like this:
 
-    pip install .
-
+```sh
+pip install .
+```
 
 Once installed, you can access the infrastructure via a standard import statement.
 
-    >>>import erpc
-    >>>xport = erpc.transport.SerialTransport("/dev/ttyS1", 115200)
-    >>>client = erpc.client.ClientManager(xport, erpc.basic_codec.BasicCodec)
-
+```python
+import erpc
+xport = erpc.transport.SerialTransport("/dev/ttyS1", 115200)
+client = erpc.client.ClientManager(xport, erpc.basic_codec.BasicCodec)
+```