Merge pull request #280491 from ealsur/users/ealsur/funcdoc

Cosmos DB Functions migration: Adding JsonNode mention

Author: prmerger-automator[bot]

articles/azure-functions/migrate-cosmos-db-version-3-version-4.md

@@ -4,7 +4,7 @@ description: This article shows you how to upgrade your existing function apps u
 ms.service: azure-functions
 ms.custom: devx-track-extended-java, devx-track-js, devx-track-python
 ms.topic: how-to 
-ms.date: 05/07/2024
+ms.date: 07/10/2024
 zone_pivot_groups: programming-languages-set-functions-lang-workers
 ---
 
@@ -210,7 +210,7 @@ namespace CosmosDBSamples
 ```
 
 > [!NOTE]
-> If your scenario relied on the dynamic nature of the `Document` type to identify different schemas and types of events, you can use a base abstract type with the common properties across your types or dynamic types like `JObject` that allow to access properties like `Document` did.
+> If your scenario relied on the dynamic nature of the `Document` type to identify different schemas and types of events, you can use a base abstract type with the common properties across your types or dynamic types like `JObject` (when using `Microsoft.Azure.WebJobs.Extensions.CosmosDB`) and `JsonNode` (when using `Microsoft.Azure.Functions.Worker.Extensions.CosmosDB`) that allow to access properties like `Document` did.
 
 Additionally, if you are using the Output Binding, please review the [change in item ID generation](#changes-to-item-id-generation) to verify if you need additional code changes.