v4.x -> v4

ejizba · ejizba · commit 645a2557e661 · 2023-03-17T19:05:45.000-07:00
also wow warning is a loud color. let's do note
diff --git a/articles/azure-functions/functions-node-upgrade-v4.md b/articles/azure-functions/functions-node-upgrade-v4.md
@@ -1,30 +1,30 @@
 ---
-title: Upgrade to Azure Functions Node.js programming model v4.x
-description: This article shows you how to upgrade your existing function apps running on version 3.x of the Node.js programming model to version 4.x.
+title: Upgrade to Azure Functions Node.js programming model v4
+description: This article shows you how to upgrade your existing function apps running on v3 of the Node.js programming model to v4.
 ms.service: azure-functions
 ms.date: 03/15/2023
 ms.devlang: javascript, typescript
 ms.topic: how-to
 ---
 
-# Upgrade to Azure Functions Node.js programming model v4.x
+# Upgrade to Azure Functions Node.js programming model v4
 
-The Node.js programming model for Azure Functions defines how you author serverless code in JavaScript or TypeScript. The version of the programming model matches the version of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package that should be included with your app. This article discusses the differences between both versions and how to upgrade an existing v3.x app. If you want to create a brand new v4.x app, see the tutorial for either [VS Code](./create-first-function-cli-node.md) or [Azure Functions Core Tools](./create-first-function-vs-code-node.md).
+The Node.js programming model for Azure Functions defines how you author serverless code in JavaScript or TypeScript. The version of the programming model matches the version of the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package that should be included with your app. This article discusses the differences between both versions and how to upgrade an existing v3 app. If you want to create a brand new v4 app, see the tutorial for either [VS Code](./create-first-function-cli-node.md) or [Azure Functions Core Tools](./create-first-function-vs-code-node.md).
 
 > [!NOTE]
-> v4.x of the Node.js programming model is currently in public preview. This version number is _not_ the same thing as the Azure Functions [runtime version](./functions-versions.md), which is coincidentally using "4" as its latest major version. Lastly, you can't mix v3.x and v4.x of the programming models.
+> v4 of the Node.js programming model is currently in public preview. This version number is _not_ the same thing as the Azure Functions [runtime version](./functions-versions.md), which is coincidentally using "4" as its latest major version. Lastly, you can't mix v3 and v4 of the programming models.
 
 ## Motivation
 
-v4.x was designed with the following goals in mind:
+v4 was designed with the following goals in mind:
 
 - Provide a familiar and intuitive experience to Node.js developers
 - Make the file structure flexible with support for full customization
 - Switch to a code-centric approach for defining function configuration
 
 ## Prerequisites
 
