diff --git a/README.md b/README.md
index df045e0..ac5c9a1 100644
--- a/README.md
+++ b/README.md
@@ -20,8 +20,8 @@ In majority of the cases, used Consent forms simply did not include any provisio
 Situation is particularly tricky because major granting agencies (e.g. NIH, NSF, RCUK) nowadays require public data sharing, but do not provide explicit instructions on how.
 
 To facilitate neuroimaging data sharing, we providing an "out of the box" solution addressing aforementioned human research participants concerns and consisting of
-- widely acceptable consent forms (with various translations) allowing deposition of anonymized data to public data archives
-- collection of tools/pipelines to help anonymization of neuroimaging data making it ready for sharing
+- widely acceptable consent forms (with various translations) allowing deposition of de-identified data to public data archives
+- collection of tools/pipelines to help de-identification of neuroimaging data making it ready for sharing
 
 ### Contributing
 
@@ -103,4 +103,4 @@ Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/d
 
 <!-- ALL-CONTRIBUTORS-LIST:END -->
 
-This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
\ No newline at end of file
+This project follows the [all-contributors](https://github.com/all-contributors/all-contributors) specification. Contributions of any kind welcome!
diff --git a/docs/source/README.rst b/docs/source/README.rst
index ce133b9..f82e5d1 100644
--- a/docs/source/README.rst
+++ b/docs/source/README.rst
@@ -39,7 +39,7 @@ concerns and consisting of
 
 - a template data user agreement (if your repository allows DUA instead of a licence)
 
-- collection of tools/pipelines to help anonymization of neuroimaging
+- collection of tools/pipelines to help de-identification of neuroimaging
   data making it ready for sharing
 
 You can read a summary of this work in our post-print: `The Open Brain Consent: Informing research participants and obtaining consent to share brain imaging data <https://psyarxiv.com/f6mnp/>`_
@@ -67,13 +67,13 @@ within the same jurisdiction. Although somewhat a utopian statement,
 we hope that with examples/precedent cases and possibly **your**
 enthusiastic involvement we cold achieve our goal.
 
-Anonymization
-=============
+De-identification
+=================
 
 Data must be de-identified before distribution.  We will collect
 information on :ref:`existing <chap_anonymization_tools>` and
 possibly establishing an *ultimate* easy to use pipeline to
-standardize anonymization of neuroimaging data to simplify data
+standardize de-identification of neuroimaging data to simplify data
 sharing.
 
 
diff --git a/docs/source/anon_tools.rst b/docs/source/anon_tools.rst
index 98a2416..c3cf4e1 100644
--- a/docs/source/anon_tools.rst
+++ b/docs/source/anon_tools.rst
@@ -33,7 +33,7 @@ One of the approaches is perform complete skull stripping, e.g. using
   of `AFNI <http://afni.nimh.nih.gov/>`_
 -  `FreeSurfer <https://surfer.nmr.mgh.harvard.edu/>`_
 
-Some dedicated anonymization tools work on this principle, e.g. `DeID`_
+Some dedicated de-identification tools work on this principle, e.g. `DeID`_
 
 Faces/dental stripping
 ~~~~~~~~~~~~~~~~~~~~~~
diff --git a/docs/source/gdpr/credit.rst b/docs/source/gdpr/credit.rst
index d93f43e..3b5bed3 100644
--- a/docs/source/gdpr/credit.rst
+++ b/docs/source/gdpr/credit.rst
@@ -34,8 +34,8 @@ Workshop Participants
 Issues addressed during the workshop
 =====================================
 
-Anonymization
--------------
+De-identification
+-----------------
 
 Following the OBC, data must be de-identified before distribution. However, it has become clear that one can single out subjects from biomedical data and/or MRI scans (including fMRI profiles from connectivity). This means that changes to the data (removing ID and defacing) is only a pseudo-anonymization procedure and according to GDPR, that procedure leaves the data as 'personal' (as opposed to 'anonymized').
 
diff --git a/docs/source/gdpr/data_user_agreement.rst b/docs/source/gdpr/data_user_agreement.rst
index 80d7332..dedb218 100644
--- a/docs/source/gdpr/data_user_agreement.rst
+++ b/docs/source/gdpr/data_user_agreement.rst
@@ -8,7 +8,7 @@ A DUA does not provide a legal basis to share personal data (the consent does).
 .. _Data User Agreement (DUA):
 
 This template is based on the `Donder’s Institute DUA Version RU-DI-HD-1.0 <https://data.donders.ru.nl/doc/dua/RU-DI-HD-1.0.html?2>`_.
-Given that brain imaging data can be used to identify individuals, it is safe to consider them as 'personal data' under the `GDPR <https://gdpr-info.eu/>`_, even after using a pseudo-anonymization procedure like defacing (see our information on :ref:`(peudo)anonymization tools <chap_anonymization_tools>`.
+Given that brain imaging data can be used to identify individuals, it is safe to consider them as 'personal data' under the `GDPR <https://gdpr-info.eu/>`_, even after using a pseudo-anonymization procedure like defacing (see our information on :ref:`de-identification tools <chap_anonymization_tools>`.
 
 To allow sharing of such personal data, it is recommended to use a Data User Agreement (DUA) over a license. The term "license" is more general than DUA, but both are "contracts" between a licensor and licensee.