Move memory docs to docs/memory-infra

docs/memory-infra/probe-gpu.md

Index: docs/memory-infra/probe-gpu.md
diff --git a/components/tracing/docs/memory_infra_gpu.md b/docs/memory-infra/probe-gpu.md
similarity index 97%
copy from components/tracing/docs/memory_infra_gpu.md
copy to docs/memory-infra/probe-gpu.md
index 57f49a48d54691cbd0cf104610504330b9154678..17fa5a8a3bc37832b3a12a5981f672974ffcca4c 100644
--- a/components/tracing/docs/memory_infra_gpu.md
+++ b/docs/memory-infra/probe-gpu.md
@@ -11,7 +11,7 @@ category and look at the _size_ column. (Not _effective size_.)
 
 ![Look at the size column for total GPU memory][gpu-size-column]
 
-[memory-infra]:    memory_infra.md
+[memory-infra]:    README.md
 [gpu-size-column]: https://storage.googleapis.com/chromium-docs.appspot.com/c7d632c18d90d99e393ad0ade929f96e7d8243fe
 
 ## In Depth
@@ -45,7 +45,7 @@ Renderer or browser process:
  * **CC Category**: The CC category contains all resource allocations used in
    the Chrome Compositor. When GPU rasterization is enabled, these resource
    allocations will be GPU allocations as well. See also
-   [cc/memory][cc-memory].
+   [docs/memory-infra/probe-cc.md][cc-memory].
  * **Skia/gpu_resources Category**: All GPU resources used by Skia.
  * **GPUMemoryBuffer Category**: All GPUMemoryBuffers in use in the current
    process.
@@ -88,6 +88,6 @@ you can look at the size column (not effective size) of just the GPU process'
 GPU category. This will show all GPU allocations, whether or not they are owned
 by another process.
 
-[cc-memory]:      /cc/memory.md
+[cc-memory]:      /docs/memory-infra/probe-cc.md
 [owner-size]:     https://storage.googleapis.com/chromium-docs.appspot.com/a325c4426422e53394a322d31b652cfa34231189
 [non-owner-size]: https://storage.googleapis.com/chromium-docs.appspot.com/b8cf464636940d0925f29a102e99aabb9af40b13