Additional openexec 26.03 release notes changes.

(Internal change: 2396792)

Author: pixar-oss

CHANGELOG.md

@@ -512,17 +512,17 @@
   space, and produces a posed space.
 
 - Cycle detection/handling improvements:
-  - Changes made to detect data cycles formed over multiple rounds of 
-    compilation.  
-  - When compilation detects an attempt to create a cycle in the network, a 
-    `TF_ERROR` is emitted with an error code value of 
-    `ExecValidationErrorType::DataDependencyCycle`, and control is returned to 
-    the client instead of aborting the process. Computations that depend on data 
-    cycles may evaluate to incorrect values. To programmatically determine if 
-    compilation detected a cycle, use a `TfErrorMark`.
-  - If an `ExecUsdRequest` contains value keys that depend on a data cycle, 
-    those value keys will be invalidated by the 
-    `ExecRequestComputedValueInvalidationCallback` for every scene change until 
+  - Changes made to detect data cycles formed by *multiple* rounds of 
+    compilation.
+  - When compilation detects an attempt to create a cycle in the network, a
+    `TF_ERROR` is now emitted with an error code value of
+    `ExecValidationErrorType::DataDependencyCycle`, and control is now returned 
+    to the client instead of aborting the process. Computations that depend on 
+    data cycles may evaluate to incorrect values. To programmatically determine 
+    if compilation detected a cycle, use a `TfErrorMark`.
+  - If an `ExecUsdRequest` contains value keys that depend on a data cycle,
+    those value keys will now be invalidated by the
+    `ExecRequestComputedValueInvalidationCallback` for every scene change until
     the cycle has been resolved.
 
 ### usdchecker