[DOCS] Updates description and example response.

Author: szabosteve

docs/reference/transform/apis/upgrade-transforms.asciidoc

@@ -34,15 +34,17 @@ configuration format and upgrades them to the latest version; including clean up
 of the internal data structures that store {transform} state and checkpoints. 
 {transform-cap} upgrade does not effect the source and destination indices.
 
-It is recommended to have a recent cluster backup prior to performing a 
-{transform} upgrade which can be run either before or after an {es} upgrade. 
-However, it is recommended to perform it prior to upgrading {es} to the next 
-major version to ensure {ctransforms} remain started.
-
 If a {transform} upgrade step fails, the upgrade stops, and an error is returned 
 about the underlying issue. Resolve the issue then re-run the process again. A 
 summary is returned when the upgrade is finished.
 
+For a major version update – for example, from 7.16 to 8.0 –, it is recommended 
+to have a recent cluster backup prior to performing a {transform} upgrade which 
+can be run either before or after an {es} upgrade. However, it is recommended to 
+perform it before upgrading {es} to the next major version to ensure 
+{ctransforms} remain running.
+
+
 [IMPORTANT]
 ====
 
@@ -80,6 +82,7 @@ When all {transforms} are upgraded, you receive a summary:
 [source,console-result]
 ----
 {
+  "updated": 2
   "no_action": 1
 }
 ----