From 71df96fd396468e26c89b14fec9aceab964e2ea2 Mon Sep 17 00:00:00 2001
From: Takuto Ikuta <tikuta@google.com>
Date: Tue, 14 Oct 2025 17:44:48 +0900
Subject: [PATCH 1/2] _content/doc/gc-guide: fix typo

---
 _content/doc/gc-guide.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_content/doc/gc-guide.html b/_content/doc/gc-guide.html
index 1be682018f..b0d49637e8 100644
--- a/_content/doc/gc-guide.html
+++ b/_content/doc/gc-guide.html
@@ -1527,7 +1527,7 @@ <h2 id="A_note_about_virtual_memory">A note about virtual memory</h2>
 
 <h2 id="Optimization_guide">Optimization guide</h2>
 
-<h3 id="Identiying_costs">Identifying costs</h3>
+<h3 id="Identifying_costs">Identifying costs</h3>
 
 <p>
 Before trying to optimize how your Go application interacts with the GC, it's

From c9e3fa68e011d5793deff3dc010d648c0bf009a3 Mon Sep 17 00:00:00 2001
From: Takuto Ikuta <tikuta@google.com>
Date: Wed, 15 Oct 2025 08:39:38 +0900
Subject: [PATCH 2/2] Update pgo.md

---
 _content/blog/pgo.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_content/blog/pgo.md b/_content/blog/pgo.md
index 4150095973..3d96feb211 100644
--- a/_content/blog/pgo.md
+++ b/_content/blog/pgo.md
@@ -350,7 +350,7 @@ Showing nodes accounting for -3.72s, 3.13% of 118.73s total
 ```
 
 So `runtime.scanobject` is ultimately coming from `runtime.gcBgMarkWorker`.
-The [Go GC Guide](/doc/gc-guide#Identiying_costs) tells us that `runtime.gcBgMarkWorker` is part of the garbage collector, so `runtime.scanobject` savings must be GC savings.
+The [Go GC Guide](/doc/gc-guide#Identifying_costs) tells us that `runtime.gcBgMarkWorker` is part of the garbage collector, so `runtime.scanobject` savings must be GC savings.
 What about `nextFreeFast` and other `runtime` functions?
 
 ```