You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -135,7 +135,7 @@ With [Azure Developer CLI](/azure/developer/azure-developer-cli/install-azd) ins
135
135
136
136
### Initialize the Azure Developer CLI template and deploy resources
137
137
138
-
From an empty directory, follow these steps to initialize the `azd` template, provision Azure resources, and get started with the code:
138
+
From an empty directory, follow these steps to initialize the `azd` template, create Azure resources, and get started with the code:
139
139
140
140
- Clone the quickstart repository assets from GitHub and initialize the template locally:
141
141
@@ -147,7 +147,7 @@ From an empty directory, follow these steps to initialize the `azd` template, pr
147
147
148
148
- **Environment name**: This value is used as a prefix for all Azure resources created by Azure Developer CLI. The name must be unique across all Azure subscriptions and must be between 3 and 24 characters long. The name can contain numbers and lowercase letters only.
149
149
150
-
- Log in to Azure:
150
+
- Sign in to Azure:
151
151
152
152
```console
153
153
azd auth login
@@ -239,7 +239,7 @@ Sample code is also available on [GitHub](https://github.com/Azure-Samples/Azure
239
239
240
240
The order and locations in which `DefaultAzureCredential` looks for credentials can be found in the [Azure Identity library overview](/javascript/api/overview/azure/identity-readme#defaultazurecredential).
241
241
242
-
For example, your app can authenticate using your Azure CLI sign-in credentials with when developing locally. Your app can then use a [managed identity](../../active-directory/managed-identities-azure-resources/overview.md) once it has been deployed to Azure. No code changes are required for this transition.
242
+
For example, your app can authenticate using your Azure CLI sign-in credentials with when developing locally. Your app can then use a [managed identity](../../active-directory/managed-identities-azure-resources/overview.md) once it's deployed to Azure. No code changes are required for this transition.
The code below retrieves the connection string for the storage account from the environment variable created earlier, and uses the connection string to construct a service client object.
332
+
The following code retrieves the connection string for the storage account from the environment variable created earlier, and uses the connection string to construct a service client object.
333
333
334
334
::: zone pivot="blob-storage-quickstart-scratch"
335
335
@@ -379,7 +379,7 @@ To learn more about uploading blobs, and to explore more code samples, see [Uplo
379
379
380
380
## List the blobs in a container
381
381
382
-
List the blobs in the container. The following code calls the [listBlobsFlat](/javascript/api/@azure/storage-blob/containerclient#listblobsflat-containerlistblobsoptions-) method. In this case, only one blob has been added to the container, so the listing operation returns just that one blob.
382
+
List the blobs in the container. The following code calls the [listBlobsFlat](/javascript/api/@azure/storage-blob/containerclient#listblobsflat-containerlistblobsoptions-) method. In this case, only one blob is in the container, so the listing operation returns just that one blob.
383
383
384
384
::: zone pivot="blob-storage-quickstart-scratch"
385
385
@@ -433,32 +433,32 @@ To learn more about deleting a container, and to explore more code samples, see
433
433
434
434
## Run the code
435
435
436
-
1.From a Visual Studio Code terminal, run the app.
436
+
From a Visual Studio Code terminal, run the app.
437
437
438
-
```console
439
-
node index.js
440
-
```
438
+
```console
439
+
node index.js
440
+
```
441
441
442
-
2. The output of the app is similar to the following example:
442
+
The output of the app is similar to the following example:
Step through the code in your debugger and check your [Azure portal](https://portal.azure.com) throughout the process. Check to see that the container is being created. You can open the blob inside the container and view the contents.
0 commit comments