deletions | additions       diff --git a/Linking Code.md b/Linking Code.md  index fd448ca..9b64a0f 100644  --- a/Linking Code.md  +++ b/Linking Code.md 
...
## Links to Software  By combining tools discussed elsewhere in this document, once can "mint" digital object identifiers that point to a particular version of software, assuming it is stored in an organized repostitory. One example is given here: https://guides.github.com/activities/citable-code/, on a web page that shows how to mint a citable DOI for code using the [GitHub](http://github.com) and [Zenodo] (http://zenodo.org) services together. In a model more directly akin to publishing code in exactly the way one currently publishes a paper, services like the [Astrophysics Source Code Library (ASCL)](ascl.net) allow authors to publish a static version of a program, and to assign that version an identifier. At present, The ASCL is indexed by the SAO/NASA Astrophysics Data System (ADS) and is citable by using the unique ascl ID assigned to each program.  ## Executable Figures  iPython Notebooks offer a nice modern example of how published figures can be made "executable." These notebooks act as code that can be annotated and executed on the web, allowing an interested reader to study and even modify a copy of the underpinning code, without contacting the authors or initiating a long investigation.[iPython example from Hope's figure]  xx AG clean up this info: The ASCL is indexed by  the SAO/NASA Astrophysics Data System (ADS) and is citable by using dust map of Ophiuchus inserted as a figure below (courtestsy of Hope Chen) offers an example of  the unique ascl ID assigned to each code. xx iPython functionality.