clean up includes

Author: ejizba

includes/functions-nodejs-model-considerations.md

@@ -12,9 +12,9 @@ ms.custom: include file
 ## Considerations
 
 - The Node.js "programming model" should not be confused with the Azure Functions "runtime".
-    - _**Programming model**_: The part of Azure Functions specific to JavaScript and TypeScript that governs how you author your code. For example it determines how you register a function, get a function's input, or interact with the invocation context.
+    - _**Programming model**_: The part of Azure Functions specific to JavaScript and TypeScript that governs how you author your code.
     - _**Runtime**_: The central part of Azure Functions that governs underlying behavior shared across all languages.
-- The Node.js programming model is versioned independently of the Azure Functions [runtime](./functions-versions.md). The programming model version is strictly tied to the version of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package. Both the runtime and the programming model use "4" as their latest major version, but that is purely a coincidence. 
+- The programming model version is strictly tied to the version of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package, and is versioned independently of the [runtime](../articles/azure-functions/functions-versions.md). Both the runtime and the programming model use "4" as their latest major version, but that is purely a coincidence. 
 - Keep in mind that you can't mix the v3 and v4 programming models in the same function app. As soon as you register one v4 function in your app, any v3 functions registered in `function.json` files will be ignored.
 
 > [!NOTE]