Fixed 2 typos (#114)

interviewers/basics.md

@@ -16,5 +16,5 @@ These items will all change based on your specific company and needs but these i
 ## Tech Question Technique
 
 - **Tools** - Using a text editor such as Sublime or Atom will give the interviewee syntax highlighting but doesn't show compiler errors which can be a help.
-- **Nitpicking** - Sometimes psuedocode is okay. If testing in C# do you really need the interviewee to write `Console.WriteLine()` or is `Print()` good enough?
+- **Nitpicking** - Sometimes pseudocode is okay. If testing in C# do you really need the interviewee to write `Console.WriteLine()` or is `Print()` good enough?
 -**Keep Dialog Open** - Don't leave the interviewee alone or sit quietly by as they attempt to code. Give some subtle hints like "I see you're doing ____, can you think of any other ways to accomplish this?" It's unlikely that the interviewee will be working in a silo should they get the job, is there any reason they should be during the interview?

preparing/README.md

@@ -67,7 +67,7 @@ An example of the above could be:
 > 
 > Outside of work I develop a on open source projects written in Python. Examples of some open source projects I created are <insert examples>.
 > 
-> I'm now seeking new job oppurtunities in the Boston area since I'm relocating for personal reasons. In particular I think Boston Dynamics is a perfect fit for my interests as well as my skill set.
+> I'm now seeking new job opportunities in the Boston area since I'm relocating for personal reasons. In particular I think Boston Dynamics is a perfect fit for my interests as well as my skill set.
 
 **Upon Getting the Question**