README typo

Author: Ashoat

README.md

@@ -10,10 +10,10 @@ This package allows the user to manage their React Navigation state from within
 
 ## Motivation
 
-Most projects that are using both Redux and React Navigation don't need this library. Things like state persistance and `BackHandler` behavior aren't handled directly by `createReduxContainer`, but are handled by the default `createAppContainer`. However, there are some things this library makes easier:
+Most projects that are using both Redux and React Navigation don't need this library. Things like state persistence and `BackHandler` behavior aren't handled directly by `createReduxContainer`, but are handled by the default `createAppContainer`. However, there are some things this library makes easier:
 
 1. It's possible to implement [custom actions](https://github.com/Ashoat/squadcal/blob/4ce900481bbfd1681d568edc669b66b1ae9555f0/native/navigation/navigation-setup.js#L384-L395), allowing you to manipulate the navigation state in ways that aren't possible with the stock React Navigation actions. Though it's possible to implement [custom routers](https://reactnavigation.org/docs/en/custom-routers.html) in React Navigation to do this, it's arguably cleaner via Redux. (If you want animations to run on your action, [make sure](https://github.com/Ashoat/squadcal/blob/4ce900481bbfd1681d568edc669b66b1ae9555f0/native/navigation/navigation-setup.js#L633) to set `isTransitioning` to true!)
-2. This library allows the user to customize the persistance of their navigation state. For instance, you could choose to persist your navigation state in encrypted storage. Most users don't need this, as there are no practical downsides to handling persistance of navigation state and Redux state separately. Note that stock React Navigation supports some basic degree of [persistance customization](https://reactnavigation.org/docs/en/state-persistence.html).
+2. This library allows the user to customize the persistence of their navigation state. For instance, you could choose to persist your navigation state in encrypted storage. Most users don't need this, as there are no practical downsides to handling persistence of navigation state and Redux state separately. Note that stock React Navigation supports some basic degree of [persistence customization](https://reactnavigation.org/docs/en/state-persistence.html).
 3. You can implement [custom reducer behavior](https://github.com/Ashoat/squadcal/blob/4ce900481bbfd1681d568edc669b66b1ae9555f0/native/navigation/navigation-setup.js#L341-L352) to validate state and maintain consistency between navigation state and other application state. This is again possible with custom routers, but likely cleaner to implement without, especially in the context of an existing Redux setup.
 
 ## Installation