ci(travis): add mdspell (#443)

Author: juancarlostong

.travis.yml

@@ -46,6 +46,19 @@ jobs:
       notifications:
         email: false
 
+    - stage: 'Lint markdown files'
+      language: node_js
+      node_js: 12
+      os: linux
+      before_install: skip
+      install:
+        - npm i -g markdown-spellcheck
+      before_script:
+        - wget --quiet https://raw.githubusercontent.com/optimizely/mdspell-config/master/.spelling
+      script:
+        - mdspell -a -n -r --en-us '**/*.md'
+      after_success: skip
+
     - stage: 'SourceClear and Lint'
       language: objective-c
       os: osx

CHANGELOG.md

@@ -191,7 +191,7 @@ The primary difference between the new Feature Variable APIs and the older, Vari
 To learn more about Feature Management, read our [knowledge base article introducing the feature](https://help.optimizely.com/Set_Up_Optimizely/Develop_a_product_or_feature_with_Feature_Management).
 
 ### New Features
-* Introduces the `isFeatureEnabled` API, a featue flag used to determine whether to show a feature to a user. The `isFeatureEnabled` should be used in place of the `activate` API to activate experiments running on features. Specifically, calling this API causes the SDK to evaluate all [Feature Tests](https://developers.optimizely.com/x/solutions/sdks/reference/?language=objectivec#activate-feature-tests) and [Rollouts](https://developers.optimizely.com/x/solutions/sdks/reference/?language=objectivec#activate-feature-rollouts) associated with the provided feature key.
+* Introduces the `isFeatureEnabled` API, a feature flag used to determine whether to show a feature to a user. The `isFeatureEnabled` should be used in place of the `activate` API to activate experiments running on features. Specifically, calling this API causes the SDK to evaluate all [Feature Tests](https://developers.optimizely.com/x/solutions/sdks/reference/?language=objectivec#activate-feature-tests) and [Rollouts](https://developers.optimizely.com/x/solutions/sdks/reference/?language=objectivec#activate-feature-rollouts) associated with the provided feature key.
 ```
 /**
  * Determine whether a feature is enabled.
@@ -270,7 +270,7 @@ with Notification Listeners APIs
 ### Deprecations
 * Version 2.1.0 deprecates the Variable APIs: `variableBoolean`, `variableDouble`, `variableInteger`, and `variableString` 
 
-* Replace use of the Variable APIs with Feature Mangement's Feature Variable APIs, described above
+* Replace use of the Variable APIs with Feature Management's Feature Variable APIs, described above
 
 * We will continue to support the Variable APIs until the 3.x release, but we encourage you to upgrade as soon as possible
 
@@ -419,7 +419,7 @@ unable to be deleted from data store due to syntax error.
 June 15, 2018
 
 ### New Features
-* Updated SDK targets to Xcode 9.4 recommended settings, pod update'd third party Cocoapods used by the 2 demo apps,
+* Updated SDK targets to Xcode 9.4 recommended settings, pod updated third party Cocoapods used by the 2 demo apps,
 and eliminated Xcode 9.4 Build and Analyze warnings for SDK targets.
 
 ## 1.5.1
@@ -480,7 +480,7 @@ OPTLYClient * _Nullable client))callback;
 ```
 ### Bug Fixes:
 * Added `libsqlite3.tbd` to the Shared framework podspec and linked it in the build settings. 
-* Crash caused by `Fatal Exception: NSRangeException` in `OPTLYHTTPRequestManager.m`. This crash occurred during a backoff retry in a datafile download or event dispatch because data strutures that were not threadsafe (used only for testing) were being modified. To resolve this, the data structures were wrapped in a flag and are only modifiable if unit tests are running.
+* Crash caused by `Fatal Exception: NSRangeException` in `OPTLYHTTPRequestManager.m`. This crash occurred during a backoff retry in a datafile download or event dispatch because data structures that were not threadsafe (used only for testing) were being modified. To resolve this, the data structures were wrapped in a flag and are only modifiable if unit tests are running.
 
 ### Cleanup:
 * Fix migration to Xcode 9.0 compiler warnings regarding "NSError * __autoreleasing *" and "(^)(void) in blocks".

OptimizelySDKShared/OPTLYFMDB/README.md

@@ -97,11 +97,11 @@ In addition to the `makeFunctionNamed` noted above, there are a few other API ch
 
  - To become consistent with the rest of the API, the methods `objectForColumnName` and `UTF8StringForColumnName` have been renamed to `objectForColumn` and `UTF8StringForColumn`.
 
- - Note, the `objectForColumn` (and the associted subscript operator) now returns `nil` if an invalid column name/index is passed to it. It used to return `NSNull`.
+ - Note, the `objectForColumn` (and the associated subscript operator) now returns `nil` if an invalid column name/index is passed to it. It used to return `NSNull`.
 
  - To avoid confusion with `OPTLYFMDBDatabaseQueue` method `inTransaction`, which performs transactions, the `OPTLYFMDBDatabase` method to determine whether you are in a transaction or not, `inTransaction`, has been replaced with a read-only property, `isInTransaction`.
 
- - Several functions have been converted to properties, namely, `databasePath`, `maxBusyRetryTimeInterval`, `shouldCacheStatements`, `sqliteHandle`, `hasOpenResultSets`, `lastInsertRowId`, `changes`, `goodConnection`, `columnCount`, `resultDictionary`, `applicationID`, `applicationIDString`, `userVersion`, `countOfCheckedInDatabases`, `countOfCheckedOutDatabases`, and `countOfOpenDatabases`. For Objective-C users, this has little material impact, but for Swift users, it results in a slightly more natural interface. Note: For Objective-C developers, previously versions of OPTLYFMDB exposed many ivars (but we hope you weren't using them directly, anyway!), but the implmentation details for these are no longer exposed.
+ - Several functions have been converted to properties, namely, `databasePath`, `maxBusyRetryTimeInterval`, `shouldCacheStatements`, `sqliteHandle`, `hasOpenResultSets`, `lastInsertRowId`, `changes`, `goodConnection`, `columnCount`, `resultDictionary`, `applicationID`, `applicationIDString`, `userVersion`, `countOfCheckedInDatabases`, `countOfCheckedOutDatabases`, and `countOfOpenDatabases`. For Objective-C users, this has little material impact, but for Swift users, it results in a slightly more natural interface. Note: For Objective-C developers, previously versions of OPTLYFMDB exposed many ivars (but we hope you weren't using them directly, anyway!), but the implementation details for these are no longer exposed.
 
 ### URL Methods
 

Pods/Mixpanel-swift/README.md

@@ -136,24 +136,24 @@ First-party code (under OptimizelySDKCore/, OptimizelySDKDatafileManager/, Optim
 
 **FMDB** [https://github.com/ccgus/fmdb](https://github.com/ccgus/fmdb)  
 License (MIT):: [https://github.com/ccgus/fmdb/blob/master/LICENSE.txt](https://github.com/ccgus/fmdb/blob/master/LICENSE.txt)
-Modfied: Yes
+Modified: Yes
 Distributed: Yes
 Distribution: Binary
 
 **SQLITE3** [https://www.sqlite.org/index.html](https://www.sqlite.org/index.html)  
 License (Public Domain):: [https://www.sqlite.org/copyright.html](https://www.sqlite.org/copyright.html)
-Modfied: Yes
+Modified: Yes
 Distributed: Yes
 Distribution: Binary
 
 **JSONModel** [https://github.com/jsonmodel/jsonmodel](https://github.com/jsonmodel/jsonmodel)  
 License (MIT):: [https://github.com/jsonmodel/jsonmodel/blob/master/LICENSEl](https://github.com/jsonmodel/jsonmodel/blob/master/LICENSE)
-Modfied: Yes
+Modified: Yes
 Distributed: Yes
 Distribution: Binary
 
 **murmur3** [https://github.com/PeterScott/murmur3l](https://github.com/PeterScott/murmur3)  
 License (Public Domain):: [https://github.com/PeterScott/murmur3l](https://github.com/PeterScott/murmur3)
-Modfied: No
+Modified: No
 Distributed: Yes
 Distribution: Binary