From d4c2d633e273f3be026e578c99446ad5fdfe49e8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pau=20Farr=C3=A9?=
 <31051788+pau557@users.noreply.github.com>
Date: Wed, 31 Oct 2018 15:36:01 -0700
Subject: [PATCH] Update README.md (#115)

fixed typo in line 100
---
 preparing/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/preparing/README.md b/preparing/README.md
index 4c420486..9f24d6f7 100644
--- a/preparing/README.md
+++ b/preparing/README.md
@@ -97,7 +97,7 @@ Write your code with good coding style. Reading code written by others is usuall
 
 Always be explaining what you are currently writing/typing to the interviewer. This is not about literally reading out what you are typing to the interviewer. Talk about the section of the code you are currently implementing at a higher level, explain why it is written as such and what it is trying to achieve.
 
-While coding and you if you find yourself copying and pasting code, consider whether it is necessary. If you find yourself copying and pasting one large chunk of code spanning multiple lines, it is usually an indicator that you can refactor by extracting those lines into a function and defining parameters for the differences in them. If it is just a single line you copied, usually it is fine. Do remember to change the respective variables in your copied line of code where relevant. Copy-paste errors are a common source of bugs even in day-to-day coding!
+While coding, if you find yourself copying and pasting code, consider whether it is necessary. If you find yourself copying and pasting one large chunk of code spanning multiple lines, it is usually an indicator that you can refactor by extracting those lines into a function and defining parameters for the differences in them. If it is just a single line you copied, usually it is fine. Do remember to change the respective variables in your copied line of code where relevant. Copy-paste errors are a common source of bugs even in day-to-day coding!
 
 **After Coding**