Fix typos

src/__tests__/reducer.test.ts

@@ -2,7 +2,7 @@ import { initialStatus, splitReducer } from '../reducer';
 import { splitReady, splitReadyWithEvaluations, splitReadyFromCache, splitReadyFromCacheWithEvaluations, splitTimedout, splitUpdate, splitUpdateWithEvaluations, splitDestroy, addTreatments } from '../actions';
 import { ISplitState } from '../types';
 import SplitIO from '@splitsoftware/splitio/types/splitio';
-import { AnyAction } from 'redux';
+import { Action } from 'redux';
 
 const initialState: ISplitState = {
   isReady: false,
@@ -179,7 +179,7 @@ describe('Split reducer', () => {
     });
   });
 
-  const actionCreatorsWithEvaluations: Array<[string, (key: SplitIO.SplitKey, treatments: SplitIO.TreatmentsWithConfig, timestamp: number, nonDefaultKey?: boolean) => AnyAction, boolean, boolean]> = [
+  const actionCreatorsWithEvaluations: Array<[string, (key: SplitIO.SplitKey, treatments: SplitIO.TreatmentsWithConfig, timestamp: number, nonDefaultKey?: boolean) => Action, boolean, boolean]> = [
     ['ADD_TREATMENTS', addTreatments, false, false],
     ['SPLIT_READY_WITH_EVALUATIONS', splitReadyWithEvaluations, true, false],
     ['SPLIT_READY_FROM_CACHE_WITH_EVALUATIONS', splitReadyFromCacheWithEvaluations, false, true],

src/react-redux/connectToggler.ts

@@ -8,7 +8,7 @@ const NullRenderComponent: React.ComponentType = () => null;
 
 /**
  * To avoid passing down dispatch property, merge props override default
- * behaviour from connect. Here dispatchProps are not passing down.
+ * behavior from connect. Here dispatchProps are not passing down.
  */
 const mergeProps = (stateProps: any, dispatchProps: any, ownProps: any) => ({
   ...stateProps,

src/types.ts

@@ -122,9 +122,9 @@ export type IGetTreatmentsParams = {
 
   /**
    * This param indicates to re-evaluate the feature flags if the SDK is updated. For example, a `true` value might be
-   * the desired behaviour for permission toggles or operation toggles, such as a kill switch, that you want to
-   * inmediately reflect in your app. A `false` value might be useful for experiment or release toggles, where
-   * you want to keep the treatment unchanged during the sesion of the user.
+   * the desired behavior for permission toggles or operation toggles, such as a kill switch, that you want to
+   * immediately reflect in your app. A `false` value might be useful for experiment or release toggles, where
+   * you want to keep the treatment unchanged during the session of the user.
    *
    * @defaultValue `false`
    */