Update doi.md

Re-wrote the paragraphs for DOIs and the 3 rs levels. Many of the level-specific descriptors applied to all levels. As it was it either resulted in a suggestion of exclusion or resulted in repetition. (Note that the prev. version included some Dave edits, but this issue was also true pre-Dave edits.)

rs-impact/doi.md

@@ -21,16 +21,16 @@ Open Data, Open Source Software, and Open Publication Access form the foundation
 
 ### DOI and Research Software
 
-As discussed in the previous section, DOIs ensure the ciability of research outputs, which include research software. DOIs are crucial to the [three levels of reproducible research software](https://mcmasterrs.github.io/lm_reproducible-rs/smp/smp.html#reproducibility-goal): research software for publication, research software as a tool and research software as infrastructure.  
+As discussed in the previous section, DOIs ensure the ciability of research outputs, which include research software. DOIs are crucial to the [three levels of reproducible research software](https://mcmasterrs.github.io/lm_reproducible-rs/smp/smp.html#reproducibility-goal): research software for publication, research software as a tool and research software as infrastructure. DOIs are important for all three levels of research software.
 
-In the context of research software for publication, research that used software for critical or novel elements of the research or results should be cited in the publication. In this case, the specific version of the software used should be referenced. In this way DOIs provide an essential service for these specific citations with preserved meta-data about the software and version, and a location to find this specific software version.
+Software used for critical or novel elements of the research or results should be cited in the publication. In this case, the specific version of the software used should be referenced. In this way DOIs provide an essential service for these specific citations with preserved meta-data about the software and version, and a location to find this specific software version relevant to the research.
 
-For research software as a tool and in publications, DOIs allow for the tracking of citations and usage metrics of the software. This provides valuable data on how the software is being used in the research community as well as its impact and reach, which can inform future support and development, and demonstrate its value to funders and stakeholders.  
+The use of DOIs provides the ability to measure citation counts and usage metrics of the software. These data provide valuable data on how the software is being used in the research community as well as its impact and reach. These data inform future support and development, and document its value to funders and stakeholders.  
 
-While in the context of research software as infrastructure, DOIs not only enable the tracking of how and where the software is cited and used across different research publications and projects, DOI references to this infrastracture software facilitate standardization and compilance, so that results can be compared to like results.
+When the research software is designed for broader use, using DOIs to cite this infrastracture research software facilitates standardization and consistency, so that results can be compared to like results.
 
 Many funding agencies, journals and institutions are increasingly requiring that research outputs, including software, be assigned DOIs. This requirement helps to ensure compliance with funding requirements as well as to promote best practices in research asset management.  
 
-Research software often have multiple versions and releases. Each version may contain subtle changes that can result in different outputs so specific versions of software can be crucial for reproducibility and verification. A DOI can be created for a software project pointing to the collection of versions, as well as separate DOIs for each specific version. DOI systems will link projects and versions bi-directionally making it easy for a link to one to find the other, and each to be presented in the context of the other. In this way DOIs provide a robust mechanism for research software projects and versions: researchers can easily reference the specific version of the software they used to generate results, such as for publications and citations, and research users can easily find software project and it's latest version for reuse.
+Research software often have multiple released versions. Each version may contain subtle changes, which can result in different outputs so specific versions of software can be crucial for reproducibility and verification. A DOI can be created for a software project generally, which points to the collection of released and preserved versions of the project. A DOI can also be created for each specific version. DOI systems will link projects and versions bi-directionally making it easy for a link to one to find the other, and each to be presented in the context of the other. In this way DOIs provide a robust mechanism for research software projects and versions: research can reference the specific version of the software used to generate results, which is ideal for publications and citations, and users can easily find a research software project and its latest version for reuse.
 
 DOIs are widely recognized and integrated into academic databases, libraries and indexing services. This integration helps ensure that research software can be found easily, and accessed by researchers across different platforms and disciplines. Some notable examples are [Zenodo](https://zenodo.org/) by CERN (European Organization for Nuclear Research) and the [Research Software Directory](https://research-software-directory.org/) by the Netherlands eScience Center.