Address PR comments in README.md

README.md

@@ -196,7 +196,7 @@ The `dfe:analytics:install` generator will also initialize some empty config fil
 | `config/analytics_blocklist.yml`      | Autogenerated file to list all fields we will NOT send to BigQuery, to support the `analytics:check` task                                                                                              |
 | `config/analytics_custom_events.yml`  | Optional file including list of all custom event names                                                             |
 
-**It is imperative that you perform a full check of the fields that are being sent, exclude those for which you have no legal basis for processing under GDPR in `config/analytics_blocklist.yml`, and exclude those containing personally-identifiable information (PII) in `config/analytics_hidden_pii.yml`, in order to comply with the requirements of the [Data Protection Act 2018](https://www.gov.uk/data-protection), unless an exemption has been obtained. Further guidance on this is available [here](./docs/deciding_what_data_to_stream_with_dfe_analytics.md).**
+**It is imperative that you perform a full check of the fields that are being sent to ensure that you have a legal basis for processing them under GDPR, as set out in your service's Data Protection Impact Assessment (DPIA). You must exclude fields for which you have no basis for processing in ```config/analytics_blocklist.yml```, and exclude those which you do have a legal basis for processing but which contain human-readable personally identifiable information (PII) in ```config/analytics_hidden_pii.yml```. This is in order to comply with the requirements of the [Data Protection Act 2018](https://www.gov.uk/data-protection). Further guidance on this is available [here](./docs/deciding_what_data_to_stream_with_dfe_analytics.md).**
 
 When you first install the gem, none of your fields will be listed in `analytics.yml`, so no data will be sent to BigQuery. To get started, generate a blocklist using this command: