README.md in sigh-0.1.2 vs README.md in sigh-0.1.3

@@ -19,11 +19,11 @@
 [![Twitter: @KauseFx](https://img.shields.io/badge/[e-mail]?style=flat)](https://twitter.com/KrauseFx)
 [![License](http://img.shields.io/badge/license-MIT-green.svg?style=flat)](https://github.com/KrauseFx/sigh/blob/master/LICENSE)
 [![Gem](https://img.shields.io/gem/v/sigh.svg?style=flat)](http://rubygems.org/gems/sigh)
 
 
-Tired of manually creating, renewing and downloading your provisioning profiles?
+Tired of manually creating, renewing and downloading your iOS provisioning profiles?
 
 ```sigh``` handles all that for you. Just run ```sigh``` and it will do the rest.
 
 Follow the developer on Twitter: [@KrauseFx](https://twitter.com/KrauseFx)
 
@@ -50,13 +50,15 @@
 - Supports **App Store**, **Ad Hoc** and **Development** profiles
 - Support for **multiple Apple accounts**, storing your credentials securely in the Keychain
 - Support for **multiple Teams**
 - Support for Enterprise Profiles
 
+To automate iOS Push profiles you can use [PEM](https://github.com/KrauseFx/PEM).
+
 ### Why not let Xcode do the work?
 
 - ```sigh``` can easily be integrated into your CI-server (e.g. Jenkins)
-- Xcode sometimes invalidates all existing profiles ([Proof](assets/SignErrors.png))
+- Xcode sometimes invalidates all existing profiles ([Screenshot](assets/SignErrors.png))
 - You have control over what happens
 - You still get to have the signing files, which you can then use for your build scripts or store in git
 
 See ```sigh``` in action: