- remove mentioning of the long gone ArangoDB 1.4
- swap sequence to first mention keepalive, then using it efficiently with async HTTP requests
- introduce the well known connection pool buzzword and howto use it best with keepalive and async HTTP
- mention in FOXX that this may also be a consideration here
- move the HTTP Basics above the API description
- mention that the user may also want to use the swagger.io interactive API-documentation in his ArangoDB
This answers the question and thus fixes#1533