From 060764ab13ba810b1d4b70a3e847c5ed798e71c4 Mon Sep 17 00:00:00 2001
From: Rodolforiv0621 <78060969+Rodolforiv0621@users.noreply.github.com>
Date: Mon, 7 Apr 2025 20:38:02 -0700
Subject: [PATCH] Update part12b.md, changed 'to ran it' to 'to run it'

Fixed grammer
---
 src/content/12/en/part12b.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/12/en/part12b.md b/src/content/12/en/part12b.md
index efdaba2d655..5cef77033cb 100644
--- a/src/content/12/en/part12b.md
+++ b/src/content/12/en/part12b.md
@@ -293,7 +293,7 @@ Tip: Run the application outside of a container to examine it before starting to
 
 ### Using Docker compose
 
-In the previous section, we created an Express server, knowing that it will run in port 3123, and used the commands _docker build -t express-server . && docker run -p 3123:3000 express-server_ to ran it. This already looks like something you would need to put into a script to remember. Fortunately, Docker offers us a better solution.
+In the previous section, we created an Express server, knowing that it will run in port 3123, and used the commands _docker build -t express-server . && docker run -p 3123:3000 express-server_ to run it. This already looks like something you would need to put into a script to remember. Fortunately, Docker offers us a better solution.
 
 [Docker compose](https://docs.docker.com/compose/) is another fantastic tool, which can help us to manage containers. Let's start using compose as we learn more about containers as it will help us save some time with the configuration.