anchor.diff:  
       <ul>
         <li>Contribute to the software</li>
  -      <li>Report an issue with the software</li>
  +      <li>Report issues or problems with the software</li>
         <li>Seek support</li>
       </ul>
   
  
positive.code: 
      <blockquote>
        <p>
          Good: An automated test suite hooked up to an external service such as Travis-CI<br />
          OK: Documented manual steps that can be followed to check the expected functionality of the software (e.g. a sample input file to assert behaviour)<br />
          Bad (not acceptable): No way for you the reviewer to check the functionality of the software
        </p>
      </blockquote>
  
  
negative.code:     <ul>
        <li>A short abstract describing the high-level functionality of the software</li>
        <li>A list of the authors of the software</li>
        <li>Author affiliations</li>
        <li>A list of key references including a link to the software archive</li>
      </ul>
  
      <p>Note the paper should <em>not</em> include software documentation such as API functionality, as this should be outlined in the software documentation.</p>
  
      <h2>Software license</h2>
  
  