From da56a3595991afb91cb252863beab07cff29fe86 Mon Sep 17 00:00:00 2001 From: Mac Bellingrath Date: Mon, 4 Jun 2018 03:33:26 -0400 Subject: [PATCH] [FIX] correct typo in README (#1303) --- docs/api-ios.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-ios.md b/docs/api-ios.md index 0911cb5de..93d0403d8 100644 --- a/docs/api-ios.md +++ b/docs/api-ios.md @@ -12,7 +12,7 @@ The `CodePush` class' methods can be thought of as composite resolvers which alw 2. As soon as you begin releasing CodePush updates, your end-users will get the JS bundle that represents the latest release for the configured deployment. This is the behavior that allows you to iterate beyond what you shipped to the store. -3. As soon as you release an update to the app store (e.g. `1.1.0`), and your end-users update it, they will once again get the JS bundle that is contained within the binary. This behavior ensures that CodePush updates that targetted a previous app store version aren't used (since we don't know it they would work), and your end-users always have a working version of your app. +3. As soon as you release an update to the app store (e.g. `1.1.0`), and your end-users update it, they will once again get the JS bundle that is contained within the binary. This behavior ensures that CodePush updates that targetted a previous app store version aren't used (since we don't know if they would work), and your end-users always have a working version of your app. 4. Repeat #2 and #3 as the CodePush releases and app store releases continue on into infinity (and beyond?)