fix (next steps): caught small formatting things identified earlier in #58

Author: njlyon0

mod_next-steps.qmd

@@ -46,7 +46,7 @@ The Environmental Data Initiative has developed the [ezEML app](https://edirepos
 
 -   **Provenance**: What original data sources did you draw on? You'll want your dataset to link to the original data sources so that they, too, receive credit for their work. In ezEML, data provenance information is associated with the methods metadata, and links are displayed on all EDI dataset landing pages.
 
--   **Reuse**: ezEML will ask you to decide on a license for reuse of your synthesized data. EDI and LTER recommend using a C[C-0 public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/) which allows reuse and adaptation without requiring a specific form of citation. Professional standards and EDI policy encourage citation, but preserving flexibility about the form of citation relieves downstream users from the obligation to cite data in ways that may not be workable for large syntheses. [CC-BY](https://creativecommons.org/licenses/by/4.0/deed.en) is also an acceptable license. It allows downstream users to re-share and adapt the licensed work, but requires that users "give appropriate credit, provide a link to the license, and indicate if changes were made."
+-   **Reuse**: ezEML will ask you to decide on a license for reuse of your synthesized data. EDI and LTER recommend using a [CC-0 public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/) which allows reuse and adaptation without requiring a specific form of citation. Professional standards and EDI policy encourage citation, but preserving flexibility about the form of citation relieves downstream users from the obligation to cite data in ways that may not be workable for large syntheses. [CC-BY](https://creativecommons.org/licenses/by/4.0/deed.en) is also an acceptable license. It allows downstream users to re-share and adapt the licensed work, but requires that users "give appropriate credit, provide a link to the license, and indicate if changes were made."
 
 -   **Sharing code**: Chances are, your code is already public on GitHub (and hopefully, well documented), but you'll want to create a persistent reference to the version of the code that you used to conduct *this* analysis. One way to go is to package your code along with your data on EDI. That approach makes the code findable, because it is right there with the data, but the code remains static, and it can be difficult to represent the software package structure and release history. Many researchers now prefer to release their GitHub repository [code on Zenodo](https://docs.github.com/en/repositories/archiving-a-github-repository/referencing-and-citing-content) and reference the specific release with their dataset in EDI or another repository. This allows continued development of code in the repository, while linking together the dataset and the code for creating or analyzing it. This approach is great for synthesis groups that will continue adding new data, analyses, or publications in the future.
 
@@ -106,7 +106,7 @@ For example, say your original project was focused on understanding what factors
 -  the effect of the same factors on the mobilization of nutrients in soil; or 
 -  scaling the analysis to forecast the impact on carbon sinks under alternative climate scenarios. 
 
-In addition to the standard science funding agencies such as NSF, NASA, DOE, or USDA, your list of stakeholders might include: farmers, fertilizer suppliers, extension professionals, carbon markets, climate modelers…
+In addition to the standard science funding agencies such as NSF, NASA, DOE, or USDA, other interested parties: farmers, fertilizer suppliers, extension professionals, carbon markets, climate modelers...
 
 Note these along with the nature of their interest.