message: docs: fix some mistakes
  PR Close
diff: @@ -55,9 +55,9 @@ We want to fix all the issues as soon as possible, but before fixing a bug we ne
  A minimal reproduction allows us to quickly confirm a bug (or point out a coding problem) as well as confirm that we are fixing the right problem.
  -We will be insisting on a minimal reproduction scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience users often find coding problems themselves while preparing a minimal reproduction. We understand that sometimes it might be hard to extract essential bits of code from a larger code-base but we really need to isolate the problem before we can fix it.
  +We will be insisting on a minimal reproduction scenario in order to save maintainers time and ultimately be able to fix more bugs. Interestingly, from our experience, users often find coding problems themselves while preparing a minimal reproduction. We understand that sometimes it might be hard to extract essential bits of code from a larger codebase but we really need to isolate the problem before we can fix it.
  -Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you we are going to close an issue that doesn't have enough info to be reproduced.
  +Unfortunately, we are not able to investigate / fix bugs without a minimal reproduction, so if we don't hear back from you, we are going to close an issue that doesn't have enough info to be reproduced.
  You can file new issues by selecting from our [new issue templates](https://github.com/angular/angular/issues/new/choose) and filling out the issue template.
  @@ -168,7 +168,7 @@ format that includes a **type**, a **scope** and a **subject**:
  The **header** is mandatory and the **scope** of the header is optional.
  -Any line of the commit message cannot be longer 100 characters! This allows the message to be easier
  +Any line of the commit message cannot be longer than 100 characters! This allows the message to be easier
  to read on GitHub as well as in various git tools.
  The footer should contain a [closing reference to an issue](https://help.github.com/articles/closing-issues-via-commit-messages/) if any.
  @@ -262,8 +262,8 @@ A detailed explanation can be found in this [document][commit-message-format].
  Please sign our Contributor License Agreement (CLA) before sending pull requests. For any code
  changes to be accepted, the CLA must be signed. It's a quick process, we promise!
  -* For individuals we have a [simple click-through form][individual-cla].
  -* For corporations we'll need you to
  +* For individuals, we have a [simple click-through form][individual-cla].
  +* For corporations, we'll need you to
  [print, sign and one of scan+email, fax or mail the form][corporate-cla].
  <hr>
  