docs: clarify content of desired resources in composition functions (#…

…506)
crossplane · Jul 28, 2023 · 872d68e · 872d68e
1 parent 5372be9
commit 872d68e
Showing 1 changed file with 9 additions and 2 deletions.
diff --git a/content/master/concepts/composition-functions.md b/content/master/concepts/composition-functions.md
@@ -348,11 +348,18 @@ The `desired` state of the XR and composed resources is how your Function tells
 Crossplane what it should do. Crossplane 'bootstraps' the initial desired state
 passed to a Function pipeline with:
 
-* A copy of the observed state of the XR.
-* A copy of the observed state of any existing composed resources.
+* A copy of the observed state of the composite resource (XR).
+* A copy of the observed state of any existing composed resources produced
+  from the `resources` array.
 * Any new composed resources or modifications to observed resources produced
   from the `resources` array.
 
+{{< hint "note" >}}
+The initial desired state doesn't include any copies of observed resources
+produced by the function pipeline. When using multiple functions each function
+passes their desired resources output as input to the next pipeline function.
+{{< /hint >}}
+
 When adding a new desired resource to the `desired.resources` array you don't
 need to: