Merge branch 'master' into 0.9.5

.github/ISSUE_TEMPLATE

 Hi ! Thank you for reporting an issue, but we would like to remind you, we have a trouble shooting page in our wiki. You may want to take a look on that page :p 
 
+* please provide the version of installed library and RN project.
+* a sample code snippet/repository is very helpful to spotting the problem.
 * issues which have been tagged as 'needs feedback', will be closed after 2 weeks if receive no feedbacks.

.github/PULL_REQUEST_TEMPLATE

 Thank you for making a pull request ! Just a gentle reminder :)
 
 1. If the PR is offering a feature please make the request to our "Feature Branch" 0.10.0
-2. Bug fix request to "Bug Fix Branch" 0.9.4
+2. Bug fix request to "Bug Fix Branch" 0.9.5
 3. Correct README.md can directly to master

README.md

 
 A project committed to make file acess and data transfer easier, efficient for React Native developers.
 
+> The npm package is inside `src` folder, if you're going to install using github repository do not point to here directly
+
 ## Features
 - Transfer data directly from/to storage without BASE64 bridging
 - File API supports normal files, Asset files, and CameraRoll files
 - File stream support for dealing with large file
 - Blob, File, XMLHttpRequest polyfills that make browser-based library available in RN (experimental)
 
-> The npm package is inside `src` folder, if you're going to install via git repository do not directly poiint to this folder
-
 ## TOC
 * [About](#user-content-about)
 * [Installation](#user-content-installation)
  - Otherwise, if a string starts with `RNFetchBlob-file://` (which can simply done by `RNFetchBlob.wrap(PATH_TO_THE_FILE)`), it will try to find the data from the URI string after `RNFetchBlob-file://` and use it as request body. 
 - To send the body as-is, simply use a `Content-Type` header not containing `;BASE64` or `application/octet`.
 
+> It is Worth to mentioning that the HTTP request uses cache by default, if you're going to disable it simply add a Cache Control header `'Cache-Control' : 'no-store'` 
+
 > After 0.9.4, we disabled `Chunked` transfer encoding by default, if you're going to use it, you should explicitly set header `Transfer-Encoding` to `Chunked`.
 
 ### Download example : Fetch files that needs authorization token
     }),
     'Content-Type' : 'application/octet-stream',
     // here's the body you're going to send, should be a BASE64 encoded string
-    // (you can use "base64" APIs to make one).
+    // (you can use "base64"(refer to the library 'mathiasbynens/base64') APIs to make one).
     // The data will be converted to "byte array"(say, blob) before request sent.  
   }, base64ImageString)
   .then((res) => {
 
 ## Performance Tips
 
-**Reduce RCT Bridge and BASE64 Overheard**
+**Read Stream Event Overhead**
 
 When reading data via `fs.readStream` the process seems blocking JS thread when file is large, it's because the default buffer size is quite small (4kb) which result in large amount of events triggered in JS thread, try to increase the buffer size (for example 100kb = 102400) and set a larger interval (which is introduced in 0.9.4 default value is 10ms) to limit the frequency. 
 
+**Reduce RCT Bridge and BASE64 Overhead**
+
 React Native connects JS and Native context by passing JSON around React Native bridge, and there will be an overhead to convert data before they sent to each side. When data is large, this will be quite a performance impact to your app, it's recommended to use file storage instead of BASE64 if possible.The following chart shows how much faster when loading data from storage than BASE64 encoded string on iphone 6.
 
 <img src="img/performance_1.png" style="width : 100%"/>