From 3f6eb7b0ee2053a156a2f6061a66acc5c80bf446 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Pott?= Date: Thu, 28 Dec 2017 21:20:43 +0100 Subject: [PATCH] A few grammar fixes (#105) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3c3addf..1fa4745 100644 --- a/README.md +++ b/README.md @@ -488,7 +488,7 @@ Having a good guideline for creating commits and sticking to it makes working wi * Avoid client-side console logs in production _Why:_ - > Even though your build process can(should) get rid of them, but make sure your code style check gives your warning about console logs. + > Even though your build process can(should) get rid of them, make sure that your code style checker warns you about leftover console logs. * Produce readable production logging. Ideally use logging libraries to be used in production mode (such as [winston](https://github.com/winstonjs/winston) or [node-bunyan](https://github.com/trentm/node-bunyan)).