guess what? more text

README.md

@@ -32,7 +32,7 @@ YAML
 It provides the following commands on the messaging service:
 Link
 
-## Gameserver joining Bot
+## The gameserver joining bots
 
 A gameserver joining bot joins the gameservers by whatever means
 the gameserver protocol allows and then allows commands to be used
@@ -54,7 +54,7 @@ network commands.
 It provides the following commands on the messaging service:
 Link
 
-## Portal Websites
+## The portal websites
 
 ### PHP Client
 
@@ -64,7 +64,7 @@ network messages.
 
 Link
 
-## Control Server
+## The Control Server
 
 The "Control Server" merely is a client on the messaging service. But since
 it is the portion that actually helps forming processes between the other clients, we began calling
@@ -77,14 +77,14 @@ IP addresses to nice short names and countries.
 It provides the following commands on the messaging service:
 Link
 
-## Messaging Service
+## The transport layer
 
 Every client connects (or _can_ connect) to a messaging service where they can interact
-with a command and control server program and the other clients. It is the communication
-backbone. So to say, it's the transport of the messages with
-which the programs interact. Let's say 'message transport' is a
-synonym and 'network commands' are the commands that all the clients
-adhere to within the Community Messaging Project.
+with the other clients. It is the communication
+backbone. So to say, it's the transport laer of the messages with
+which the programs interact. Let's say 'message transport' and 'messaging service' are
+synonyms and 'network commands' are the commands that clients chose to provide and 
+request on each other within the Community Messaging Project.
 
 As a future (late 2017?) underlying message transport I chose NATS from Apcera. 
 https://nats.io