Fix some minor typo’s and corrections

Author: sstok

contributing/community/review-comments.rst

@@ -12,7 +12,7 @@ is world-wide and is composed of a wide variety of people with differing
 ideas and opinions.
 
 Not everyone speaks English or is able to use a keyboard. Some might
-have Dyslexia or similar conditions that affect their writing.
+have dyslexia or similar conditions that affect their writing.
 
 Not to mention that some might have a bad experience from previous
 contributions (to other projects).
@@ -36,7 +36,7 @@ Tone of voice
 -------------
 
 We don't expect you to be completely formal, or to even write error-free
-English. Just remember one thing: Don't swear, and be respectful to others.
+English. Just remember this: don't swear, and be respectful to others.
 
 Don't reply in anger or with an aggressive tone. You're angry, we understand
 that, but swearing/cursing and name calling doesn't really encourage anyone to
@@ -46,13 +46,13 @@ you encounter.
 Gender pronouns
 ---------------
 
-While not "formally" required it's better to use gender-neutral pronouns.
+While not "formally" required, it's better to use gender-neutral pronouns.
 Unless someone "indicated" their pronouns, use "they", "them" instead of
 "he", "she", "his", "hers", "his/hers", "he/she", etc.
 
 Try to avoid using wording that may be considered excluding and needlessly gendered,
 like for example words that have a male base. For example we recommend to use other
-words like “folks”, “team”, “everyone” in place of “guys”.
+words like "folks", "team", "everyone" in place of "guys".
 
 Giving positive feedback
 ------------------------
@@ -61,10 +61,10 @@ While reviewing issues and pull requests you may run into some suggestions
 (including patches) that don't reflect your ideas, are not good, or downright wrong.
 
 Now, when you prepare your comment, consider the amount of work and time the author
-has spent on their idea and how your response would make them feel;
+has spent on their idea and how your response would make them feel.
 
 Did you correctly understand their intention? Or are you making assumptions?
-Which ever you respond, be explicit. Remember people don't always understand your
+Whatever your response, be explicit. Remember people don't always understand your
 intentions online.
 
 Avoid using terms that could be seen as referring to personal traits ("dumb", "stupid").
@@ -113,7 +113,7 @@ If a piece of code is in fact wrong, explain why:
 
     * Code doesn't match Symfony's CS rules (e.g. ``use array()`` instead of ``[]``)
 
-    * We only provide integration with very popular projects (e.g. we integrate Bootstrap but not your own CSS framework
+    * We only provide integration with very popular projects (e.g. we integrate Bootstrap but not your own CSS framework)
 
     * This would require adding lots of code and making lots of changes for a feature that doesn't look so important.
       That could hurt maintaining in the future.
@@ -141,17 +141,17 @@ Use words like "Please", "Thank you" and "Could you" instead of making demands;
 
 * "Please use 4 spaces instead of tabs", "This needs be on the previous line";
 
-  During a pull request review you can usually leave more then one comment,
-  you don't have to use "Please" all the time. But it wouldn't hurt.
+During a pull request review you can usually leave more then one comment,
+you don't have to use "Please" all the time. But it wouldn't hurt.
 
 It may not seem like much, but saying "Thank you" does make others feel
 more welcome.
 
 Using humor
 -----------
 
-In short: Don't be a troll; This violates the Code of Conduct and may
-even get you banned! Keep it real and friendly.
+In short: Extreme misbehavior will not be tolerated and may even get you banned;
+Keep it real and 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;