more feedback

Author: ejizba

articles/azure-functions/durable/durable-functions-node-model-upgrade.md

@@ -1,5 +1,5 @@
 ---
-title: Upgrade your Durable Functions app to version 4 of the Node.js programming model
+title: Migrate your Durable Functions app to version 4 of the Node.js programming model
 description: This article shows you how to upgrade your existing Durable Functions apps running on v3 of the Node.js programming model to v4.
 author: hossam-nasr
 ms.service: azure-functions
@@ -11,7 +11,7 @@ ms.topic: how-to
 zone_pivot_groups: programming-languages-set-functions-nodejs
 ---
 
-# Upgrade your Durable Functions app to version 4 of the Node.js programming model
+# Migrate your Durable Functions app to version 4 of the Node.js programming model
 
 This article provides a guide to upgrade your existing Durable Functions app to version 4 of the Node.js programming model. Note that this article uses "TIP" banners to summarize the key steps needed to upgrade your app.
 

articles/azure-functions/functions-node-troubleshoot.md

@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot Node.js apps in Azure Functions
-description: Learn how to troubleshoot Node.js apps in Azure Functions.
+description: Learn how to troubleshoot common errors when you deploy or run a Node.js app in Azure Functions.
 ms.service: azure-functions
 ms.date: 09/20/2023
 ms.devlang: javascript, typescript
@@ -33,12 +33,10 @@ If those resources didn't solve your problem, the following sections provide adv
 
 ## No functions found
 
-If you see this error in your deployment logs:
+If you see any of the following errors in your logs:
 
 > No HTTP triggers found.
 
-Or this error in your function app logs:
-
 > No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. Azure Storage, ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. builder.AddAzureStorage(), builder.AddServiceBus(), builder.AddTimers(), etc.).
 
 Try the following fixes:
@@ -48,7 +46,8 @@ Try the following fixes:
 - When running in Azure:
     - Make sure you're using [Azure Functions Runtime Version](./functions-versions.md) 4.25 or higher.
     - Make sure you're using Node.js v18 or higher.
-    - Check your function app logs for entry point errors. First, set the app setting `FUNCTIONS_NODE_BLOCK_ON_ENTRY_POINT_ERROR` to `1` to ensure all errors are tracked in yours logs. The following example query shows how to view entry point errors for your app in the past day:
+    - Set the app setting `FUNCTIONS_NODE_BLOCK_ON_ENTRY_POINT_ERROR` to `1`. This setting is recommended for all model v4 apps and ensures that all entry point errors are visible in your application insights logs.
+    - Check your function app logs for entry point errors. The following example query shows how to view entry point errors for your app in the past day:
 
         ```kusto
         let myAppName = "<your app name>";

articles/azure-functions/functions-reference-node.md

@@ -14,7 +14,7 @@ zone_pivot_groups: functions-nodejs-model
 This guide is an introduction to developing Azure Functions using JavaScript or TypeScript. The article assumes that you have already read the [Azure Functions developer guide](functions-reference.md).
 
 > [!IMPORTANT]
-> The content of this article changes based on your choice of the Node.js programming model in the selector at the top of this page. The version you choose should match the version of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package you are using in your app. If you do not have that package listed in your `package.json`, the default is v3. Learn more about the differences between v3 and v4 in the [upgrade guide](./functions-node-upgrade-v4.md).
+> The content of this article changes based on your choice of the Node.js programming model in the selector at the top of this page. The version you choose should match the version of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package you are using in your app. If you do not have that package listed in your `package.json`, the default is v3. Learn more about the differences between v3 and v4 in the [migration guide](./functions-node-upgrade-v4.md).
 
 As a Node.js developer, you might also be interested in one of the following articles:
 

includes/functions-nodejs-durable-model-description.md

@@ -10,6 +10,6 @@ ms.custom: include file
 ---
 
 > [!NOTE]
-> Version 4 of the Node.js programming model for Azure Functions is generally available. The new v4 model is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. Learn more about the differences between v3 and v4 in the [upgrade guide](../articles/azure-functions/functions-node-upgrade-v4.md).
+> Version 4 of the Node.js programming model for Azure Functions is generally available. The new v4 model is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. Learn more about the differences between v3 and v4 in the [migration guide](../articles/azure-functions/functions-node-upgrade-v4.md).
 >
 > In the following code snippets, JavaScript (PM4) denotes programming model V4, the new experience.

includes/functions-nodejs-model-pivot-description.md

@@ -10,4 +10,4 @@ ms.custom: include file
 ---
 
 > [!IMPORTANT]
-> The content of this article changes based on your choice of the Node.js programming model in the selector at the top of the page. The v4 model is generally available and is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. Learn more about the differences between v3 and v4 in the [upgrade guide](../articles/azure-functions/functions-node-upgrade-v4.md).
+> The content of this article changes based on your choice of the Node.js programming model in the selector at the top of the page. The v4 model is generally available and is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. Learn more about the differences between v3 and v4 in the [migration guide](../articles/azure-functions/functions-node-upgrade-v4.md).

includes/functions-nodejs-model-tabs-description.md

@@ -10,4 +10,4 @@ ms.custom: include file
 ---
 
 > [!IMPORTANT]
-> This article uses tabs to support multiple versions of the Node.js programming model. The v4 model is generally available and is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. Learn more about the differences between v3 and v4 in the [upgrade guide](../articles/azure-functions/functions-node-upgrade-v4.md).
+> This article uses tabs to support multiple versions of the Node.js programming model. The v4 model is generally available and is designed to have a more flexible and intuitive experience for JavaScript and TypeScript developers. Learn more about the differences between v3 and v4 in the [migration guide](../articles/azure-functions/functions-node-upgrade-v4.md).