diff --git a/content/feed/who-is-data-controller-for/index.md b/content/feed/who-is-data-controller-for/index.md
index d39c54a..da6d8dd 100644
--- a/content/feed/who-is-data-controller-for/index.md
+++ b/content/feed/who-is-data-controller-for/index.md
@@ -19,7 +19,7 @@ Would you grant self-serve data updates in SAS if there was no risk to the data
 
 ## Data Auditors
 
-Do you need to know who made a particular data change, what that change was, when it was made, and who signed it off? Every submission carries a full audit trail, and the original Excel file is retained alongside it, so the source of a change can be reviewed long after it was loaded.
+Do you need to know who made a particular data change, what that change was, when it was made, and who signed it off? Every submission carries a full audit trail, and any associated Excel file is retained alongside it, so the source of a change can be reviewed long after it was loaded.
 
 ## Data Managers
 
@@ -27,7 +27,7 @@ Do you want to load, modify or delete production data without writing repetitive
 
 ## Data Owners
 
-Do you like to review data changes before they are applied? Approvers see the diff - new, changed and deleted rows - and nothing lands until it is signed off. Email alerts can tell you when data is changed or about to change, and a completed load can trigger a SAS job downstream.
+Do you like to review data changes before they are applied? Approvers see the diff - new, changed and deleted rows - and nothing lands until it is signed off. Email alerts can tell you when data is changed or about to change, and a completed load can trigger a SAS job downstream. If the wrong change gets approved anyway, the table can be rolled back to a previous state - and the rollback is itself a new, reviewable change, so the audit trail keeps both the mistake and the correction.
 
 ## Purchasers