anchor.diff:  The server is configured with `TextWire`, so
   the client must also be configured with `TextWire`. The port that we will use will be ( in this example ) determined
   by the `TCPRegistry`, of course in a real life production environment you may decide not to use the
  -`TcpRegistry` or if you still use the `TcpRegistry` you can use a fixed host:port.
  +`TCPRegistry` or if you still use the `TCPRegistry` you can use a fixed host:port.
   
   [source,java]
   ----
  
positive.code: 
  ==== Create and Start the Client
  
  The client code that creates the `TcpChannelHub`,
  
  The `TcpChannelHub` is used to send your messages to the server and then read the servers response.
  
  The `TcpChannelHub` ensures that each response is marshalled back onto the appropriate client thread.
  It does this through the use of a unique transaction ID ( we call this transaction ID the "tid" ),
   when the server responds to the client, its expected that the server sends back the tid as the very first field in the message.
  
negative.code: 
  == Server Threading Strategy
  
  By default the Chronicle Network server uses a single thread to process all messages.
  However, if you wish to dedicate each client connection to its own thread,
  then you can change the server threading strategy, to:
  
  