diff --git a/README.md b/README.md
index a95618a..54af054 100644
--- a/README.md
+++ b/README.md
@@ -290,7 +290,7 @@ The simplest way to do this is to perform the following in your app's root compo
If an update is available, it will be silently downloaded, and installed the next time the app is restarted (either explicitly by the end user or by the OS), which ensures the least invasive experience for your end users. If you would like to display a confirmation dialog (an "active install"), or customize the update experience in any way, refer to the `sync` method's [API reference](#codepushsync) for information on how to tweak this default behavior.
-*NOTE: While [Apple's developer agreement](https://developer.apple.com/programs/ios/information/iOS_Program_Information_4_3_15.pdf) fully allows performing over-the-air updates of JavaScript and assets, we have seen a few isolated incidents where they have rejected apps due to displaying an update prompt. In each instance, once the app supressed the dialog, and was re-submitted to the store, it was approved. Because of this, we recommend that App Store-distributed apps don't enable the `updateDialog` option when calling `sync`, whereas Google Play and internally distributed apps (e.g. Enterprise, Fabric, HockeyApp) can choose to freel y enable/customize it.*
+*NOTE: While [Apple's developer agreement](https://developer.apple.com/programs/ios/information/iOS_Program_Information_4_3_15.pdf) fully allows performing over-the-air updates of JavaScript and assets, we have seen a few isolated incidents where they have rejected apps due to displaying an update prompt. In each instance, once the app supressed the dialog, and was re-submitted to the store, it was approved. Because of this, we recommend that App Store-distributed apps don't enable the `updateDialog` option when calling `sync`, whereas Google Play and internally distributed apps (e.g. Enterprise, Fabric, HockeyApp) can choose to enable/customize it.*
## Releasing Updates (JavaScript-only)