Merge pull request #18 from bringauto/readme_update_img

Readme - update img and TYPO changes

Author: koudis

README.md

@@ -1,6 +1,12 @@
 # Fleet Protocol
 
-Fleet Protocol is a communication technology developed by BringAuto to allow for **simple and reliable** communication between
+**Connect any device from anywhere to everywhere!**
+
+![Fleet Protocol](./doc/img/FleetProtocolImg.webp)
+
+## General
+
+Fleet Protocol is a **modular** communication technology developed by BringAuto to allow for **simple and reliable** communication between
 devices deployed in an **internet-connection-unstable** environment and cloud infrastructure.
 
 Protocol consists of three parts:
@@ -14,14 +20,13 @@ Protocol consists of three parts:
 
 ## Communication protocol
 
-We use the [ProtoBuf] library for message format (version [Protobuf version]) and serialization/deserialization - protocol
-specification
-can be found in protobuf folder.
+[ProtoBuf] (see [Protobuf version]) is used to serialize and deserialize messages. The message format
+specification can be found in the protobuf folder.
 
 Each message must be prefixed with a four bytes long (uint32_t data type) header, which holds
-information about the size of the ProtoBuf message.
+information about the size of the Protobuf message.
 
-To read more about the system architecture, check the Fleet Protocol v2 documentation:
+Check the Fleet Protocol v2 documentation to learn more about the system architecture:
 
 - [Summary] - overall high-level summary
 - [Fleet Protocol Requirements]
@@ -73,6 +78,9 @@ Optional fields have defaults as described in the [ProtoBuf] v3 doc.
 
 ## Repo structure
 
+This repository contains a basic C API and CMake project to easily
+implement Fleet Protocol Modules.
+
 ### Examples
 
 Samples of fleet-protocol features usage.