Make paper high-level

[kelle]

" the paper reads more like documentation than like a paper. Software papers should be a little different from documentation, and should include for example more about how the package compares to alternatives, and explaining some design choices in more detail. Installation instructions are much too specific to go in a paper, since they may become obsolete on ~ 1-2 year timescales. Examples of usage are of course fine, but a paper should be reasonably high-level and does not need to be a complete manual."