one-to-many ports relation

Exercise-Configuration.md

@@ -208,12 +208,12 @@ Pipelines are sent to clients in JSON format and are stored in API in correspond
 Important features:
 
 * Every port either have to have defined reference to variable or it has to be blank. Actual value (for example string) is not allowed in port. If variable name is declared in port it has to exist in variables table.
-* Connection between ports have to always be one end to another end. It is not possible to have one output port which redirects variables to two input ports. Of course there has to be exception, it is allowed to have variable which is used only in input port, value of this variable has to be defined in pipeline variables table.
+* Connection between ports can be one-to-one or one-to-many from the perspective of output port. That means it is possible to have one output port which redirects variables to two or more input ports. Of course there has to be exception, it is allowed to have variable which is used only in input port, value of this variable has to be defined in pipeline variables table.
 
 ### Boxes
 
 * DataInBox and DataOutBox are special boxes which are treated differently from the others. This means that their deletion or even some breaking changes may have unforseen consequences. They are used for importing and exporting stuff out from pipeline. These inputs or outputs may have been connected to another pipeline or to supervisor/student inputs.
-* Every (except data boxes) box is used only in BoxService for creation purposes and then through abstract Box interface which is of course using inheritance for providing general usage schema. Thanks to this creation of new boxes is quite simple and straightforward.
+* Every (except data boxes) box is used only in BoxService for creation purposes and then through abstract Box interface which is of course using inheritance for providing general usage schema. Thanks to this, creation of new boxes is quite simple and straightforward.
 
 ### Configuration