diff --git a/pages/docs/couple-your-code/couple-your-code-mesh-and-data-access.md b/pages/docs/couple-your-code/couple-your-code-mesh-and-data-access.md
index 7a4c0a65a7..a0bd9355f1 100644
--- a/pages/docs/couple-your-code/couple-your-code-mesh-and-data-access.md
+++ b/pages/docs/couple-your-code/couple-your-code-mesh-and-data-access.md
@@ -33,8 +33,18 @@ void Participant::writeData(
     precice::span<const double>   values)
 ```
 
-<!-- TODO Also point to section where `relativeReadTime` is explained? We will probably solve this in https://github.com/precice/precice.github.io/pull/257 -->
-Similarly, there is a `readData` API function for reading coupling data.
+Similarly, there is a `readData` API function for reading coupling data:
+
+```cpp
+void readData(
+    precice::string_view          meshName,
+    precice::string_view          dataName,
+    precice::span<const VertexID> vertices,
+    double                        relativeReadTime,
+    precice::span<double>         values) const;
+```
+
+We will talk about the additional argument `relativeReadTime` in detail in [the section on time interpolation](couple-your-code-waveform.html).
 
 Let's define coupling meshes and access coupling data in our example code: