message: Reword MacOS Installation guide
diff: @@ -15,7 +15,7 @@ in project IS (note that regular Indy tickets are in the INDY project instead...
  us on [Hyperledger's Rocket.Chat](https://chat.hyperledger.org/) at #indy-sdk to discuss.
  -## How to install
  +## Installation
  ### Release channels
  Indy SDK release process defines the following release channels:
  @@ -24,7 +24,8 @@ Indy SDK release process defines the following release channels:
  * `stable` - stable releases.
  Please refer to [release workflow](doc/release-workflow.md) for more details.
  -### Install for Ubuntu based distro (Ubuntu 16.04)
  +
  +### Ubuntu based distributions (Ubuntu 16.04)
  It is recommended to install packages with APT:
  apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 68DB5E88
  @@ -35,14 +36,13 @@ It is recommended to install packages with APT:
  {release channel} must be replaced with master, rc or stable to define corresponded release channel.
  See section "Release channels" for more details.
  -### Install for Windows
  +### Windows
  1. follow to https://repo.sovrin.org/windows/libindy/{release-channel}.
  2. download last version of libindy.
  3. unzip archives to directory, where you want to save working library.
  4. After unzip you will get next structure of files:
  -
  * `Your working directory`
  * `include`
  * `...`
  @@ -62,20 +62,22 @@ that may be need for your applications.
  {release channel} must be replaced with master, rc or stable to define corresponded release channel.
  See section "Release channels" for more details.
  -### Install for iOS
  +### iOS
  See [wrapper iOS install documentation](wrappers/ios/README.md "How to install").
  -### Install for MacOS
  -Now we haven't prebuild library in some shared place. You can build
  -library yourself. Please refer to How-to-build section.
  +### MacOS
  +
  +Pre-built libraries are not provided for MacOS. Please look [here](blob/master/doc/mac-build.md)
  +for details on building from source for MacOS.
  -After build add to LD_LIBRARY_PATH and to DYLD_LIBRARY_PATH
  -environment variables path to builded library. It's necessary
  -for dynamic linkage your application with libindy. At first dynamic linker
  -browse library in LD_LIBRARY_PATH, if library in your application doesn't include directory names.
  -If library in your application include any directory name, then dynamic linker will search library
  -in DYLD_LIBRARY_PATH(not LD_LIBRARY_PATH). So for reliability we recommend you set both this variables.
  +After building `libindy`, add the path containing the library the `LD_LIBRARY_PATH` and
  +`DYLD_LIBRARY_PATH` environment variables. This is necessary for dynamically linking
  +your application with `libindy`. The dynamic linker will first check for the library in
  +`LD_LIBRARY_PATH` if the library in your application doesn't include directory names.
  +If the library in your application does include any directory name, then dynamic
  +linker will search for the library in `DYLD_LIBRARY_PATH` (not `LD_LIBRARY_PATH`)
  +so we recommend you set both variables to be safe.
  ### Install for RHEL based distro (Amazon Linux 2017.03)
  Now we haven't prebuild library in some shared place. You can build
  