Skip to content

Commit 646e01a

Browse files
authored
edits per
1 parent 3d43086 commit 646e01a

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docker/tutorials/tutorial-multi-container-app-mysql.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ghogen
55
ms.author: ghogen
66
ms.service: vs-code
77
ms.topic: tutorial
8-
ms.date: 08/28/2024
8+
ms.date: 08/29/2024
99
# Under agreement with Docker Inc. to provide this content. Contact is: nebuk89. Mike Morton has context on MSFT side, but has moved on to another role.
1010

1111
#customer intent: As a developer, I want to create multi-container applications with MySQL and Docker Compose, so I can use the containers to scale my project in Visual Studio.
@@ -15,10 +15,10 @@ ms.date: 08/28/2024
1515

1616
This article describes how to create multi-container apps with [MySQL](https://dev.mysql.com/) and [Docker Compose](https://docs.docker.com/compose/). An app with multiple containers allows you to dedicate containers for specialized tasks, so each container can focus on a single task. There are many advantages to using multi-container apps:
1717

18-
- Separate containers allow you to manage APIs and front-end resources differently than databases
19-
- Multiple containers let you version and update versions in isolation
20-
- Local databases can be maintained in containers and managed services used for databases in production
21-
- Multi-container apps are more efficient than running multiple processes with a process manager, which adds complexity to container startup/shutdown
18+
- Separate containers allow you to manage APIs and front-end resources differently than databases.
19+
- Multiple containers let you version and update versions in isolation.
20+
- Local databases can be maintained in containers and managed services used for databases in production.
21+
- Multi-container apps are more efficient than running multiple processes with a process manager, which adds complexity to container startup/shutdown.
2222

2323
In this tutorial, you:
2424

@@ -411,7 +411,7 @@ Now you can try running your *docker-compose.yml* file.
411411

412412
1. Stop any running instances of your application and database.
413413

414-
# [VS Code](#tab/visual-studio)
414+
# [Visual Studio Code](#tab/visual-studio-code)
415415

416416
Follow these steps in VS Code:
417417

@@ -439,7 +439,7 @@ Now you can try running your *docker-compose.yml* file.
439439

440440
1. Start your multi-container app and all services.
441441

442-
# [VS Code](#tab/visual-studio)
442+
# [Visual Studio Code](#tab/visual-studio-code)
443443

444444
Follow these steps in VS Code:
445445

@@ -469,7 +469,7 @@ Now you can try running your *docker-compose.yml* file.
469469

470470
1. Review the logs for the running container.
471471

472-
# [VS Code](#tab/visual-studio)
472+
# [Visual Studio Code](#tab/visual-studio-code)
473473

474474
Follow these steps in VS Code:
475475

@@ -509,7 +509,7 @@ Now you can try running your *docker-compose.yml* file.
509509

510510
When you're done with the app and containers, you can remove them.
511511

512-
# [VS Code](#tab/visual-studio)
512+
# [Visual Studio Code](#tab/visual-studio-code)
513513

514514
Follow these steps in VS Code:
515515

0 commit comments

Comments
 (0)