Skip to content

Commit 63f629c

Browse files
committed
acrolinx and nits
1 parent 6809c98 commit 63f629c

File tree

1 file changed

+12
-13
lines changed

1 file changed

+12
-13
lines changed

articles/app-service/tutorial-nodejs-mongodb-app.md

Lines changed: 12 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -274,7 +274,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
274274

275275
## 4. Deploy sample code
276276

277-
In this step, you'll configure GitHub deployment using GitHub Actions. It's just one of many ways to deploy to App Service, but also a great way to have continuous integration in your deployment process. By default, every `git push` to your GitHub repository will kick off the build and deploy action.
277+
In this step, you configure GitHub deployment using GitHub Actions. It's just one of many ways to deploy to App Service, but also a great way to have continuous integration in your deployment process. By default, every `git push` to your GitHub repository kicks off the build and deploy action.
278278

279279
:::row:::
280280
:::column span="2":::
@@ -366,7 +366,7 @@ In this step, you'll configure GitHub deployment using GitHub Actions. It's just
366366

367367
Having issues? Check the [Troubleshooting section](#troubleshooting).
368368

369-
## 4. Browse to the app
369+
## 5. Browse to the app
370370

371371
:::row:::
372372
:::column span="2":::
@@ -388,7 +388,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
388388
:::column-end:::
389389
:::row-end:::
390390

391-
## 5. Stream diagnostic logs
391+
## 6. Stream diagnostic logs
392392

393393
Azure App Service captures all messages logged to the console to assist you in diagnosing issues with your application. The sample app outputs console log messages in each of its endpoints to demonstrate this capability. For example, the `get` endpoint outputs a message about the number of tasks retrieved from the database and an error message appears if something goes wrong.
394394

@@ -414,7 +414,7 @@ Azure App Service captures all messages logged to the console to assist you in d
414414
:::column-end:::
415415
:::row-end:::
416416

417-
## 6. Inspect deployed files using Kudu
417+
## 7. Inspect deployed files using Kudu
418418

419419
Azure App Service provides a web-based diagnostics console named [Kudu](./resources-kudu.md) that lets you examine the server hosting environment for your web app. Using Kudu, you can view the files deployed to Azure, review the deployment history of the application, and even open an SSH session into the hosting environment.
420420

@@ -438,7 +438,7 @@ Azure App Service provides a web-based diagnostics console named [Kudu](./resour
438438
:::row-end:::
439439
:::row:::
440440
:::column span="2":::
441-
If you have deployed code to App Service using Git or zip deploy, you'll see a history of deployments of your web app.
441+
If you deploy code to App Service using Git or zip deploy, you see a history of deployments of your web app.
442442
:::column-end:::
443443
:::column:::
444444
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-3.png" alt-text="A screenshot showing deployment history of an App Service app in JSON format." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-3.png":::
@@ -454,14 +454,14 @@ Azure App Service provides a web-based diagnostics console named [Kudu](./resour
454454
:::row-end:::
455455
:::row:::
456456
:::column span="2":::
457-
You can see the deployed folder structure and click to browse and view the files.
457+
You can see the deployed folder structure and select to browse and view the files.
458458
:::column-end:::
459459
:::column:::
460460
:::image type="content" source="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-5.png" alt-text="A screenshot of deployed files in the wwwroot directory." lightbox="./media/tutorial-nodejs-mongodb-app/azure-portal-inspect-kudu-5.png":::
461461
:::column-end:::
462462
:::row-end:::
463463

464-
## 7. Clean up resources
464+
## 8. Clean up resources
465465

466466
When you're finished, you can delete all of the resources from your Azure subscription by deleting the resource group.
467467

@@ -567,14 +567,13 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
567567
568568
## 4. Modify sample code and redeploy
569569
570-
571570
# [With GitHub Copilot](#tab/copilot)
572571
573572
1. In the GitHub codespace, start a new chat session by clicking the **Chat** view, then clicking **+**.
574573
575574
1. Ask, "*@workspace How does the app connect to the database?*" Copilot might point you to the *app.js* file and the `mongoose.connect` call.
576575
577-
1. Say, "*I have a connection string variable in Azure called AZURE_COSMOS_CONNECTIONSTRING.". Copilot might give you a code suggestion similar to the one in the **Option 2: without GitHub Copilot** steps below and even tell you to make the change in [app.js](https://github.com/Azure-Samples/msdocs-nodejs-mongodb-azure-sample-app/blob/main/app.js).
576+
1. Say, "*I have a connection string variable in Azure called AZURE_COSMOS_CONNECTIONSTRING.*". Copilot might give you a code suggestion similar to the one in the **Option 2: without GitHub Copilot** steps below and even tell you to make the change in [app.js](https://github.com/Azure-Samples/msdocs-nodejs-mongodb-azure-sample-app/blob/main/app.js).
578577
579578
1. Open *app.js* in the explorer and add the code suggestion in the `getApp` method.
580579
@@ -607,7 +606,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
607606
608607
Having issues? Check the [Troubleshooting section](#troubleshooting).
609608
610-
## 4. Browse to the app
609+
## 5. Browse to the app
611610
612611
1. In the AZD output, find the URL of your app and navigate to it in the browser. The URL looks like this in the AZD output:
613612
@@ -626,7 +625,7 @@ Having issues? Check the [Troubleshooting section](#troubleshooting).
626625

627626
Having issues? Check the [Troubleshooting section](#troubleshooting).
628627

629-
## 5. Stream diagnostic logs
628+
## 6. Stream diagnostic logs
630629

631630
Azure App Service captures all messages logged to the console to assist you in diagnosing issues with your application. The sample app outputs console log messages in each of its endpoints to demonstrate this capability. For example, the `get` endpoint outputs a message about the number of tasks retrieved from the database and an error message appears if something goes wrong.
632631

@@ -642,7 +641,7 @@ Learn more about logging in Java apps in the series on [Enable Azure Monitor Ope
642641

643642
Having issues? Check the [Troubleshooting section](#troubleshooting).
644643

645-
## 6. Clean up resources
644+
## 7. Clean up resources
646645

647646
To delete all Azure resources in the current deployment environment, run `azd down` and follow the prompts.
648647

@@ -680,7 +679,7 @@ You probably still need to make the connection string changes in your applicatio
680679

681680
#### How much does this setup cost?
682681

683-
Pricing for the create resources is as follows:
682+
Pricing for the created resources is as follows:
684683

685684
- The App Service plan is created in **Basic** tier and can be scaled up or down. See [App Service pricing](https://azure.microsoft.com/pricing/details/app-service/linux/).
686685
- The Azure Cosmos DB server is created in a single region and can be distributed to other regions. See [Azure Cosmos DB pricing](https://azure.microsoft.com/pricing/details/cosmos-db/).

0 commit comments

Comments
 (0)