deletions | additions       diff --git a/Rule 6. Publish your code.md b/Rule 6. Publish your code.md  index 3504e14..f5ec593 100644  --- a/Rule 6. Publish your code.md  +++ b/Rule 6. Publish your code.md 
...
# Rule 6. Publish your code (even the small bits).  Did you write any code to run your analysis? No matter how buggy and insignificant you may find it, publish it. Your code, even the shortest script (whether or not you are proud of its quality), can be an important component for understanding your data and how you got your results \cite{Barnes_2010}. Software plays several roles in relation to data and scientific research. research \cite{iroff_Mink_Hanisch_DuPrie_2013}.  Often, the highest fidelity way to document the provenance of your data is the software and the code that were used. In other cases, software is the primary data product (e.g., new algorithms). Sharing as much of the software used in the provenance of your other data products enhances transparency and reproducibility. The use of open source software when possible reduces barriers for subsequent users of your software related data products. \cite{Prlic_Procter_2012} The same best practices discussed above in relation to data and workflow also apply to software materials: cite the software that you use and provide unique, persistent identifiers to the code you share.\cite{iroff_Mink_Hanisch_DuPrie_2013}