Repository structure clean up

README.md

@@ -18,7 +18,7 @@ Carefully curated content to help you ace your next technical interview, with a
 - [How to prepare](preparing) for coding interviews
 - [Algorithm tips and the best practice questions](algorithms) categorized by topic
 - ["Front-end Job Interview Questions" answers](front-end/interview-questions.md)
-- [Interview formats](non-technical/format.md) of the top tech companies
+- [Interview formats](non-technical/interview-formats.md) of the top tech companies
 - [Behavioral questions](non-technical/behavioral.md) categorized by companies
 - [Good questions to ask your interviewers](non-technical/questions-to-ask.md) at the end of the interviews
 
@@ -47,8 +47,8 @@ Also, existing resources focus mainly on algorithm questions, and lack in covera
   - [Front-end Job Interview Questions and Answers](front-end/interview-questions.md) 🔥⭐
 - **[Non-Technical Tips](non-technical)** - Random non-technical tips that cover behavioral and psychological aspects, interview formats and "Do you have any questions for me?"
   - [Behavioral Questions](non-technical/behavioral.md)
-  - [Interview Formats](non-technical/format.md)
+  - [Interview Formats](non-technical/interview-formats.md)
-  - [Psychological Tricks](non-technical/psychological.md)
+  - [Psychological Tricks](non-technical/psychological-tricks.md)
   - [Questions to Ask](non-technical/questions-to-ask.md)
   - [Negotiation Tips](non-technical/negotiation.md)
 - **[Utilities](utilities)** - Snippets of algorithms/code that will help in coding questions.

non-technical/self-introduction.md

@@ -14,7 +14,7 @@ The Elevator Pitch is an indispensable tool for you as you move forward in your
   - Tell them who you are, who you work for (or school and major), and what you do.
 - KISS (Keep It Simple, Stupid)
   - Tell them some highlights from your favorite / most impressive projects.
-    - Do not delve into the depths of how you reverse engineered a game and decrypted a packet to predict when to use your DKP on a drop. Tell them the executive summary: "I reverse engineered X game by decrypting Y packet to predict Z." If this catches their interest, they *will* ask further questions on their own.
+  - Do not delve into the depths of how you reverse engineered a game and decrypted a packet to predict when to use your DKP on a drop. Tell them the executive summary: "I reverse engineered X game by decrypting Y packet to predict Z." If this catches their interest, they *will* ask further questions on their own.
 - Why do *they* want *you*?
   - This is where you use your knowledge of the company, knowledge of their technology stack(s), your unique talent that they want, etc. in order to solidify your ability to contribute to their company.
 - PRACTICE!