Update readme

Editorial review (structure, style, language, typos)

Author: lenkis

README.md

@@ -1,77 +1,95 @@
-You could get [1.6.9](https://github.com/tarantool/tarantool-java/tree/connector-1.6.9)
+<a href="http://tarantool.org">
+   <img src="https://avatars2.githubusercontent.com/u/2344919?v=2&s=250"
+align="right">
+</a>
 
-# Java Connector for Tarantool 1.7.4
+# Java connector for Tarantool 1.7.4+
 
 [![Join the chat at https://gitter.im/tarantool/tarantool-java](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/tarantool/tarantool-java?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
 
-## Problems & Questions
-http://stackoverflow.com/questions/ask/advice with tags `tarantool` and `java`.
+To get the Java connector for Tarantool 1.6.9, visit
+[this GitHub page](https://github.com/tarantool/tarantool-java/tree/connector-1.6.9).
 
-## Note
-Tarantool client is not supports name resolving for fields, indexes, space etc. I highly recommend to use server side lua to
-operate with named items. For example you could create dao object with simple CRUD functions.
-If you still need client name resolving for some reasons you could create function which will return required maps with name to id mappings.
+## Table of contents
+* [Getting started](#getting-started)
+* [Where to get help](#where-to-get-help)
 
-## How to start
+## Getting started
+
+1. Add a dependency to your `pom.xml` file.
 
-First you should add dependency to your pom file
 ```xml
 <dependency>
   <groupId>org.tarantool</groupId>
   <artifactId>connector</artifactId>
   <version>1.7.4</version>
 </dependency>
 ```
-Second configure TarantoolClientConfig.
+
+2. Configure `TarantoolClientConfig`.
 
 ```java
-     TarantoolClientConfig config = new TarantoolClientConfig();
-     config.username = "test";
-     config.password = "test";
+TarantoolClientConfig config = new TarantoolClientConfig();
+config.username = "test";
+config.password = "test";
 ```
 
-Then implements your SocketChannelProvider. SocketChannelProvider should return connected SocketChannel.
-Here you also could implement some reconnect or fallback policy. Remember that TarantoolClient uses [fail fast
-policy](https://en.wikipedia.org/wiki/Fail-fast) when client is not connected.
-
+3. Implement your `SocketChannelProvider`.
+   It should return a connected `SocketChannel`.
 
 ```java
-     SocketChannelProvider socketChannelProvider = new SocketChannelProvider() {
-                @Override
-                public SocketChannel get(int retryNumber, Throwable lastError) {
-                    if (lastError != null) {
-                        lastError.printStackTrace(System.out);
-                    }
-                    try {
-                        return SocketChannel.open(new InetSocketAddress("localhost", 3301));
-                    } catch (IOException e) {
-                        throw new IllegalStateException(e);
-                    }
-                }
-            };
+SocketChannelProvider socketChannelProvider = new SocketChannelProvider() {
+           @Override
+           public SocketChannel get(int retryNumber, Throwable lastError) {
+               if (lastError != null) {
+                   lastError.printStackTrace(System.out);
+               }
+               try {
+                   return SocketChannel.open(new InetSocketAddress("localhost", 3301));
+               } catch (IOException e) {
+                   throw new IllegalStateException(e);
+               }
+           }
+       };
 ```
 
-Now you are ready to create client
+Here you could also implement some reconnection or fallback policy.
+Remember that `TarantoolClient` adopts a
+[fail-fast](https://en.wikipedia.org/wiki/Fail-fast) policy
+when a client is not connected.
+
+4. Create a client.
+
 ```java
 TarantoolClient client = new TarantoolClientImpl(socketChannelProvider, config);
 ```
 
-TarantoolClient is thread safe and async so you should use one client inside whole application. 
+> **Notes:**
+> * `TarantoolClient` is thread-safe and asynchronous, so you should use one
+>   client inside the whole application.
+> * `TarantoolClient` does not support name resolution for fields, indexes,
+>   spaces and so on. We highly recommend to use server-side Lua when working
+>   with named items. For example, you could create a data access object (DAO)
+>   with simple CRUD functions. If, for some reason, you do need client name
+>   resolution, you could create a function that returns necessary name-to-ID
+>   mappings.
 
-TarantoolClient provides 3 interfaces to execute queries
+`TarantoolClient` provides three interfaces to execute queries:
 
-* SyncOps returns operation result
-* AsyncOps returns operation result Future
-* FireAndForgetOps returns query ID
+* `SyncOps` - returns the operation result
+* `AsyncOps` - returns the operation result as a `Future`
+* `FireAndForgetOps` - returns the query ID
 
+Feel free to override any method of `TarantoolClientImpl`. For example, to hook
+all the results, you could override this:
 
-Feel free to override any method of TarantoolClientImpl. For example you
-could override 
 ```java
 protected void complete(long code, FutureImpl<List> q);
 ```
-to hook all results.
-
-
 
+## Where to get help
 
+Got problems or questions? Post them on
+[Stack Overflow](http://stackoverflow.com/questions/ask/advice) with the
+`tarantool` and `java` tags, or use these tags to search the existing knowledge
+base for possible answers and solutions.