README.md in pod-builder-3.0.1 vs README.md in pod-builder-3.1.0

@@ -214,11 +214,11 @@
         }
     }
 }
 ```
 
-### `skip_pods`
+#### `skip_pods`
 
 You may want to skip some pods to be prebuilt, you can do that as follows:
 
 ```json
 {
@@ -227,11 +227,11 @@
         ]
 }
 ```
 
 
-### `force_prebuild_pods`
+#### `force_prebuild_pods`
 
 You may want to force some pods to be prebuilt, this might be the case for prebuilt ones (pods with a single vendored .framework) which are dependencies of othere pods
 
 ```json
 {
@@ -242,12 +242,14 @@
 ```
   
 
 #### `build_settings`
 
-Xcode build settings to use. You can override the default values which are:
+These settings allow you to specify the build settings to use when compiling prebuilt items. These values won't be reflected in your project once the pod has been built.
 
+You can override the default values which are:
+
 ```json
 {
     "build_settings": {
         "ENABLE_BITCODE": "NO",
         "GCC_OPTIMIZATION_LEVEL": "s",
@@ -360,10 +362,10 @@
 
 Please open an issue here. You may also add the name of the pod to the [`skip_pods`](#skip_pods) key in the configuration file and try rebuilding again.
 
 # Git LFS
 
-We high encourage to use PodBuilder in combination with Git LFS. Tacking PodBuilder/Prebuilt/**/*.framework/* and PodBuilder/Prebuilt/**/*.a and PodBuilder/dSYM/**/* will ensure that your repo size stays under control with all the benefits of having prebuilt dependencies ready to use.
+We high encourage to use PodBuilder in combination with Git LFS. Tacking `PodBuilder/Prebuilt/**/*.framework/*` and `PodBuilder/Prebuilt/**/*.a` and `PodBuilder/dSYM/**/*` will ensure that your repo size stays under control with all the benefits of having prebuilt dependencies ready to use.
 
 
 # Try it out!
 
 Under _Example_ there's a sample project with a Podfile adding [Alamofire](https://github.com/Alamofire/Alamofire) you can use to try PodBuilder out.