_content/doc/gc-guide: fix typo

Change-Id: Id300424ca0aa56f7019788db56d88190ca9b81a5
GitHub-Last-Rev: c9e3fa6
GitHub-Pull-Request: #332
Reviewed-on: https://go-review.googlesource.com/c/website/+/711600
Reviewed-by: Michael Pratt <[email protected]>
LUCI-TryBot-Result: Go LUCI <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
Reviewed-by: Dmitri Shuralyov <[email protected]>
Auto-Submit: Dmitri Shuralyov <[email protected]>

Author: atetubou

_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?
 
 ```

_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