Skip to content

Commit 1bde96f

Browse files
committed
acrolynx fixes
1 parent 2e5bbaa commit 1bde96f

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/app-service/containers/tutorial-javascript-vscode-containerize-app.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,25 +38,25 @@ Open the **Command Palette** (CTRL + SHIFT + P) and run **Docker: Build Image**
3838

3939
`[registry or username]/[image name]:[tag]`
4040

41-
This quickstart uses the Azure Container Registry so for my example:
41+
Here's an example, using the Azure Container Registry:
4242

4343
`fiveisprime.azurecr.io/myexpressapp:latest`
4444

4545
![tag docker image](./media/tutorial-javascript-vscode/tag-image.png)
4646

47-
If you're using Docker Hub, use your Docker Hub username, for example:
47+
If you're using Docker Hub, use your Docker Hub username. For example:
4848

4949
`fiveisprime/myexpressapp:latest`
5050

51-
Once completed, the Terminal panel will open and the Docker command will be executed. This is a good way to get an understanding of the commands required to do the same steps directly from the terminal. You'll also see each step, or layer, that makes up the app environment.
51+
When the build finishes, the **Terminal** panel will open and the Docker command will run. Viewing the terminal is a good way to get an understanding of the commands required to do the same steps when you use the terminal directly. You'll also see each step, or layer, that makes up the app environment.
5252

5353
Once built, the image will show up in the **DOCKER** explorer under **Images**.
5454

5555
![Docker Image](./media/tutorial-javascript-vscode/image-list.png)
5656

5757
## Push the image to a registry
5858

59-
Open the **Command Palette** (CTRL + SHIFT + P) and run **Docker: Push** and choose the image you just built to push the image to the registry. This will also execute the Docker command in the Terminal panel to show the status of the operation. Once completed, expand the **Images** node in the Docker extension explorer to see your image.
59+
Open the **Command Palette** (CTRL + SHIFT + P), run **Docker: Push**, and choose the image you built to push the image to the registry. This command will also execute the Docker command in the Terminal panel to show the status of the operation. When the command finishes, expand the **Images** node in the Docker extension explorer to see your image.
6060

6161
![Image in ACR](./media/tutorial-javascript-vscode/image-in-acr.png)
6262

articles/app-service/tutorial-javascript-vscode-deploy-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ In the **AZURE APP SERVICE** explorer, click the blue up arrow icon to deploy yo
3737

3838
![Configured deployment](./media/tutorial-javascript-vscode/server-build.png)
3939

40-
Once the deployment starts, you're prompted to update your workspace so that all subsequent deploys automatically target the same App Service Web App. Choose **Yes** to ensure your changes are deployed to the correct app.
40+
When the deployment starts, you're prompted to update your workspace so that later deployments will automatically target the same App Service Web App. Choose **Yes** to ensure your changes are deployed to the correct app.
4141

4242
![Configured deployment](./media/tutorial-javascript-vscode/save-configuration.png)
4343

@@ -50,7 +50,7 @@ Once the deployment completes, click **Browse Website** in the prompt to view yo
5050

5151
## Troubleshooting
5252

53-
Are you seeing the error **"You do not have permission to view this directory or page."**? If so, the application probably failed to start correctly. Head to the next step and view the log output to find and fix the error. If you aren't able to fix it, contact us by clicking the **I ran into an issue** button below. We're happy to help!
53+
If you see the error **"You do not have permission to view this directory or page."**, then the application probably failed to start correctly. Head to the next step and view the log output to find and fix the error. If you aren't able to fix it, contact us by clicking the **I ran into an issue** button below. We're happy to help!
5454

5555
## Updating the website
5656

0 commit comments

Comments
 (0)