first pass at feedback

Author: ejizba

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

@@ -5,7 +5,7 @@ ms.service: azure-functions
 ms.date: 09/20/2023
 ms.devlang: javascript, typescript
 ms.custom: devx-track-js
-ms.topic: how-to
+ms.topic: troubleshooting-general
 zone_pivot_groups: functions-nodejs-model
 ---
 
@@ -15,9 +15,9 @@ zone_pivot_groups: functions-nodejs-model
 
 This article provides a guide for troubleshooting common scenarios in Node.js function apps.
 
-The **Diagnose and solve problems** tab in the Azure portal is a useful resource to monitor and diagnose possible issues related to your application. It also supplies potential solutions to your problems based on the diagnosis. For more information, see [Azure Function app diagnostics](./functions-diagnostics.md). 
+The **Diagnose and solve problems** tab in the [Azure portal](https://portal.azure.com) is a useful resource to monitor and diagnose possible issues related to your application. It also supplies potential solutions to your problems based on the diagnosis. For more information, see [Azure Function app diagnostics](./functions-diagnostics.md). 
 
-Another useful resource is the **Logs** tab in the Azure Portal for your Application Insights instance so that you can run custom [KQL queries](/azure/data-explorer/kusto/query/). The following example query shows how to view errors and warnings for your app in the past day:
+Another useful resource is the **Logs** tab in the [Azure portal](https://portal.azure.com) for your Application Insights instance so that you can run custom [KQL queries](/azure/data-explorer/kusto/query/). The following example query shows how to view errors and warnings for your app in the past day:
 
 ```kusto
 let myAppName = "<your app name>";
@@ -31,7 +31,7 @@ union traces,requests,exceptions
 
 If those resources didn't solve your problem, the following sections provide advice for specific application issues:
 
-## No Functions Found
+## No functions found
 
 If you see this error in your deployment logs:
 
@@ -44,11 +44,10 @@ Or this error in your function app logs:
 Try the following fixes:
 
 ::: zone pivot="nodejs-model-v4"
-- If you're running locally:
-    - Make sure you're on Azure Functions Core Tools v4.0.5382 or higher.
-- If you're running in Azure:
-    - Make sure you're on [Azure Functions Runtime Version](./functions-versions.md) 4.25 or higher.
-    - Make sure you're on Node.js v18 or higher.
+- When running locally, make sure you're using Azure Functions Core Tools v4.0.5382 or higher.
+- 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:
 
         ```kusto
@@ -75,21 +74,25 @@ If you get the following error in your function app logs:
 > System.Private.CoreLib: Exception while executing function: Functions.httpTrigger1. System.Private.CoreLib: Result: Failure
 > Exception: undici_1.Request is not a constructor
 
-Try the following fixes:
-- Make sure you're on Node.js version 18.x or higher.
+Make sure you're using Node.js version 18.x or higher.
 
 ## Failed to detect the Azure Functions runtime
 
 If you get the following error in your function app logs:
 
 > WARNING: Failed to detect the Azure Functions runtime. Switching "@azure/functions" package to test mode - not all features are supported.
 
-Try the following fixes:
-- Check your `package.json` file for a reference to `applicationinsights` and make sure the version is `^2.7.1` or higher. After updating the version, run `npm install`
+Check your `package.json` file for a reference to `applicationinsights` and make sure the version is `^2.7.1` or higher. After updating the version, run `npm install`
 ::: zone-end
 
-## Next steps
+## Get help from Microsoft
 
-Microsoft support engineers are available to help diagnosing issues with your application. If you're not able to diagnose your problem using this guide, you can file a support ticket by accessing the **Support + troubleshooting** section of your function app page in the Azure portal.
+You can get more help from Microsoft in one of the following ways:
+
+- Search the known issues in the [Azure Functions Node.js repository](https://github.com/Azure/azure-functions-nodejs-library/issues). If you don't see your issue mentioned, create a new issue and let us know what has happened.
+- If you're not able to diagnose your problem using this guide, Microsoft support engineers are available to help diagnose issues with your application. Microsoft offers [various support plans](https://azure.microsoft.com/support/plans). Create a support ticket in the **Support + troubleshooting** section of your function app page in the [Azure portal](https://portal.azure.com).
+
+## Next steps
 
-You can also contact the Azure Functions Node.js team directly [on GitHub](https://github.com/Azure/azure-functions-nodejs-library/issues).
+- [Microsoft Q&A page for Azure Functions](/answers/tags/87/azure-functions)
+- [Azure Functions Node.js developer guide](functions-reference-node.md)