[tcmalloc] remove remaining references to tcmalloc.

This is a follow-up to
https://chromium-review.googlesource.com/c/chromium/src/+/3402604.

Bug: 1257213, 973552, 98589
Change-Id: Ibee15fcf8b444e4d0c5db65a49d5f34fd8b78e05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3402350
Reviewed-by: Benoit Lize <[email protected]>
Reviewed-by: Nico Weber <[email protected]>
Reviewed-by: Dmitry Gozman <[email protected]>
Reviewed-by: Jamie Walch <[email protected]>
Commit-Queue: Thiabaud Engelbrecht <[email protected]>
Cr-Commit-Position: refs/heads/main@{#969727}
diff --git a/docs/memory/README.md b/docs/memory/README.md
index 0d18fef..4b2f6d57 100644
--- a/docs/memory/README.md
+++ b/docs/memory/README.md
@@ -45,8 +45,8 @@
 There are roughly three types of memory work within Chrome:
 
 * Team based, targeted improvements. Examples include:
-    * memory reductions for specific components like v8
-    * allocator improvements: tcmalloc for linux + cros, PartitionAlloc for blink, etc.
+    * memory reductions for specific components [e.g. for v8]
+    * allocator improvements [e.g. PartitionAlloc]
     * memory purging at appropriate times [e.g. on tab background]
     * better memory pressure signals
 * Memlog: Heap profiling in the wild for regression detection + root cause