message: added note about PoolLedgerTimeout error
diff: @@ -217,6 +217,8 @@ If you would like to analyse CPU performance of libindy for your use case, you h
  ## How to start local nodes pool with docker
  To test the SDK codebase with a virtual Indy node network, you can start a pool of local nodes using docker:
  +**Note: If you are getting a PoolLedgerTimeout error it's because the IP addresses in /indy-sdk/cli/docker_pool_transactions_genesis and the pool configuration don't match. Use method 3 to configure the IPs of the docker containers to match the pool.**
  +
  ### 1) Starting the test pool on localhost
  Start the pool of local nodes on `127.0.0.1:9701-9708` with Docker by running:
  @@ -225,6 +227,8 @@ docker build -f ci/indy-pool.dockerfile -t indy_pool .
  docker run -itd -p 9701-9708:9701-9708 indy_pool
  ```
  +*Note: If you are getting a PoolLedgerTimeout Error it's because the IP Addresses in .*
  +
  ### 2) Starting the test pool on a specific IP address
  Dockerfile `ci/indy-pool.dockerfile` supports an optional pool_ip param that allows
  changing ip of pool nodes in generated pool configuration.
  @@ -237,8 +241,7 @@ docker run -itd -p 9701-9708:9701-9708 indy_pool
  docker build --build-arg pool_ip=192.168.179.90 -f ci/indy-pool.dockerfile -t indy_pool .
  docker run -itd -p 192.168.179.90:9701-9708:9701-9708 indy_pool
  ```
  - To connect to the pool the IP addresses in /var/lib/indy/sandbox/pool_transactions_genesis (in docker) and the
  - pool configuration you use in your mobile app must match.
  + To connect to the pool the IP addresses in /var/lib/indy/sandbox/pool_transactions_genesis (in docker) and the pool configuration you use in your mobile app must match.
  ### 3) Starting the test pool on a docker network
  The following commands allow to start local nodes pool in custom docker network and access this pool
  