Skip to content
This repository was archived by the owner on May 20, 2025. It is now read-only.

Commit da56a35

Browse files
[FIX] correct typo in README (#1303)
1 parent 899f05f commit da56a35

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/api-ios.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ The `CodePush` class' methods can be thought of as composite resolvers which alw
1212

1313
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.
1414

15-
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.
15+
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.
1616

1717
4. Repeat #2 and #3 as the CodePush releases and app store releases continue on into infinity (and beyond?)
1818

0 commit comments

Comments
 (0)