Update documentation

README.md

@@ -21,7 +21,7 @@ To make your scheme shared go to "Manage schemes" in Xcode and tick "Shared" che
 
 
 ### what is this `plist_build_setting_support` stuff about?!
-If you have a xcodeproject and have updated to Xcode 11, you'll notice that if you change your build and version numbers through the UI, the actual numbers are now stored inside build settings inside build confiugration. The Info.plist file -- where they used to be stored -- now contains build setting variables (looks like `$(CURRENT_PROJECT_VERSION)` or `$(MARKETING_VERSION)`, for build number and version number respectively).
+If you have a xcodeproject and have updated to Xcode 11, you'll notice that if you change your build and version numbers through the UI, the actual numbers are now stored inside build settings inside build configuration. The Info.plist file -- where they used to be stored -- now contains build setting variables (looks like `$(CURRENT_PROJECT_VERSION)` or `$(MARKETING_VERSION)`, for build number and version number respectively).
 If you are at this migration 'turning point', you have two options. you can either:
 
 - Continue using the legacy method of inserting build and versions directly into plists by simply add `plist_build_setting_support: true` to your plist action parameters
@@ -35,8 +35,6 @@ Verify your plist files are using the build variables (new) `$(CURRENT_PROJECT_V
 
 We will leave the plist actions in, as for those consumers who are limited to their upgrade path.
 
-
-
 ## Actions
 
 ### increment_version_number_in_plist