vulnerability fixes, typos fixes and LICENSE file update

.github/pull_request_template.md

@@ -1,4 +1,4 @@
-# Javascript Sync Tools
+# JavaScript Sync Tools
 
 ## What did you accomplish?
 

CONTRIBUTORS-GUIDE.md

@@ -1,22 +1,23 @@
-# Contributing to the Split Javascript Sync Tools
+# Contributing to the Split JavaScript Sync Tools
 
-Split Javascript Sync Tools is an open source project and we welcome feedback and contribution. The information below describes how to build the project with your changes, run the tests, and send the Pull Request(PR).
+Split JavaScript Sync Tools is an open source project and we welcome feedback and contribution. The information below describes how to build the project with your changes, run the tests, and send the Pull Request(PR).
 
 ## Development
 
 ### Development process
 
 1. Fork the repository and create a topic branch from `development` branch. Please use a descriptive name for your branch.
-2. While developing, use descriptive messages in your commits. Avoid short or meaningless sentences like: "fix bug".
-3. Make sure to add tests for both positive and negative cases.
-4. Run the linter script of the project and fix any issues you find.
-5. Run the build script and make sure it runs with no errors.
-6. Run all tests and make sure there are no failures.
-7. `git push` your changes to GitHub within your topic branch.
-8. Open a Pull Request(PR) from your forked repo and into the `development` branch of the original repository.
-9. When creating your PR, please fill out all the fields of the PR template, as applicable, for the project.
-10. Check for conflicts once the pull request is created to make sure your PR can be merged cleanly into `development`.
-11. Keep an eye out for any feedback or comments from Split's SDK team.
+2. Run `nvm use` to ensure that you are using the right npm and node version, and `npm install` to have the dependencies up to date.
+3. While developing, use descriptive messages in your commits. Avoid short or meaningless sentences like: "fix bug".
+4. Make sure to add tests for both positive and negative cases.
+5. Run the linter script of the project and fix any issues you find.
+6. Run the build script and make sure it runs with no errors.
+7. Run all tests and make sure there are no failures.
+8. `git push` your changes to GitHub within your topic branch.
+9. Open a Pull Request(PR) from your forked repo and into the `development` branch of the original repository.
+10. When creating your PR, please fill out all the fields of the PR template, as applicable, for the project.
+11. Check for conflicts once the pull request is created to make sure your PR can be merged cleanly into `development`.
+12. Keep an eye out for any feedback or comments from Split's SDK team.
 
 ### Building the tools
 
@@ -26,8 +27,6 @@ For widespread use of the tools with different environments and module formats,
 
 The different builds can be generated all at once with the command `npm run build`. Refer to [package.json](package.json) for more insight on the build scripts.
 
-_Note:_ In order to run build/tests commands, Node 10 or higher is required.
-
 ### Running tests
 
 The project includes unit as well as integration tests.

LICENSE

@@ -1,4 +1,4 @@
-Copyright © 2022 Split Software, Inc.
+Copyright © 2023 Split Software, Inc.
 
 Licensed under the Apache License, Version 2.0 (the "License");
 you may not use this file except in compliance with the License.

README.md

@@ -1,17 +1,17 @@
-# Split Javascript Sync Tools
+# Split JavaScript Sync Tools
 
 [![npm version](https://badge.fury.io/js/%40splitsoftware%2Fsplitio-sync-tools.svg)](https://badge.fury.io/js/%40splitsoftware%2Fsplitio-sync-tools) [![Build Status](https://github.com/splitio/javascript-sync-tools/actions/workflows/ci.yml/badge.svg)](https://github.com/splitio/javascript-sync-tools/actions/workflows/ci.yml)
 
 ## Overview
-This package includes a set of Javascript synchronization tools built based on the core implementation used by SDKs, allowing users to rely on this tool to synchronize the rollout plan data cache snapshot, as well as send the tracked events and impressions data to the Split cloud when running SDKs in consumer mode.
+This package includes a set of JavaScript synchronization tools built based on the core implementation used by SDKs, allowing users to rely on this tool to synchronize the rollout plan data cache snapshot, as well as send the tracked events and impressions data to the Split cloud when running SDKs in consumer mode.
 
 [![Twitter Follow](https://img.shields.io/twitter/follow/splitsoftware.svg?style=social&label=Follow&maxAge=1529000)](https://twitter.com/intent/follow?screen_name=splitsoftware)
 
 ## Compatibility
-Split sync tools supports Node.js version 8 or higher. To run the tools in other Javascript environments, the target environment must support ES6 (ECMAScript 2015) syntax, and provide built-in support or a global polyfill for Promises and Web Fetch API.
+Split sync tools supports Node.js version 8 or higher. To run the tools in other JavaScript environments, the target environment must support ES6 (ECMAScript 2015) syntax, and provide built-in support or a global polyfill for Promises and Web Fetch API.
 
 ## Getting started
-Below is a simple example that describes the execution of the Javascript Synchronizer:
+Below is a simple example that describes the execution of the JavaScript Synchronizer:
 
 1. Install npm package via `npm install @splitsoftware/splitio-sync-tools`
 2. Inside your app, import the `Synchronizer`
@@ -43,7 +43,7 @@ const synchronizer = new Synchronizer({
 synchronizer.execute().then(() => console.log('ready'));
 ```
 
-Please refer to [Javascript Sync Tools](https://help.split.io/hc/en-us/articles/4421513571469-Split-JavaScript-synchronizer-tools) to learn about all the functionality provided by the package.
+Please refer to [JavaScript Sync Tools](https://help.split.io/hc/en-us/articles/4421513571469-Split-JavaScript-synchronizer-tools) to learn about all the functionality provided by the package.
 
 ## Submitting issues
 The Split team monitors all issues submitted to this [issue tracker](https://github.com/splitio/javascript-sync-tools/issues). We encourage you to use this issue tracker to submit any bug reports, feedback, and feature enhancements. We'll do our best to respond in a timely manner.
@@ -67,8 +67,8 @@ Split has built and maintains SDKs for:
 * GO [Github](https://github.com/splitio/go-client) [Docs](https://help.split.io/hc/en-us/articles/360020093652-Go-SDK)
 * iOS [Github](https://github.com/splitio/ios-client) [Docs](https://help.split.io/hc/en-us/articles/360020401491-iOS-SDK)
 * Java [Github](https://github.com/splitio/java-client) [Docs](https://help.split.io/hc/en-us/articles/360020405151-Java-SDK)
-* Javascript [Github](https://github.com/splitio/javascript-client) [Docs](https://help.split.io/hc/en-us/articles/360020448791-JavaScript-SDK)
-* Javascript for Browser [Github](https://github.com/splitio/javascript-browser-client) [Docs](https://help.split.io/hc/en-us/articles/360058730852-Browser-SDK)
+* JavaScript [Github](https://github.com/splitio/javascript-client) [Docs](https://help.split.io/hc/en-us/articles/360020448791-JavaScript-SDK)
+* JavaScript for Browser [Github](https://github.com/splitio/javascript-browser-client) [Docs](https://help.split.io/hc/en-us/articles/360058730852-Browser-SDK)
 * Node [Github](https://github.com/splitio/javascript-client) [Docs](https://help.split.io/hc/en-us/articles/360020564931-Node-js-SDK)
 * PHP [Github](https://github.com/splitio/php-client) [Docs](https://help.split.io/hc/en-us/articles/360020350372-PHP-SDK)
 * Python [Github](https://github.com/splitio/python-client) [Docs](https://help.split.io/hc/en-us/articles/360020359652-Python-SDK)