-// flow (e.g. gigits, made from them RecPoints, made from them TrackSegments, made from
-// them RecParticles) are distinguished by the title of created branches. One can
-// use this title as a comment, see user case below. Thanks to getters, one can set
-// parameters to reconstruction bricks. The full set of parameters is saved in the
-// correspoinding branch: e.g. parameters of clusterizer are stored in branch
-// TreeR::AliPHOSClusterizer with the same title as the branch contaning RecPoints
-// themself. TTree does not support overwriting, therefore one can not produce several
+// flow (e.g. digits, made from them RecPoints, subsequently made TrackSegments,
+// subsequently made RecParticles) are distinguished by the title of created branches. One can
+// use this title as a comment, see use case below.
+// Thanks to getters, one can set
+// parameters to reconstruction briks. The full set of parameters is saved in the
+// corresponding branch: e.g. parameters of clusterizer are stored in branch
+// TreeR::AliPHOSClusterizer with the same title as the branch containing the RecPoints.
+// TTree does not support overwriting, therefore one can not produce several