README.md in cocoapods-binaryhqp-0.5.1 vs README.md in cocoapods-binaryhqp-0.5.2

@@ -31,20 +31,21 @@
 
 Then in the flowing normal install process, we hook the integration functions to modify pod specification to using our frameworks.
 
 ## Installation
 
-## 编译方法
-sudo gem build cocoapods-binaryhqp.gemspec && sudo gem install cocoapods-binaryhqp-0.4.7.gem
+## 安装方法 
 
+sudo gem install cocoapods-binaryhqp
+
+
 ## Usage
 
 ``` ruby
-plugin 'cocoapods-binary'
+plugin 'cocoapods-binaryhqp'
 
 use_frameworks!
-# all_binary!
 
 target "HP" do
     pod "ExpectoPatronum", :binary => true
 end
 ```
@@ -52,9 +53,13 @@
 - Add `plugin 'cocoapods-binary'` in the head of Podfile 
 - Add `:binary => true` as a option of one specific pod, or add `all_binary!` before all targets, which makes all pods binaries.
 - pod install, and that's all
 
 **Note**: cocoapods-binary require `use_frameworks!`. If your worry about the boot time and other problems introduced by dynamic framework, static framework is a good choice. Another [plugin](https://github.com/leavez/cocoapods-static-swift-framework) made by me to make all pods static frameworks is recommended.
+
+## 全部使用源码
+ - pod install --hsource
+ 
 
 #### Options
 
 If you want to disable binary for a specific pod when using `all_binary!`, place a `:binary => false` to it.