Incipit reviewed

Author: arialdomartini

README.md

@@ -3,22 +3,21 @@ Back-End Developer Interview Questions
 
 This page has been translated to [Chinese](https://github.com/monklof/Back-End-Developer-Interview-Questions) by [monklof](https://github.com/monklof).
 
-I started writing down this list for a very personal goal, as a reminder of topics I had the chance to discuss with colleagues and friends, and that I wanted to deepen...
+I started writing down this list as a personal reminder of topics I had the chance to discuss with colleagues and friends, and that I wanted to deepen...
 
-I'm not a big fan of asking technical questions in job interviews: I'd rather prefer to sit together with candidates in front of some real code, facing a real problem, and have a full day of pair programming rotating with all the team members. Yet, some technical questions could be used to start a deep and nice conversation, and this can be useful to get a deeper knowledge of each other.
+I'm not a big fan of asking technical questions in job interviews: I rather prefer to sit together with candidates in front of some real code, hands on the keyboard, facing a real problem, and have a full day of pair programming, hopefully rotating with all the other team members. Yet, I feel some technical questions could be a good starting point to begin an engaging and nice conversation, and this can be useful to get a deeper knowledge of each others.
 
-This repo contains a number of backend interview questions that can be used when vetting potential candidates. It is by no means recommended to use every single question here on the same candidate: that would take hours, and would have no sense at all, as they cover a too broad set of topics no single developer would probably have such a broad knowledge. Choosing a few selected items from this list should help you vet the intended skills you require.
+This repo collects a number of back end related questions that can be used when vetting potential candidates. It is by no means recommended to use every single question on the same candidate: that would take hours, and would have no sense at all, as they cover a too broad set of topics for a single developer's to possibly know. Browse the section you find more relevant for your context, and pick the questions that give you more ideas on the conversation to have.
 
 ### Notice
-Most of the questions are open-ended, and they just don't have a **right** answer. On the contrary, they are intended to be used as the starting point for a conversation that hopefully tell you more about the person's capabilities than a straight answer would.
+Most of the questions are open-ended, and some of them just don't have a *right* or a *wrong* answer. On the contrary, they are intended to be used as the starting point for a conversation that hopefully tells you more about the person's capabilities than a straight answer would. Personally, I would even choose the questions whose answers are not yet clear to me.
 
-Again, I stress that just asking questions is hardly sufficient. Complete the interview with a long pair programming session with your candidates: it is one of the best opportunities to know each other's style and approach and to let candidates know some details about their future day job.
+Again, I stress that just asking questions is hardly sufficient. Complete the interview with a long pair programming session with your candidates: it is one of the best opportunities to know each others' style and approach and to let candidates know some details about their future day job.
 
 This project is admittedly inspired by [Front-end Job Interview Questions](https://github.com/darcyclarke/Front-end-Developer-Interview-Questions) by [@darcyclarke](https://github.com/darcyclarke)
 
 
 
-
 ### Where are the answers?
 
 Sooner or later I will complete it with the relative answers. Feel free to contribute, it would be highly appreciated!
@@ -466,7 +465,7 @@ This section collects some weird questions along the lines of the [Manhole Cover
 * Imagine there's a perfect clone of yourself. Imagine that that clone is your boss. Would you like to work for him/her?
 * Interview me
 * Why are Quora's answers better than Yahoo Answers' ones?
-* As a play game, defend Cobol against modern languages, and try to find as many reasonable arguments as you can.
+* Let's play a game: defend Cobol against modern languages, and try to find as many reasonable arguments as you can.
 * Where will you be in 10 years?
 * You are my boss and I'm fired. Inform me.
 * I want to refactor a legacy system. You want to rewrite it from scratch. Argument. Then, switch our roles.