diff --git a/understanding/20/headings-and-labels.html b/understanding/20/headings-and-labels.html
index e619a4df6d..fb98a2fd10 100644
--- a/understanding/20/headings-and-labels.html
+++ b/understanding/20/headings-and-labels.html
@@ -11,7 +11,7 @@ <h1>Understanding Headings and Labels</h1>
    <section id="brief">
       <h2>In brief</h2>
       <dl>
-         <dt>Goal</dt><dd>A page's content is described in headings and labels</dd>
+         <dt>Goal</dt><dd>A page's content is described by headings and labels</dd>
          <dt>What to do</dt><dd>Provide descriptive headings and labels</dd>
          <dt>Why it's important</dt><dd>People can orient themselves, especially those with cognitive or visual disabilities.</dd>
       </dl>
@@ -34,12 +34,12 @@ <h2>Intent of Headings and Labels</h2>
          <p>Note that the same image can be interpreted differently in different contexts. However, it can still be considered descriptive if its use is commonly understood in each context. For example, when accompanying a text field, a loupe or magnifying glass icon with text alternative of "Search" is commonly interpreted as indicating the field is for entering and submitting a search query.</p>
         <p>Placed on or near another image, a loupe or magnifying glass icon is commonly interpreted as a means to view a magnified version of the image (for instance, acting as a mechanism to zoom into the image, or opening a full-sized image in a new window).</p>
       
-      <p>This success criterion requires that if headings or labels are provided, they be descriptive. This success criterion does not require headings or labels; labels for inputs are covered separately by <a href="labels-or-instructions">3.3.2 Labels or Instructions</a>.  This success criterion also
-         does not require that content acting as a heading or label be correctly marked up or
+      <p>This success criterion requires that <em>when</em> headings or labels are provided, that they be descriptive. This success criterion does not address if headings or labels need to be provided. Providing section headings to organize the content is covered separately by <a href="section-headings">2.4.10 Section Headings</a>. Providing labels for inputs are covered separately by <a href="labels-or-instructions">3.3.2 Labels or Instructions</a>.  This success criterion also
+         does not address content acting as a heading or label being correctly marked up or
          identified — that aspect is covered separately by
          <a href="info-and-relationships">1.3.1: Info and Relationships</a>. It is possible for content
          to pass this success criterion (providing descriptive content that acts as headings or labels) while failing
-         Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up/identified). Conversely,
+         Success Criterion 1.3.1 (if the headings or labels aren't correctly marked up or identified). Conversely,
          it is also possible for content to pass Success Criterion 1.3.1 (with headings or labels correctly
          marked up or identified), while failing this success criterion (if those headings or labels are inaccurate or insufficiently clear).
       </p>
@@ -49,9 +49,6 @@ <h2>Intent of Headings and Labels</h2>
          for controls and inputs to have an appropriate accessible name (e.g. using <code>aria-label="…"</code>)
          and therefore pass Success Criterion 4.1.2, but to still fail this success criterion (if the label is inaccurate or insufficiently clear or descriptive).
       </p>
-      <p>This success criterion does not require the use of labels; however, it does require that if labels are present, they must be accurate and sufficiently clear or descriptive. Please see <a href="labels-or-instructions">3.3.2: Labels or Instructions</a> for more information on the use of labels.
-      </p>         
-      
    </section>
    <section id="benefits">
       <h2>Benefits of Headings and Labels</h2>