[web][doc] minor modification in toolchains and dataformats

doc/user/dataformats/guide.rst

@@ -37,7 +37,7 @@ communicate in an orderly manner. For more detailed information see :ref:`beat-s
    Data formats are named using three values joined by a ``/`` (slash)
    operator. The first value is the **username**.
 
-   The ``system`` user, provides a number of `pre-defined formats such as
+   The ``system`` user, provides a number of pre-defined formats such as
    integers, booleans, floats and arrays
    <https://www.beat-eu.org/platform/dataformats/system/>`_. You may also
    browse `publicly available data formats`_ to see all available data formats

doc/user/toolchains/guide.rst

@@ -30,43 +30,6 @@
 Toolchains are the backbone of experiments within the |project| platform. They
 determine the data flow for experiments in the |project| platform. For more information about toolchanis see :ref:`beat-system-toolchains`.
 
-You can see an example toolchain for a toy-`eigenface`_ system on the image
-below.
-
-.. image:: img/eigenfaces.*
-
-
-From this block diagram, the platform can identify all it requires to conduct
-an experiment with this workflow:
-
-  * There are three types of blocks:
-
-    1. **Dataset blocks** (light yellow, left side): are the input blocks of a
-       toolchain. They only have outputs.
-    2. **Regular blocks** (gray): represent processing steps of the toolchain.
-    3. **Analysis blocks** (light blue, right side): is the output of a
-       toolchain. They only have inputs.
-
-  * Each block defines *place holders* for datasets and algorithms to be
-    inserted when the user wants to execute an experiment based on such a
-    toolchain (see the :ref:`experiments` section).
-
-  * Each block is linked to the next one via a **connection**. The sequence of
-    blocks in a toolchain and their connectivity defines a natural data flow.
-    Data is output by data sets on the left and flow to the right until a
-    result is produced.
-
-  * Each dataset block (light yellow, left side) define a unique
-    *synchronization channel*, which is encoded in the platform via a color.
-    For example, the sychronization channel ``train`` is blue. The
-    synchronization channel ``templates`` is green and, finally, the
-    synchronization channel ``probes`` is red.
-
-  * Each regular or analysis block on the toolchain respects exactly one of
-    these synchronization channels. This is indicated by the colored circle on
-    the top-right of each block. For example, the block called ``scoring`` is
-    said to be *synchronized with* the ``probes`` channel.
-
 
 The *Toolchains* tab
 --------------------