From bb25419e05249e67b97113fd8fd09ddae805b927 Mon Sep 17 00:00:00 2001
From: Coheed <53392996+janpatrick-dev@users.noreply.github.com>
Date: Tue, 14 Nov 2023 16:20:25 +0800
Subject: [PATCH] fixed typo - leetcode > hone your soft skills

fixed typo triyng to trying
---
 leetcode/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/leetcode/README.md b/leetcode/README.md
index bdc8476..ed2b26f 100644
--- a/leetcode/README.md
+++ b/leetcode/README.md
@@ -103,7 +103,7 @@ I've talked a lot of solving Leetcode problems, but in reality there's another p
 I (think) I have had success in this area by doing the following:
 
 - **Overcommunicate.** The interviewer has no way of knowing what you're thinking unless you tell them. This is especially important if you haven't figured out a solution yet and you're thinking through options.
-- **Be friendly.** Leetcode-style interviews are stressful. By default, when we're stressed, we are not very happy. Interviewers see _a lot_ of candidates who are all business triyng to crank away at these coding challenges. You can stand out a lot if you smile and are conversational/friendly.
+- **Be friendly.** Leetcode-style interviews are stressful. By default, when we're stressed, we are not very happy. Interviewers see _a lot_ of candidates who are all business trying to crank away at these coding challenges. You can stand out a lot if you smile and are conversational/friendly.
 - **Ask questions checking your logic.** Interviewers mostly want you to succeed, especially if you seem like a good person. My favorite question to ask during a Leetcode-style interview is, "does that make sense?" I'll use this after I have propsed an approach to the problem and explained its time and space complexity. If you're on the money, the interviewer will often say, "yeah, that sounds great to me!" If they want to see something different (e.g., there's a flaw in your logic or your solution won't be efficient enough for them), they'll often tell you that. That's a huge benefit to prevent you going down the wrong path!
 
 You can't necessarily control whether you get a Leetcode problem you'll be able to solve optimally, but you _can_ control your demeanor/soft skills during the interview. This could be the difference between getting the job and not getting the job!