anchor.diff:            <br/>
   
             <p>
  -            We recommend setting the 
  +            We recommend setting the
               <a href="https://guides.rubygems.org/setting-up-multifactor-authentication/#authentication-levels" target="_blank">MFA level</a>
               to <b><i>UI and API</i></b>. However, <b><i>UI and gem signin</i></b> is acceptable too.
             </p>
  
positive.code:           <br/>
  
            <p>
              We recommend setting the 
              <a href="https://guides.rubygems.org/setting-up-multifactor-authentication/#authentication-levels" target="_blank">MFA level</a>
              to <b><i>UI and API</i></b>. However, <b><i>UI and gem signin</i></b> is acceptable too.
            </p>
  
negative.code:         <p>
            On August 15, 2022, we will begin requiring maintainers of packages with more than 180 million downloads to have multi-factor authentication (MFA) enabled.
            If maintainers don't have MFA enabled by this date, a number of operations will be restricted.
            These restrictions include <a href="https://guides.rubygems.org/mfa-requirement-opt-in/#privileged-operations" target="_blank">privileged operations</a> (ie. push, yank, add/remove owners).
            Furthermore, we are officially recommending that maintainers of packages with more than 165 million downloads enable MFA.
            This recommendation will also be shown by the gem CLI.
          </p>
          <br/>
  
          <% if @user.mfa_disabled? %>
            <p>
              We're notifying you of this policy because you maintain at least one gem that has more than 165 million downloads.
              So, we'd like to ask you to <b>please enable multi-factor authentication on your RubyGems account 🙏.</b>
  