Updating BP Make feedback available

bp.html

@@ -3048,7 +3048,7 @@ <h4 class="subhead">Possible Approach to Implementation</h4>
           <p>New versions of the dataset can be posted to the Web on a regular schedule, following the <a href="#dataVersioning">Best Practices for Data Versioning</a>. Posting to the Web can be made a part of the release process for new versions of the data. Making Web publication a deliverable item in the process and assigning an individual person as responsible for the task can help prevent data becoming out of date. To set consumer expectations for updates going forward, you can include human-readable text stating the expected publication frequency, and you can provide machine-readable metadata indicating the frequency as well. </p>
 
           <aside class="example">
-            <p>Suppose that the update frequency of the bus stops dataset is annual. In order to describe the frequency with which new data is added to the dataset, the property <code>dct:accrualPeriodicity</code> can be used. A new version of the dataset (<code> bus-stops-2016-05-05 </code>) is created to reflect the update schedule of the data. It is important to note that new versions can be created sooner than the schedule calls for, but the publisher should ensure that extra versions are published to the Web as quickly as their scheduled counterparts.
+            <p>Suppose that the update frequency of the bus stops dataset is annual. In order to describe the frequency with which new data is added to the dataset, the property <code>dct:accrualPeriodicity</code> can be used. A new version of the dataset (<code>bus-stops-2016-05-05</code>) is created to reflect the update schedule of the data. It is important to note that new versions can be created sooner than the schedule calls for, but the publisher should ensure that extra versions are published to the Web as quickly as their scheduled counterparts.
              <pre class="highlight">
    :bus-stops-2016-05-05
       a dcat:Dataset ;
@@ -3670,14 +3670,14 @@ <h4 class="subhead">Benefits</h4>
       <!-- begin of BP Information about Feedback -->
       <div class="practice">
         <p><span id="FeedbackInformation" class="practicelab">Make feedback available</span></p>
-        <p class="practicedesc">Make feedback about datasets and distributions publicly available.</p>
+        <p class="practicedesc">Make consumerfeedback about datasets and distributions publicly available.</p>
         <section class="axioms">
           <h4 class="subhead">Why</h4>
-          <p>Making feedback about datasets and distributions publicly available allows consumers to become aware of other data consumers and supports a collaborative environment. User community experiences, concerns or questions currently being addressed can also be shared. </p>
+          <p>By sharing feedback with consumers, publishers can demonstrate to users that their concerns are being addressed, and they can avoid submission of duplicate bug reports. Sharing feedback also helps consumers understand any issues that may affect their ability to use the data, and it can foster a sense of community among them.</p>
         </section>
         <section class="outcome">
           <h4 class="subhead">Intended Outcome</h4>
-          <p>Data consumers will be able to assess feedback provided by other data consumers and therefore to know their opinion about a specific dataset or distribution.</p>
+          <p>Consumers will be able to assess the kinds of errors that affect the dataset as well as consumers ratings and opinions, and be reassured that the publisher is actively addressing issues as needed.</p>
         </section>
         <section class="how">
           <h4 class="subhead">Possible Approach to Implementation</h4>
@@ -3735,7 +3735,7 @@ <h4 class="subhead">Possible Approach to Implementation</h4>
         </section>
         <section class="test">
           <h4 class="subhead">How to Test</h4>
-          <p>Check if the feedback given by a data consumer on a specific dataset or distribution is publicly available. </p>
+          <p>Check that any feedback given by data consumers for a specific dataset or distribution is publicly available.</p>
         </section>
         <section class="ucr">
           <h4 class="subhead">Evidence</h4>