update PR

Author: spagarwa

articles/data-factory/control-flow-expression-language-functions.md

@@ -57,13 +57,14 @@ Expressions can appear anywhere in a JSON string value and always result in anot
 |"Answer is: @{pipeline().parameters.myNumber}"| Returns the string `Answer is: 42`.|  
 |"\@concat('Answer is: ', string(pipeline().parameters.myNumber))"| Returns the string `Answer is: 42`|  
 |"Answer is: \@\@{pipeline().parameters.myNumber}"| Returns the string `Answer is: @{pipeline().parameters.myNumber}`.|  
-
-> [!NOTE]
-> A complex example of how the parameters can be used is this, here to be able to use pipeline parameters in dot operator, '[]' is required.
-  @activity('{activityName}').output.{Param1}.{Param2}[pipeline().parameters.Param3].{Param4}
 
 ## Examples
 
+### Complex expression example
+The below example shows a complex example that references a deep sub-field of activity output. To reference a pipeline parameter that evaluates to a sub-field, use [] syntax instead of dot(.) operator (as in case of subfield1 and subfield2)
+
+@activity('{activityName}').output.{subfield1}.{subfield2}[pipeline().parameters.subfield3].{subfield4}
+
 ### A dataset with a parameter
 In the following example, the BlobDataset takes a parameter named **path**. Its value is used to set a value for the **folderPath** property by using the expression: `dataset().path`.