Fix the add binding table

Author: ggailey777

Diff for: articles/azure-functions/add-bindings-existing-function.md

@@ -4,6 +4,7 @@ description: Learn how to add bindings that connect to other Azure services to a
 ms.topic: how-to
 ms.date: 04/29/2020
 ms.custom: vscode-azure-extension-update-not-needed
+zone_pivot_groups: programming-languages-set-functions-lang-workers    
 #Customer intent: As a developer, I need to know how to add a binding to an existing function so that I can integrate external services to my function.
 ---
 

Diff for: articles/azure-functions/create-first-function-cli-python.md

@@ -87,7 +87,7 @@ py -m venv .venv
 
 You run all subsequent commands in this activated virtual environment.
 
-## Create a local function project
+## Create a local function
 
 In Azure Functions, a function project is a container for one or more individual functions that each responds to a specific trigger. All functions in a project share the same local and hosting configurations. 
 ::: zone pivot="python-mode-configuration"  
@@ -116,7 +116,7 @@ In this section, you create a function project that contains a single function.
     `func new` creates a subfolder matching the function name that contains a code file appropriate to the project's chosen language and a configuration file named *function.json*.    
 ::: zone-end  
 ::: zone pivot="python-mode-decorators"  
-In this section, you create a function project.
+In this section, you create a function project and add an HTTP triggered function.
 
 1. Run the `func init` command as follows to create a functions project in a folder named *LocalFunctionProj* with the specified runtime and the specified programming model version.
 
@@ -132,7 +132,7 @@ In this section, you create a function project.
     
     This folder contains various files for the project, including configuration files named [*local.settings.json*](functions-develop-local.md#local-settings-file) and [*host.json*](functions-host-json.md). Because *local.settings.json* can contain secrets downloaded from Azure, the file is excluded from source control by default in the *.gitignore* file.
 
-1. The file `function_app.py` can include all functions within your project. Open this file and replace the existing contents with the following code that also defines an HTTP triggered function named HttpExample:  
+1. The file `function_app.py` can include all functions within your project. Open this file and replace the existing contents with the following code that adds an HTTP triggered function named `HttpExample`:  
 
    ```python
    import azure.functions as func

Diff for: articles/azure-functions/functions-core-tools-reference.md

@@ -44,6 +44,7 @@ When you supply `<PROJECT_FOLDER>`, the project is created in a new folder with
 | **`--force`** | Initialize the project even when there are existing files in the project. This setting overwrites existing files with the same name. Other files in the project folder aren't affected. |
 | **`--language`** | Initializes a language-specific project. Currently supported when `--worker-runtime` set to `node`. Options are `typescript` and `javascript`. You can also use `--worker-runtime javascript` or `--worker-runtime typescript`.  |
 | **`--managed-dependencies`**  | Installs managed dependencies. Currently, only the PowerShell worker runtime supports this functionality. |
+| **`--model`** | Sets the desired programming model for a target language when more than one model is available. Supported options are `V1` and `V2` for Python and `V3` and `V4` for Node.js. For more information, see the [Python developer guide](functions-reference-python.md#programming-model) and the [Node.js developer guide](functions-reference-node.md), respectively. |
 | **`--source-control`** | Controls whether a git repository is created. By default, a repository isn't created. When `true`, a repository is created. |
 | **`--worker-runtime`** | Sets the language runtime for the project. Supported values are: `csharp`, `dotnet`, `dotnet-isolated`, `javascript`,`node` (JavaScript), `powershell`, `python`, and `typescript`. For Java, use [Maven](functions-reference-java.md#create-java-functions). To generate a language-agnostic project with just the project files, use `custom`. When not set, you're prompted to choose your runtime during initialization. |
 | **`--target-framework`** | Sets the target framework for the function app project. Valid only with `--worker-runtime dotnet-isolated`. Supported values are: `net6.0` (default), `net7.0`, and `net48`. |
@@ -472,11 +473,16 @@ To learn more, see the [Durable Functions documentation](./durable/durable-funct
 
 ## func extensions install
 
-Installs Functions extensions in a non-C# class library project. 
+Manually installs Functions extensions in a non-.NET project or in a C# script project. 
 
-When possible, you should instead use extension bundles. To learn more, see [Extension bundles](functions-bindings-register.md#extension-bundles).
+> [!TIP] 
+> When possible, you should instead use extension bundles. To learn more, see [Extension bundles](functions-bindings-register.md#extension-bundles).
 
-For compiled C# projects (both in-process and isolated worker process), instead use standard NuGet package installation methods, such as `dotnet add package`.
+The following are some reasons why you might need to install extensions manually:
+
+* You need to access a specific version of an extension not available in a bundle.
+* You need to access a custom extension not available in a bundle.
+* You need to access a specific combination of extensions not available in a single bundle.
 
 The `install` action supports the following options:
 
@@ -490,7 +496,15 @@ The `install` action supports the following options:
 | **`--source`** |  NuGet feed source when not using NuGet.org.|
 | **`--version`** |  Extension package version. |
 
-No action is taken when an extension bundle is defined in your host.json file. When you need to manually install extensions, you must first remove the bundle definition. For more information, see [Install extensions](functions-run-local.md#install-extensions).
+The following considerations apply when using `func extensions install`:
+
++ For compiled C# projects (both in-process and isolated worker process), instead use standard NuGet package installation methods, such as `dotnet add package`.
+
++ To manually install extensions using Core Tools, you must have the [.NET 6.0 SDK](https://dotnet.microsoft.com/download) installed.
+
++ Before you can manually install extensions, you must first remove the [`extensionBundle`](functions-host-json.md#extensionbundle) object from the host.json file that defines the bundle. No action is taken when an extension bundle is already set in your [host.json file](functions-host-json.md#extensionbundle).
+
++ The first time you explicitly install an extension, a .NET project file named extensions.csproj is added to the root of your app project. This file defines the set of NuGet packages required by your functions. While you can work with the [NuGet package references](/nuget/consume-packages/package-references-in-project-files) in this file, Core Tools lets you install extensions without having to manually edit this C# project file.
 
 ## func extensions sync