From f98e34d5b569edf079ab0099772cf2f063cb447c Mon Sep 17 00:00:00 2001
From: denny-ddfe <101379619+denny-ddfe@users.noreply.github.com>
Date: Tue, 9 Dec 2025 13:49:44 +1100
Subject: [PATCH] Update explanation for auto-reloading with ts-node-dev

Updated description of previous implementation of auto-reloading. The course so far has used the --watch flag, not nodemon
---
 src/content/9/en/part9b.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/9/en/part9b.md b/src/content/9/en/part9b.md
index ad95b4e357..5f90406610 100644
--- a/src/content/9/en/part9b.md
+++ b/src/content/9/en/part9b.md
@@ -750,7 +750,7 @@ Let's rename the *req* variable to *_req*. Finally, we are ready to start the ap
 
 ![browser result showing pong on /ping](../../images/9/11a.png)
 
-To simplify the development, we should enable *auto-reloading* to improve our workflow. In this course, you have already used *nodemon*, but ts-node has an alternative called *ts-node-dev*. It is meant to be used only with a development environment that takes care of recompilation on every change, so restarting the application won't be necessary.
+To simplify the development, we should enable *auto-reloading* to improve our workflow. In this course, we have started backends by running *node --watch server.js*, but ts-node does not support the *--watch* argument. Instead, we will use an alternative called *ts-node-dev*. It is meant to be used only with a development environment that takes care of recompilation on every change, so restarting the application won't be necessary.
 
 Let's install *ts-node-dev* to our development dependencies: