From 578eae489cbc391aa6842722ffbc1730d32094f3 Mon Sep 17 00:00:00 2001 From: Parikshit Hooda Date: Tue, 17 Mar 2020 23:23:25 +0530 Subject: [PATCH] chore: fix typos, add code of conduct link --- CODE_OF_CONDUCT.md | 2 +- test/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 22ab32170..4faf227c4 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1 +1 @@ -[Code of Conduct](https://js.foundation/community/code-of-conduct) +[Code of Conduct](https://github.com/openjs-foundation/code-and-learn/blob/master/CODE_OF_CONDUCT.md) diff --git a/test/README.md b/test/README.md index d3d827023..a60fd77a8 100644 --- a/test/README.md +++ b/test/README.md @@ -48,9 +48,9 @@ Stats cases are similar to configCases except specifically focusing on the `expe By default, the "expected" outcome is a pain to write by hand so instead when statsCases are run, runner is checking output using jest's awesome snapshot functionality. -Basically you don't need to write any expected behaviors your self. The assumption is that the stats output from your test code is what you expect. +Basically you don't need to write any expected behaviors yourself. The assumption is that the stats output from your test code is what you expect. -Please follow the approach described bellow: +Please follow the approach described below: * write your test code in `statsCases/` folder by creating a separate folder for it, for example `statsCases/some-file-import-stats/index.js`