anchor.diff:          </li>
         </ul>
         <p>
  -        In short, the best way to make sure you have a healthy application is to comment on RFCs, use an up-to-date version of the CLI, keep your application clean of deprecations, and when possible, test your application against beta and canary releases of Ember.
  +        In short, the best way to make sure you have a healthy application is to comment on RFCs, clean up deprecations when you see them, and when possible, test your application against beta and canary releases of Ember.
         </p>
       </section>
     </article>
  
positive.code:           RFCs: Ember.js follows a community-driven process for its development that incorporates <a href="https://github.com/emberjs/rfcs">RFCs for features and deprecations.</a> An RFC is a Request for Comments. Before changes are made to Ember's API, they are proposed publicly and the community is asked to review and comment. Anyone can create an RFC, not just Core Team members. RFCs undergo many edits to incorporate community feedback. If a proposal has enough support, it is merged, meaning that work may begin to integrate the functionality into the codebase.
          </li>
          <li>
            Deprecations: The ember-cli informs developers of upcoming changes to the API via deprecation warnings. To see these warnings and <a href="http://emberjs.com/deprecations/">Deprecation Guides instructions</a> about how to resolve them, make sure you have the latest CLI. You can use newer CLI versions with older Ember app versions. It's a good idea to resolve deprecations as they arise, so that when new major versions are released, there is less overhead to upgrade.
          </li>
          <li>
            Codemods: When it's time for a major version upgrade, and there are syntax edits to make, tools like codemods are provided to help you make changes quickly. 
  
negative.code:       <h3 id="faq-future-proof">How do I future-proof my Ember.js application?</h3>
        
        <p>
          You should not try to future proof your application. Ember.js has a strong emphasis on developer productivity, which means that framework developers take great care when designing new functionality and provide migration paths. Here are some ways to keep up to date on future changes:
        </p>
  
        <ul>
  