Fix grammar errors and add suggestions

Author: sstok

contributing/giving-constructive-criticism.rst

@@ -4,24 +4,26 @@ Giving constructive criticism
 :doc:`Reviewing issues and pull request </contributing/community/reviews>` is a great way to get started with
 contributing to the Symfony community. Anyone can do it! But before
 you give a comment, take a step back and think, is what you are about
-to say actually what you indent?
+to say actually what you intend?
 
-Communicating over the internet with nothing but text can pose a
-big challenge, especially if you remember the Symfony community
+Communicating over the Internet with nothing but text can pose a
+big challenge, especially if you remember that the Symfony community
 is world-wide and is composed of a wide variety of people with differing
-idea's and opinions.
+ideas and opinions.
 
-Not everyone speaks English, is able to use a keyboard, and some might
-even have dyslexia. And not to mention that some might have a
-bad experience from previous contributions (to other projects).
+Not everyone speaks English or is able to use a keyboard, some might
+have Dyslexia or similar conditions that affect their writing.
 
-Your not alone in this, this guide will try help you write
+Not to mention that some might have a bad experience from previous
+contributions (to other projects).
+
+You're not alone in this. This guide will try help you write
 constructive, respectful and helpful reviews and replies.
 
 .. tip::
 
     This guide is not about lecturing you to "conform" or give-up
-    your ideas and opinions. But helping you to better communicate,
+    your ideas and opinions but helping you to better communicate,
     prevent possible confusion, and keeping the Symfony community a
     welcoming place for everyone. **You are free to disagree with
     someone's opinions just don't be disrespectful.**
@@ -45,7 +47,7 @@ Gender pronouns
 ---------------
 
 While not "formally" required it's better to use gender-neutral pronouns.
-Unless someone "indicated" there pronouns, use "they", "them" instead of
+Unless someone "indicated" their pronouns, use "they", "them" instead of
 "he", "she", "his", "hers", "his/hers", "he/she", etc.
 
 And instead of saying "guys" it's better to use "folks", or Symfonions
@@ -55,19 +57,18 @@ Giving positive feedback
 ------------------------
 
 While reviewing issues and pull request you may run into some suggestions
-(including patches) that don't reflect your idea's, are not good, or down
-right wrong.
+(including patches) that don't reflect your ideas, are not good, or downright wrong.
 
-Now, instead of writing a lengthy comment why you think they are wrong.
-Consider the amount of work and time the author has spend on there idea.
-And how your response would make them feel;
+Now, instead of writing a lengthy comment why you think they are wrong,
+consider the amount of work and time the author has spent on their idea
+and how you're response would make them feel;
 
 * Are you making a point only because you believe they are wrong?
 
-* Did you correctly understand there intention? or are you making assumptions?
+* Did you correctly understand their intention? or are you making assumptions?
 
-Maybe you can ask for clarification?, suggest an alternative? or
-provide a simple explanation *why* disagree with there proposal.
+Maybe you can ask for clarification? suggest an alternative? or
+provide a simple explanation *why* disagree with their proposal.
 
 Even if something *is* really wrong or "a bad idea", stay respectful and
 don't get into endless you-are-wrong discussions or "flame wars".
@@ -78,12 +79,12 @@ don't get into endless you-are-wrong discussions or "flame wars".
 * Avoid using terms that could be seen as referring to personal traits. ("dumb",
   "stupid"). Assume everyone is intelligent and well-meaning.
 
-* Be explicit. Remember people don't always understand your intentions online.
+* Be explicit. Remember people don't always understand you're intentions online.
 
 * Don't use hyperbole. ("always", "never", "endlessly", "nothing", "worst",
   "horrible", "terrible").
 
-Instead of saying "This is a horrible idea" use something like
+Instead off saying "This is a horrible idea" use something like
 "This can introduce issues in the future. Please make sure this is safe to use."
 
 Asking for changes
@@ -92,10 +93,10 @@ Asking for changes
 Rarely something is perfect from the start, while the code itself is good.
 It may not be optimal or conform the Symfony coding style.
 
-Again, understand the author already spend time on the issue and asking
+Again, understand the author already spent time on the issue and asking
 for (small) changes may be misinterpreted or seen as a personal attack.
 
-Be thankful for there work (so far), stay positive and really help them
+Be thankful for their work (so far), stay positive and really help them
 to make the contribution a great one. *Especially if they are a first
 time contributor.*
 
@@ -125,17 +126,17 @@ OK, lets be honest. We all make jokes, some are funny and some are not.
 They don't put anyone of, right? Well, who's to tell. What's funny to one
 is offensive to another.
 
-In short. Keep it real. There is nothing wrong with using a meme or emoji
-from time to time, but don't over do it. And even then, keep it friendly.
+In short, keep it real. Their is nothing wrong with using a meme or emoji
+from time to time, but don't overdo it. And even then, keep it friendly.
 
 **Don't use sarcasm for a serious topic, that's not something that belongs
 to the Symfony community.** And don't marginalize someone's problems;
-"Well I guess that's not suppose to happen? 😆 ".
+"Well I guess that's not supposed to happen? 😆 ".
 
-Even if someone's explanation is "inviting to joke about", it's a real
-problem to them. Making jokes about this doesn't help with solving
-there problem and only makes them *feel stupid*. Instead try to discover
-what the problem is really about.
+Even if someone's explanation is "inviting to joke about it", it's a real
+problem to them. Making jokes about this doesn't help with solving their
+problem and only makes them *feel stupid*. Instead try to discover what
+the problem is really about.
 
 If emoji, animated gifs, or humor aren't you, don't force them.
 
@@ -150,5 +151,5 @@ simply failed.
 But don't say it "just because", if your apology is not really meant
 you *will* loose credibility and respect from other developers.
 
-*Don't do unto others what you don't want others to do unto you.*
+*Do unto others as you would have them do unto you.*