Merge pull request #60 from yuriy-glotanov/2021.1

README.md fix

Author: interference-project

README.md

@@ -13,9 +13,9 @@ contacts: info@inteference.su
 
 ## Concepts & features
 
-######i.o.cluster also known as interference open cluster is a simple java framework enables you to launch a distributed database and complex event processing service within your java application, using JPA-like interface and annotations for structure mapping and data operations. This software inherits its name from the interference project, within which its mechanisms were developed.
+###### i.o.cluster also known as interference open cluster is a simple java framework enables you to launch a distributed database and complex event processing service within your java application, using JPA-like interface and annotations for structure mapping and data operations. This software inherits its name from the interference project, within which its mechanisms were developed.
 
-######i.o.cluster is a opensource, pure java software.
+###### i.o.cluster is a opensource, pure java software.
 
 The basic unit of the i.o.cluster service is a node - it can be a standalone running service, or a service running within some java application.
 
@@ -39,7 +39,7 @@ Nodes can be joined into a cluster, at the cluster level with inter-node interac
 - support of complex event processing (CEP) and simple streaming SQL
 - i.o.cluster nodes does not require the launch of any additional coordinators
 
-##Overview
+## Overview
 
 Initially, the service was designed in such a way that each node is a java application that can be launched both by sharing one JVM with the client application using the service, or autonomously.
 
@@ -58,7 +58,7 @@ a brief diagram of the internal implementation of the service on the example of
 
 ![Screenshot](doc/interference.png)
 
-##Distributed persistent model
+## Distributed persistent model
 
 To include a node in the cluster, you must specify the full list of cluster nodes (excluding this one) in the cluster.nodes configuration parameter. The minimum number of cluster nodes is 2, and the maximum is 64 (for more details, see cluster configuration rules below).
 
@@ -70,7 +70,7 @@ Within the framework of these rules, all nodes of the Interference open cluster
 
 Running commit in a local user session automatically ensures that the changed data is visible on all nodes in the cluster.
 
-##Distribute rules
+## Distribute rules
 
 The concept of interference open cluster is based on a simple basic requirement, which can be literally expressed as follows: we must allow insertion and modification of data at the cluster level from any node, and we must allow data retrieval from any node, using as much as possible the computing resources of the cluster as a whole. Further, we accept the condition that all cluster nodes must be healthy and powered on, if any of the nodes has been turned off for a while, it will not be turned on to receive data until her storage is synchronized with other nodes. In practice, in the absence of changes in the moment, this means that there are identical copies of the storage on the cluster nodes. To prevent conflicts of changes in cluster, several lock modes are used:
 
@@ -92,12 +92,12 @@ Thus, let's repeat again:
 - the cluster uses the generation of unique identifiers for entities (@DistributedId annotation) so that the identifier is unique within the cluster, but not just within the same node
 - the cluster does not use any additional checks for uniqueness, requiring locks at the cluster level
 
-##SQL horizontal-scaling queries
+## SQL horizontal-scaling queries
 
 All SQL queries called on any of the cluster nodes will be automatically distributed among the cluster nodes for parallel processing, if such a decision is made by the node based on the analysis of the volume of tasks (the volume of the query tables is large enough, etc.)
 If during the processing of a request a node is unavailable, the task distributed for this node will be automatically rescheduled to another available node.
 
-##Complex event processing concepts
+## Complex event processing concepts
 
 So, we must allow insertion and modification of data at the cluster level from any node, and we must allow data retrieval from any node, using as much as possible the computing resources of the cluster as a whole.