anchor.diff:  
           <br />
   
  +        <h2>What about submissions that rely upon proprietary languages/development environments?</h2>
  +
  +        <p>We strongly prefer software that doesn't rely upon proprietary (paid for) development environments/programming languages. However, provided <em>your</em> submission meets our submission requirements (including having a valid open source license) then we will consider your submission for review. Should your submission be accepted for review, we may ask you, the submitting author, to help us find reviewers who already have the required development environment installed.</p>
  +
  +        <br />
  +
           <h2>What does a typical review process look like?</h2>
   
           <p>We encourage you to familiarize yourself with our <%= link_to "reviewer guidelines", "#reviewer_guidelines" %> as this will help you understand what our reviewers will be looking for. Broadly speaking though, provided you have followed our pre-submission steps and meet our submission requirements then you should expect a rapid review (typically less than two weeks).</p>
  
positive.code:       <div class="main" id="author_guidelines">
          <h1>Author guidelines</h1>
  
          <p class="lead">If you've already licensed your code and have good documentation then we expect that it should take <strong>less than an hour</strong> to prepare and submit your paper to JOSS.</p>
  
          <h2>What does a typical submission flow look like?</h2>
  
  
negative.code: 
          <h3>What happens if the software I'm reviewing doesn't meet the JOSS criteria?</h3>
          <p>We ask that reviewers grade submissions in one of three categories: 1) Accept 2) Minor Revisions 3) Major Revisions. Unlike some journals we do not reject outright submissions requiring major revisions - we're more than happy to give the author as long as they need to make these modifications/improvements.</p>
  
          <h3>What about submissions that rely upon proprietary languages/development environments?</h3>
  
          <p>As outlined in our author guidelines, submissions that rely upon a proprietary/closed source language or development environment are acceptable provided that they meet the other submission requirements and that you, the reviewer, are able to install the software &amp; verify the functionality of the submission as required by our reviewer guidelines.</p>
  
          <p>If an open source or free variant of the programming language exists, feel free to encourage the submitting author to consider making their software compatible with the open source/free variant.</p>
        </div>
  
        <div class="main" id="editorial_board">
  