Authored by Justin R. Miller

link to guide for install options

@@ -50,6 +50,8 @@ There are three ways that you can install the SDK, depending upon your needs: @@ -50,6 +50,8 @@ There are three ways that you can install the SDK, depending upon your needs:
50 1. Use the [binary framework](https://github.com/mapbox/mapbox-ios-sdk/tree/packaging/Downloads). Use like regular frameworks, linking it in your project, adding `#import <MapBox/MapBox.h>`, and additionally, including the `-ObjC` linker flag. 50 1. Use the [binary framework](https://github.com/mapbox/mapbox-ios-sdk/tree/packaging/Downloads). Use like regular frameworks, linking it in your project, adding `#import <MapBox/MapBox.h>`, and additionally, including the `-ObjC` linker flag.
51 1. Install via [CocoaPods](http://cocoapods.org). 51 1. Install via [CocoaPods](http://cocoapods.org).
52 52
  53 +More detailed information on the installation options is available in the [SDK guide](http://mapbox.com/mapbox-ios-sdk/).
  54 +
53 The two main branches of the GitHub repository are pretty self-explanatory: `release` and `develop`. When we tag a [release](https://github.com/mapbox/mapbox-ios-sdk/tags), we also merge `develop` over to `release`, except in the case of minor point releases (e.g., `0.4.2`), where we might just bring over a fix or two from `develop`. 55 The two main branches of the GitHub repository are pretty self-explanatory: `release` and `develop`. When we tag a [release](https://github.com/mapbox/mapbox-ios-sdk/tags), we also merge `develop` over to `release`, except in the case of minor point releases (e.g., `0.4.2`), where we might just bring over a fix or two from `develop`.
54 56
55 Then, update the submodules: 57 Then, update the submodules: