✏️ Fixing english typos

FBerthelot · Mar 22, 2019 · 805b551 · 805b551
1 parent 613eb31
commit 805b551
Show file tree

Hide file tree

Showing 4 changed files with 10 additions and 10 deletions.
diff --git a/README.md b/README.md
@@ -1,12 +1,12 @@
 # component-test-utils
 
-Test HTML component the same way, whenever the FrameWork (React, Angular, Vue.JS, Vanilla, ...)
+Test HTML component the same way, regardless of the framework (React, Angular, Vue.JS, Vanilla, ...)
 
 [![npm Version](https://img.shields.io/npm/v/component-test-utils.svg)](https://www.npmjs.com/package/component-test-utils)
 
 [![License](https://img.shields.io/npm/l/component-test-utils.svg)](https://www.npmjs.com/package/component-test-utils)
 
-Component test utils is a Javascript Utility that help you to interact with your component and get component's output.
+Component test utils is a JavaScript Utility that help you to interact with your component and get component's output.
 
 ## Documentation
 
@@ -15,12 +15,12 @@ Documentation is Available here => [https://component-test-utils.berthelot.io](h
 ## Purpose
 
 Nowdays, testing component is commonly misunderstood.
-Each JavaScript FrameWork has is own way of testing.
-It\'s confusing when you switch of FrameWork.
+Each JavaScript framework has its own way of testing components.
+It's confusing when you switch framework.
 
-The goal of this tool is to have a opinated and unify way to test component disregarding the framework you use.
+The goal of this tool is to have an opinionated and unify the way to test a component disregarding the framework you use.
 
-## FrameWorks Available
+## Frameworks Available
 
 - ![React - Available](https://img.shields.io/badge/React-Available-brightgreen.svg) ![npm](https://img.shields.io/npm/v/component-test-utils-react.svg)
 
@@ -32,7 +32,7 @@ The goal of this tool is to have a opinated and unify way to test component disr
 
 ## Contributing
 
-Contribute as you want! It's always good to open, issues or PR !
+Contribute as you want! It's always good to open issues or PR !
 
 That said, I try to [follow some rules for commit](./CONTRIBUTING.md).
 

diff --git a/package.json b/package.json
@@ -2,7 +2,7 @@
   "name": "component-test-utils-master",
   "version": "1.0.0-alpha.0",
   "private": true,
-  "description": "Test HTML component the same way, whenever the framework (React, Angular, Vue.JS, Vanilla, ...) ",
+  "description": "Test HTML component the same way, regardless of the framework (React, Angular, Vue.JS, Vanilla, ...) ",
   "main": "index.js",
   "scripts": {
     "install": "npm run lerna bootstrap && cd website && npm i",

diff --git a/packages/component-test-utils/README.md b/packages/component-test-utils/README.md
@@ -1,5 +1,5 @@
 # component-test-utils
-Test HTML component the same way, whenever the FrameWork (React, Angular, Vue.JS, Vanilla, ...)
+Test HTML component the same way, regardless of the framework (React, Angular, Vue.JS, Vanilla, ...)
 
 [![npm Version](https://img.shields.io/npm/v/component-test-utils.svg)](https://www.npmjs.com/package/component-test-utils)
 [![License](https://img.shields.io/npm/l/component-test-utils.svg)](https://www.npmjs.com/package/component-test-utils)

diff --git a/packages/component-test-utils/package.json b/packages/component-test-utils/package.json
@@ -1,7 +1,7 @@
 {
   "name": "component-test-utils",
   "version": "1.0.0-alpha.1",
-  "description": " Test HTML component the same way, whenever the framework (React, Angular, Vue.JS, Vanilla, ...) ",
+  "description": " Test HTML component the same way, regardless of the framework (React, Angular, Vue.JS, Vanilla, ...) ",
   "main": "index.js",
   "scripts": {
     "test": "echo \"to launch tests, start it from component-tet-utils root folder\" && exit 1"