diff --git a/docs/30_data/30_data_organisation.mdx b/docs/30_data/30_data_organisation.mdx
index 43062422..34d2d125 100644
--- a/docs/30_data/30_data_organisation.mdx
+++ b/docs/30_data/30_data_organisation.mdx
@@ -85,11 +85,11 @@ Consider the way data and [Metadata](/docs/metadata/) can be stored together as
 - technical metadata
 - structural metadata
 
-An FDO encapsulates data and metadata in one file and can be saved as an [HDF5](https://www.hdfgroup.org/solutions/hdf5/), for example. See [Data Format Standards](/docs/data_formats/) for more information.
+An FDO encapsulates data and metadata in one file and can be saved as an [HDF5](https://www.hdfgroup.org/solutions/hdf5/), for example. See [Data Formats](/docs/data_formats/) for more information.
 
 ## Files: formats
 
-Different disciplines use established standards, see [Data Format Standards](/docs/data_formats/). Also consider beyond the duration of the project:
+Different disciplines use established standards, see [Data Formats](/docs/data_formats/). Also consider beyond the duration of the project:
 
 - usage of proprietary or open file formats
 - exchange within and outside of the working group
diff --git a/docs/30_data/40_data_documentation.mdx b/docs/30_data/40_data_documentation.mdx
index 6dda2a0d..947e7a36 100644
--- a/docs/30_data/40_data_documentation.mdx
+++ b/docs/30_data/40_data_documentation.mdx
@@ -49,7 +49,7 @@ The result should be a set of descriptive documents associated with the files us
 
 ### Technical implementations
 
-Get an overview of the occurring data and document flows. A short description, easy to understand for every user, should be accessible on a low level and explain the main concepts. The data itself needs to have a bulletproof [Data Organisation](/docs/data_organisation), including [Metadata](/docs/metadata/) and suitable [Data Format Standards](/docs/data_formats/). Find out more about the usual [Best Practice](/docs/best_practice/) at your institute or within your discipline. Plan how documents can be shared between project staff and what needs to be accessed for [Data Publication](/docs/data_publishing/) with [PIDs](/docs/pid/).
+Get an overview of the occurring data and document flows. A short description, easy to understand for every user, should be accessible on a low level and explain the main concepts. The data itself needs to have a bulletproof [Data Organisation](/docs/data_organisation), including [Metadata](/docs/metadata/) and suitable [Data Formats](/docs/data_formats/). Find out more about the usual [Best Practice](/docs/best_practice/) at your institute or within your discipline. Plan how documents can be shared between project staff and what needs to be accessed for [Data Publication](/docs/data_publishing/) with [PIDs](/docs/pid/).
 
 Data security affects all technical and organisational issues to protect the data from alteration, loss, and destruction. In this context, storage methods, backup procedures, necessary physical resources as well as automated and administrative routines must be planned and put in place. Ask local contacts or external experts about already established technologies for [Data Storage and Archiving](/docs/data_storage) as well as suitable [Repositories](/docs/repositories/).
 
diff --git a/docs/50_data_publication/00_data_publishing.mdx b/docs/50_data_publication/00_data_publishing.mdx
index ae264c73..4968b55d 100644
--- a/docs/50_data_publication/00_data_publishing.mdx
+++ b/docs/50_data_publication/00_data_publishing.mdx
@@ -12,7 +12,7 @@ This page applies to all researchers who want to publish their data.
 
 In chemical research, we strive to share results with others, commonly through articles in renowned scientific journals. To be able to actually work with and build upon these results, the scientific community also requires the data that the results were based on.
 
-Publishing and therefore sharing these chemistry research data in a [FAIR](/docs/fair) manner adds value to the research results and enables discovery and reuse. For this purpose it is important to consider aspects such as rich [metadata](/docs/metadata), provenance information, information on the [license](/docs/licences) applied, [persistent identifiers](/docs/pid), [data formats standards](/docs/data_formats) for analytical data, and [machine-readable chemical structures](/docs/machine-readable_chemical_structures).
+Publishing and therefore sharing these chemistry research data in a [FAIR](/docs/fair) manner adds value to the research results and enables discovery and reuse. For this purpose it is important to consider aspects such as rich [metadata](/docs/metadata), provenance information, information on the [license](/docs/licences) applied, [persistent identifiers](/docs/pid), [data formats](/docs/data_formats) for analytical data, and [machine-readable chemical structures](/docs/machine-readable_chemical_structures).
 
 To publish data is essential to ensure that findings are transparent and reproducible. Moreover, it prevents duplicate efforts to generate data; hence, data publishing is also a measure of (ecological) sustainability.