anchor.diff:              Practice accepting feedback graciously.
             </li>
             <li>
  -            Practice giving feedback respectfully.
  +            Practice providing feedback respectfully.
             </li>
           </ul>
   
           <h2>Conversations</h2>
  -        <p>The code is a conversation starter. The interesting part begins when you begin having discussions with your peers about the nuances that you see. What do you like? What do they dislike? What are the trade-offs? How can the code be improved?</p>
  -        <p>Curious about what this might look like? <a href="/conversations/1">See this conversation</a> that happened on the Ruby track.</p>
  +        <p>The code is only the beginning.  It is a conversation starter. The fun begins when you discuss, with your peers, nuances and variety in perspectives about the problem the code is intended to solve.   What do you like? What do they dislike? What were the "tough choices" you had to make? What are the trade-offs? How can the code be improved?</p>
  +        
  +        <p>Curious about what this might look like? <a href="/conversations/1">Here is a conversation</a> from the Ruby track.</p>
   
           <h2>Open Source</h2>
  -        <p>Contributing to open source can be very intimidating. It's scary to put your code in front of strangers. It's terrifying to be presented with problems that you probably don't understand, and don't know how to trouble-shoot.</p>
  +        <p>Contributing to Open Source Software can be very intimidating. It's scary to expose your code to strangers. It's terrifying to be presented with problems that you probably don't understand, and don't know how to even approach.  These are feelings that ALL developers have had.  And the more experienced - those whom you look up to - overcame it with practice and active participation.</p>
         </div>
       </article>
       <article class="article-block">
  
positive.code:           In February 2013 I joined Jumpstart Lab as a developer and co-instructor for their 6-month full-time developer training program. One of the things we implemented
            was a daily programming warm-up exercise. At first, this was simply a README, then we added a test suite to help guide the students and let them get a taste of what TDD feels like. After a few months we had a number of pain points that we wanted to address:
          </p>
          <p>We had to manually upload a new warmup every morning</p>
          <ul class="list">
            <li>The students often did not finish exercises</li>
            <li>The students didn't get feedback on the code they wrote</li>
          </ul>
          <p>I decided to try to combine these ideas into an app, and launched a very rough prototype to the students in late June 2013.</p>
          <p>
            It came as a complete surprise to me that the project hit a nerve with people. I expected dozens of people to use the site. Within the first couple of months, over 1,000 people had submitted over 10,000 pieces of code.
          </p>
        </div>
      </article>
    </section>
  
negative.code:   <section class="main">
      <article class="article-block">
        <div class="article-contents">
          <h2><u>Exer</u>cises and Criti<u>cism</u></h2>
          <p>
            <ul>
              <li>There is immense value in comments and critiques of your code by your peers.</li>
              <li>You grow and improve your ability to <strong>write code</strong> by <strong>reading others' code</strong> and commenting on it.</li>
            </ul>
            This is the essence of Exercism.</p>
          <p>Exercism is your place to engage in thoughtful conversations about code. Explore simplicity, idiomatic language features, and expressive readable code.</p>
  
          <h2>Practice</h2>
          <ul class="list">
  