--- 0.20200227.1-CC.txt	2020-02-27 07:12:50.137521863 +0000
+++ 0.20200227.2-CC-WM.txt	2020-02-27 16:18:36.405180683 +0000
@@ -1,7 +1,7 @@
 PeeringDB Data Ownership Policy Document
 
 Date: TBD
-Version: 0.20200227.1-CC
+Version: 0.20200227.2-CC-WM
 
 1) Background
 
@@ -11,7 +11,7 @@
 been raised relating to who owns the data in PeeringDB when more than one 
 party is involved (ex: netixlan, ixfac, netfac).
 
-A call for participation to the task Force was made on September 10th, 
+A call for participation to the Task Force was made on September 10th, 
 2019.
 
 2) Scope
@@ -75,7 +75,7 @@
 order help resolve matters.
 
 The Admin Committee has their own ticketing and logging systems as they 
-deal with user data. This task force recommends this practice continue as 
+deal with user data. The Task Force recommends this practice continue as 
 having audit trails of all data is good practice.
 
 3.4) Conflicted Data
@@ -517,9 +517,10 @@
   published until a resolution process has been mediated by the Admin 
   Committee.
 
-  PeeringDB may also employ user interface methods to encourage data 
-  harmony between a Network and an Internet Exchange, as a means of 
-  expediting resolution and decreasing the burdens on the Admin Committee.
+  The Task Force recommends PeeringDB employ user interface methods and 
+  email notifications to encourage data harmony between a Network and an 
+  Internet Exchange, as a means of expediting resolution and decreasing 
+  the burdens on the Admin Committee.
 
 - Example:
   - Query: https://www.peeringdb.com/api/netixlan/#