-Before you start upgrading your app, v4.x of the Node.js programming model is only supported with the following minimum versions:
+Before you start upgrading your app, v4 of the Node.js programming model is only supported with the following minimum versions:
 
 - [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package v4.0.0-alpha.8+
 - [Node.js](https://nodejs.org/en/download/releases/) v18+
@@ -34,17 +34,17 @@ Before you start upgrading your app, v4.x of the Node.js programming model is on
 
 ## npm package
 
-For the first time, the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package contains the primary source code that backs the Node.js programming model for Azure Functions. Previously, that code shipped directly in Azure and the npm package only had the TypeScript types. Moving forward both JavaScript and TypeScript users need to include this package in their app. v3.x apps _can_ include the npm package, but it isn't required.
+For the first time, the [`@azure/functions`](https://www.npmjs.com/package/@azure/functions) npm package contains the primary source code that backs the Node.js programming model for Azure Functions. Previously, that code shipped directly in Azure and the npm package only had the TypeScript types. Moving forward both JavaScript and TypeScript users need to include this package in their app. v3 apps _can_ include the npm package, but it isn't required.
 
 > [!TIP]
-> _**Action Item**_: Make sure the `@azure/functions` package is listed in the `dependencies` section (not `devDependencies`) of your `package.json` file. You can install v4.x with the command 
+> _**Action Item**_: Make sure the `@azure/functions` package is listed in the `dependencies` section (not `devDependencies`) of your `package.json` file. You can install v4 with the command 
 > ```
 > npm install @azure/functions@preview
 > ```
 
 ## App entry point
 
-v4.x of the programming model lets you structure your code however you want. The only files you need at the root of your app are `host.json` and `package.json`. Otherwise, you define the file structure by setting the `main` field in your `package.json` file. The `main` field can be set to a single file or multiple files by using a [glob pattern](https://wikipedia.org/wiki/Glob_(programming)). Common values for the `main` field may be:
+v4 of the programming model lets you structure your code however you want. The only files you need at the root of your app are `host.json` and `package.json`. Otherwise, you define the file structure by setting the `main` field in your `package.json` file. The `main` field can be set to a single file or multiple files by using a [glob pattern](https://wikipedia.org/wiki/Glob_(programming)). Common values for the `main` field may be:
 - TypeScript
     - `dist/src/index.js`
     - `dist/src/functions/*.js`
@@ -57,7 +57,7 @@ v4.x of the programming model lets you structure your code however you want. The
 
 ## Order of arguments
 
-The trigger input is now the first argument to your function handler instead of the invocation context. The invocation context, now the second argument, was simplified in v4.x and isn't as required as the trigger input - it can be left off if you aren't using it.
+The trigger input is now the first argument to your function handler instead of the invocation context. The invocation context, now the second argument, was simplified in v4 and isn't as required as the trigger input - it can be left off if you aren't using it.
 
 > [!TIP]
 > _**Action Item**_: Switch the order of your arguments. For example if you are using an http trigger, switch `(context, request)` to either `(request, context)` or just `(request)` if you aren't using the context.
@@ -67,9 +67,9 @@ The trigger input is now the first argument to your function handler instead of
 Say goodbye 👋 to `function.json` files! All of the configuration that you were previously specifying in a `function.json` file is now defined directly in your TypeScript or JavaScript files. In addition, many properties now have a default so that you don't have to specify them every time.
 
 > [!WARNING]
-> You can't mix the v3.x and v4.x programming models. As soon as you register one v4.x function in your app, any v3.x functions registered in `function.json` files will be ignored.
+> You can't mix the v3 and v4 programming models. As soon as you register one v4 function in your app, any v3 functions registered in `function.json` files will be ignored.
 
-# [v4.x](#tab/v4)
+# [v4](#tab/v4)
 
 ```javascript
 const { app } = require("@azure/functions");
@@ -90,7 +90,7 @@ app.http('helloWorld1', {
 
 No `function.json` file! ✨
 
-# [v3.x](#tab/v3)
+# [v3](#tab/v3)
 
 ```javascript
 module.exports = async function (context, req) {
@@ -142,18 +142,18 @@ The `context` object has been simplified to reduce duplication and make it easie
 
 The primary input is also called the "trigger" and is the only required input or output. You must have one and only one trigger.
 
-# [v4.x](#tab/v4)
+# [v4](#tab/v4)
 
-v4.x only supports one way of getting the trigger input, as the first argument.
+v4 only supports one way of getting the trigger input, as the first argument.
 
 ```javascript
 async function helloWorld1(request, context) {
   const onlyOption = request;
 ```
 
-# [v3.x](#tab/v3)
+# [v3](#tab/v3)
 
-v3.x supports several different ways of getting the trigger input.
+v3 supports several different ways of getting the trigger input.
 
 ```javascript
 async function helloWorld1(context, request) {
@@ -169,19 +169,19 @@ async function helloWorld1(context, request) {
 
 ### Setting the primary output
 
-# [v4.x](#tab/v4)
+# [v4](#tab/v4)
 
-v4.x only supports one way of setting the primary output, through the return value.
+v4 only supports one way of setting the primary output, through the return value.
 
 ```javascript
 return { 
   body: `Hello, ${name}!` 
 };
 ```
 
-# [v3.x](#tab/v3)
+# [v3](#tab/v3)
 
-v3.x supports several different ways of setting the primary output.
+v3 supports several different ways of setting the primary output.
 
 ```javascript
 // Option 1
@@ -211,9 +211,9 @@ return {
 
 ### Create a test context
 
-v3.x doesn't support creating an invocation context outside of the Azure Functions runtime, making it difficult to author unit tests. v4.x allows you to create an instance of the invocation context, although the information during tests isn't detailed unless you add it yourself.
+v3 doesn't support creating an invocation context outside of the Azure Functions runtime, making it difficult to author unit tests. v4 allows you to create an instance of the invocation context, although the information during tests isn't detailed unless you add it yourself.
 
-# [v4.x](#tab/v4)
+# [v4](#tab/v4)
 
 ```javascript
 const testInvocationContext = new InvocationContext({
@@ -222,7 +222,7 @@ const testInvocationContext = new InvocationContext({
 });
 ```
 
-# [v3.x](#tab/v3)
+# [v3](#tab/v3)
 
 Not possible 😮
 
@@ -234,7 +234,7 @@ The http request and response types are now a subset of the [fetch standard](htt
 
 ### HttpRequest
 
-# [v4.x](#tab/v4)
+# [v4](#tab/v4)
 - _**Body**_. You can access the body using a method specific to the type you would like to receive:
     ```javascript
     const body = await request.text();
@@ -252,7 +252,7 @@ The http request and response types are now a subset of the [fetch standard](htt
     const name = request.query.get('name');
     ```
 
-# [v3.x](#tab/v3)
+# [v3](#tab/v3)
 - _**Body**_. You can access the body in several ways, but the type returned isn't always consistent:
     ```javascript
     // returns a string, object, or Buffer
@@ -278,7 +278,7 @@ The http request and response types are now a subset of the [fetch standard](htt
 
 ### HttpResponse
 
-# [v4.x](#tab/v4)
+# [v4](#tab/v4)
 - _**Status**_:
     ```javascript
     return { status: 200 };
@@ -299,7 +299,7 @@ The http request and response types are now a subset of the [fetch standard](htt
     };
     ```
 
-# [v3.x](#tab/v3)
+# [v3](#tab/v3)
 - _**Status**_. A status can be set in several different ways:
     ```javascript
     context.res.status(200);
diff --git a/articles/azure-functions/functions-reference-node.md b/articles/azure-functions/functions-reference-node.md
@@ -15,7 +15,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've 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.x. Learn more about the differences between v3.x and the new v4.x programming model in the [upgrade guide](./functions-node-upgrade-v4.md). v4.x is currently in public preview.
+> 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 the new v4 programming model in the [upgrade guide](./functions-node-upgrade-v4.md). v4 is currently in public preview.
 
 As a JavaScript developer, you might also be interested in one of the following articles:
 
@@ -27,7 +27,7 @@ As a JavaScript developer, you might also be interested in one of the following
 
 The "programming model" as discussed in this article loosely represents the Node.js layer of Azure Functions. If you are authoring code in JavaScript or TypeScript, the code patterns you use are governed by the programming model. For example, it defines how you register a function, get a function's input, or interact with the invocation context. 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 _not_ the same thing as the Azure Functions [runtime version](./functions-versions.md), even if the major version numbers are coincidentally similar.
 
-> [!WARNING]
+> [!NOTE]
 > You can only use one major version of the programming model at a time.
 
 ### Supported Versions
@@ -261,12 +261,12 @@ app.http('httpTrigger1', {
 });
 ```
 
-> [!WARNING]
-> You can't mix the v3.x and v4.x programming models. As soon as you register one v4.x function in your app, any v3.x functions registered in `function.json` files will be ignored.
+> [!NOTE]
+> You can't mix the v3 and v4 programming models. As soon as you register one v4 function in your app, any v3 functions registered in `function.json` files will be ignored.
 
 ## Inputs and outputs
 
-Your function is required to have exactly one primary input called the trigger. It may also have secondary inputs, a primary output called the return output, and/or secondary outputs. Inputs and outputs are also referred to as bindings outside the context of the Node.js programming model. Before v4.x of the model, these bindings were configured in `function.json` files.
+Your function is required to have exactly one primary input called the trigger. It may also have secondary inputs, a primary output called the return output, and/or secondary outputs. Inputs and outputs are also referred to as bindings outside the context of the Node.js programming model. Before v4 of the model, these bindings were configured in `function.json` files.
 
 ### Trigger input
 
