condense and make neutral

Author: mlinksva

_articles/legal.md

@@ -113,7 +113,7 @@ Also, by adding "paperwork" that some believe is unnecessary, hard to understand
 Some situations where you may want to consider an additional contributor agreement for your project include:
 
 * Your lawyers want all contributors to expressly accept (_sign_, online or offline) contribution terms, perhaps because they feel the open source license itself is not enough (even though it is!). If this is the only concern, a contributor agreement that affirms the project's open source license should be enough. The [jQuery Individual Contributor License Agreement](https://contribute.jquery.org/CLA/) is a good example of a lightweight additional contributor agreement.
-* For some projects, all you or your lawyers may want is a simple representation that a developer was authorized to contribute their contribution. Would you want to accept a contribution from someone who could not represent they were authorized to contribute that contribution? A [Developer Certificate of Origin](https://developercertificate.org/) requirement can be a simple option. There is also a very useful tool to automate enforcement of the DCO on your repository called the [DCO Probot](https://github.com/probot/dco). One key difference with a CLA is the DCO `signed-off-by` representation is made on every commit, whereas CLAs are signed once and forgotten. This is what the [Node.js community](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md) uses today instead of their prior CLA requirement. It's also important to know many projects that have a CLA will also require a DCO so that the community can have confidence each commit was authorized.
+* You or your lawyers want developers to represent that each commit they make is authorized. A [Developer Certificate of Origin](https://developercertificate.org/) requirement is how many projects achieve this. For example, the Node.js community [uses](https://github.com/nodejs/node/blob/master/CONTRIBUTING.md) the DCO [instead](https://nodejs.org/en/blog/uncategorized/notes-from-the-road/#easier-contribution) of their prior CLA. A simple option to automate enforcement of the DCO on your repository is the [DCO Probot](https://github.com/probot/dco).
 * Your project uses an open source license that does not include an express patent grant (such as MIT), and you need a patent grant from all contributors, some of whom may work for companies with large patent portfolios that could be used to target you or the project's other contributors and users. The [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) is a commonly used additional contributor agreement that has a patent grant mirroring the one found in the Apache License 2.0.
 * Your project is under a copyleft license, but you also need to distribute a proprietary version of the project. You'll need every contributor to assign copyright to you or grant you (but not the public) a permissive license. The [MongoDB Contributor Agreement](https://www.mongodb.com/legal/contributor-agreement) is an example this type of agreement.
 * You think your project might need to change licenses over its lifetime and want contributors to agree in advance to such changes.