Skip to content

Commit 7a91609

Browse files
update
1 parent 2bb5194 commit 7a91609

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed
39.2 KB
Loading

articles/azure-app-configuration/quickstart-feature-flag-javascript.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: quickstart
99
ms.date: 09/26/2024
1010
ms.author: zhiyuanliang
1111
ms.custom: quickstart, mode-other, devx-track-js
12-
#Customer intent: As an JavaScript developer, I want to use feature flags to control feature availability quickly and confidently.
12+
#Customer intent: As a JavaScript developer, I want to use feature flags to control feature availability quickly and confidently.
1313
---
1414

1515
# Quickstart: Add feature flags to a Node.js app
@@ -29,7 +29,7 @@ The example used in this tutorial is based on the Node.js application introduced
2929
Add a feature flag called *Beta* to the App Configuration store and leave **Label** and **Description** with their default values. For more information about how to add feature flags to a store using the Azure portal or the CLI, go to [Create a feature flag](./manage-feature-flags.md#create-a-feature-flag).
3030

3131
> [!div class="mx-imgBorder"]
32-
> ![Enable feature flag named Beta](media/add-beta-feature-flag.png)
32+
> ![Enable feature flag named Beta](media/quickstart-feature-flag-javascript/add-beta-feature-flag.png)
3333
3434
## Use the feature flag
3535

@@ -87,7 +87,7 @@ Add a feature flag called *Beta* to the App Configuration store and leave **Labe
8787
node app.js
8888
```
8989

90-
1. You will see the following console outputs because the *Beta feature flag is disabled.
90+
1. You will see the following console outputs because the *Beta* feature flag is disabled.
9191

9292
``` console
9393
Beta is enabled: false

0 commit comments

Comments
 (0)