diff --git a/curriculum/challenges/english/blocks/lecture-understanding-performance-in-web-applications/67d2f7cf63fafe7d20270498.md b/curriculum/challenges/english/blocks/lecture-understanding-performance-in-web-applications/67d2f7cf63fafe7d20270498.md
index e5791d3c1b8..b03d47d3f71 100644
--- a/curriculum/challenges/english/blocks/lecture-understanding-performance-in-web-applications/67d2f7cf63fafe7d20270498.md
+++ b/curriculum/challenges/english/blocks/lecture-understanding-performance-in-web-applications/67d2f7cf63fafe7d20270498.md
@@ -35,7 +35,7 @@ const end = performance.now();
 console.log(`Execution time: ${end - start}ms`);
 ```
 
-This is more accurate than using `Date.now()` because it measures time in microseconds, avoiding clock drift issues. You can use it to track script execution time, event response delays and animation performance.
+This is more accurate than using `Date.now()` because it measures time in milliseconds with microsecond precision, avoiding clock drift issues. You can use it to track script execution time, event response delays, and animation performance.
 
 Next, the Performance Timing API.
 
@@ -97,7 +97,7 @@ What is the main advantage of using `performance.now()` over `Date.now()`?
 
 ## --answers--
 
-It's more accurate and measures time in microseconds.
+It's more accurate and measures time in milliseconds with microsecond precision.
 
 ---