Address some comments

docs/reference/configuration/keywords.rst

@@ -790,16 +790,16 @@ and/or history matching project.
 .. _gen_data:
 .. topic:: GEN_DATA
 
-        The ``GEN_DATA`` keyword is used to declare text files that are referred to by
-        :ref:`GENERAL_OBSERVATIONs <general_observation>`. It declares
-        text files which have been generated by the forward model, which will be
-        loaded by ert when loading general observations.
-        These text files are expected to follow the same naming scheme for all realizations
-        (ex: ``gd_%d`` which may resolve to ``gd_0``, ``gd_1`` where `%d` is the report step).
+        The GEN_DATA key is used to declare a response which corresponds to a
+        :ref:`GENERAL_OBSERVATION <general_observation>`. It expects to read a
+        text file produced by the forward model, which will be loaded by ert when
+        loading general observations. These text files are expected to follow the
+        same naming scheme for all realizations (ex: ``gd_%d`` which may resolve to
+        ``gd_0``, ``gd_1`` where `%d` is the report step).
         The contents of these result are always of this format:
         **exactly one floating point number per line**.
-        If we speak about "indexing" into a ``GEN_DATA`` file,
-        the "index" always refers to the row number, where the index 0 refers to the first row.
+        Indexing ``GEN_DATA``refers to row number in the forward model's output file,
+        where the index 0 refers to the first row.
         ``GEN_DATA`` will only affect the simulation if it is referred to by a
         :ref:`GENERAL_OBSERVATION <general_observation>`.
 
@@ -841,7 +841,7 @@ and/or history matching project.
                 GEN_DATA 4DWOC  RESULT_FILE:SimulatedWOC_%d.txt   REPORT_STEPS:0
 
         The ``4DWOC`` is an arbitrary unique key, ``RESULT_FILE:SimulatedWOC%d.txt``
-        means that ERT will look for results in the file ``ensembles/<ensemble>/<realization>/SimulatedWOC_0.txt``.
+        means that ERT will look for results in the file ``<runpath>/SimulatedWOC_0.txt``.
 
         The ``REPORT_STEPS:0`` is tightly bound to the ``%d`` integer format specifier
         in the result file - at load time the ``%d`` is replaced with the integer values