From 133fbdeb2539c0ca36f3beb09a90370664a877cf Mon Sep 17 00:00:00 2001 From: Thamizhselvan Date: Tue, 16 Oct 2018 09:21:49 +0530 Subject: [PATCH] fixed typo issue (#19429) converted is to it --- .../pages/guide/english/working-in-tech/code-reviews/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/client/src/pages/guide/english/working-in-tech/code-reviews/index.md b/client/src/pages/guide/english/working-in-tech/code-reviews/index.md index 8a64de97044..334e0afdc35 100644 --- a/client/src/pages/guide/english/working-in-tech/code-reviews/index.md +++ b/client/src/pages/guide/english/working-in-tech/code-reviews/index.md @@ -15,7 +15,7 @@ As to what is reviewed and when, well there is no clear answer. Many teams have rules that every piece of code that checks-in in the version control system has to be reviewed by another programmer, while other teams have whole days when they dedicate to code reviews across the team. -Is is important to be humble throughout the code review process. Accept your mistakes, +It is important to be humble throughout the code review process. Accept your mistakes, and be professional when pointing out improvements or errors in the code of your fellow team members.