Added missing step to Cocoapods instructions and added recommendation…

… about committing pods.

README.md

@@ -60,18 +60,21 @@ To get started, move inside your iOS project folder and run
 
     pod init
 
-This creates a Podfile, which will hold all your dependencies in one place. You can then
+This creates a Podfile, which will hold all your dependencies in one place. After adding your dependencies to the Podfile, you run
 
     pod install
 
-to install these dependencies and include them as part of a workspace which also holds your own project. Note that from now on, you'll need to open the `.xcworkspace` file instead of `.xcproject`, or your code will not compile. The command
+to install the libraries and include them as part of a workspace which also holds your own project. It is generally [recommended to commit the installed dependencies to your own repo][committing-pods], instead of relying on having each developer running pod install after a fresh checkout.
+
+Note that from now on, you'll need to open the `.xcworkspace` file instead of `.xcproject`, or your code will not compile. The command
 
     pod update
 
 will update all pods to the newest versions permitted by the Podfile. You can use a wealth of [operators][cocoapods-pod-syntax] to specify your exact version requirements.
 
 [cocoapods]: http://www.cocoapods.org
 [cocoapods-pod-syntax]: http://guides.cocoapods.org/syntax/podfile.html#pod
+[committing-pods]: https://www.dzombak.com/blog/2014/03/including-pods-in-source-control.html
 
 ### Project Structure