From 5decac35f0b391f8ddd091b53b29073afcbf6e59 Mon Sep 17 00:00:00 2001
From: TheFoxerThatFoxed <214658836+UnFoxable@users.noreply.github.com>
Date: Fri, 24 Jul 2026 02:28:00 +0800
Subject: [PATCH] Update part3c.md

---
 src/content/3/en/part3c.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/3/en/part3c.md b/src/content/3/en/part3c.md
index 6bc9ade2784..5e9cb17f31b 100644
--- a/src/content/3/en/part3c.md
+++ b/src/content/3/en/part3c.md
@@ -638,7 +638,7 @@ Full stack development is <i> extremely hard</i>, that is why I will use all the
 - I will have my browser developer console open all the time
 - I will use the network tab of the browser dev tools to ensure that frontend and backend are communicating as I expect
 - I will constantly keep an eye on the state of the server to make sure that the data sent there by the frontend is saved there as I expect
-- <i>I will keep an eye on the database: does the backend save data there in the right format</i>
+- <i>I will keep an eye on the database; whether the data is saved in the expected state</i>
 - I progress with small steps
 - I will write lots of _console.log_ statements to make sure I understand how the code behaves and to help pinpoint problems
 - If my code does not work, I will not write more code. Instead, I start deleting the code until it works or just return to a state when everything was still working