From 7c68f400006a2c09d69ae5441286ff7fa8314bb5 Mon Sep 17 00:00:00 2001
From: neotheobserver <65279181+neotheobserver@users.noreply.github.com>
Date: Sun, 15 Feb 2026 14:53:24 +0545
Subject: [PATCH] 630 seconds with 1.4*10^9 cycle per seconds calculates to
 almost 10^12 seconds not 10^15 seconds

---
 content/english/hpc/complexity/languages.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/english/hpc/complexity/languages.md b/content/english/hpc/complexity/languages.md
index abb80979..27475839 100644
--- a/content/english/hpc/complexity/languages.md
+++ b/content/english/hpc/complexity/languages.md
@@ -84,7 +84,7 @@ print(duration)
 
 This code runs in 630 seconds. That's more than 10 minutes!
 
-Let's try to put this number in perspective. The CPU that ran it has a clock frequency of 1.4GHz, meaning that it does $1.4 \cdot 10^9$ cycles per second, totaling to almost $10^{15}$ for the entire computation, and about 880 cycles per multiplication in the innermost loop.
+Let's try to put this number in perspective. The CPU that ran it has a clock frequency of 1.4GHz, meaning that it does $1.4 \cdot 10^9$ cycles per second, totaling to almost $10^{12}$ for the entire computation, and about 880 cycles per multiplication in the innermost loop.
 
 This is not surprising if you consider the things that Python needs to do to figure out what the programmer meant: