Skip to content

Commit 3021ea3

Browse files
authored
Made H2s more consistent
1 parent 82ce9bf commit 3021ea3

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-functions/extension-bundles.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Extension bundles add a predefined set of compatible binding extensions to your
1919

2020
When you create an Azure Functions project from a non-.NET template, extension bundles are already enabled in the app's `host.json` file.
2121

22-
## Defining an extension bundle reference
22+
## Define an extension bundle reference
2323

2424
You define an extension bundle reference in the `host.json` project file by adding an `extensionBundle` section, as in this example:
2525

@@ -59,7 +59,7 @@ Keep these considerations in mind when upgrading the extension bundle version us
5959
+ Local project: extensions are updated locally when Core Tools starts, either from the `func start` command or when debugging in your development tools.
6060
+ Function app: extensions are updated when you deploy the updated host.json file to your function app in Azure.
6161

62-
## Previewing extension bundles
62+
## Preview extension bundles
6363

6464
Prerelease versions of specific binding extensions are maintained in a preview extension bundle: `Microsoft.Azure.Functions.ExtensionBundle.Preview`. You can use this preview extension bundle to take advantage of preview extensions and new behaviors in existing extensions before they reach general availability (GA).
6565

0 commit comments

Comments
 (0)