[Docs] Move startup tracing docs into repository

components/tracing/docs/memory_infra.md

 # MemoryInfra
 
 MemoryInfra is a timeline-based profiling system integrated in chrome://tracing.
 It aims at creating Chrome-scale memory measurement tooling so that on any
 Chrome in the world --- desktop, mobile, Chrome OS or any other --- with the
 click of a button you can understand where memory is being used in your system.
 
 [TOC]
 
 ## Getting Started
@@ skipping 80 matching lines @@
 
 <!-- TODO(primiano): Improve this. https://crbug.com/??? -->
 
 [oilpan]:     /third_party/WebKit/Source/platform/heap/BlinkGCDesign.md
 [cc-memory]:  /cc/memory.md
 [gpu-memory]: memory_infra_gpu.md
 [partalloc]:  /third_party/WebKit/Source/wtf/PartitionAlloc.md
 
 ## Related Pages
 
+ * [Adding MemoryInfra Tracing to a Component](adding_memory_infra_tracing.md)
  * [GPU Memory Tracing](memory_infra_gpu.md)
  * [Heap Profiling with MemoryInfra](heap_profiler.md)
+ * [Startup Tracing with MemoryInfra](memory_infra_startup_tracing.md)
 
 ## Rationale
 
 Another memory profiler? What is wrong with tool X?
 Most of the existing tools:
 
  * Are hard to get working with Chrome. (Massive symbols, require OS-specific
    tricks.)
  * Lack Chrome-related context.
  * Don't deal with multi-process scenarios.
@@ skipping 46 matching lines @@
 
 Chrome-side design docs:
 
 <iframe width="100%" height="300px" src="https://docs.google.com/a/google.com/embeddedfolderview?id=0B3KuDeqD-lVJfndSa2dleUQtMnZDeWpPZk1JV0QtbVM5STkwWms4YThzQ0pGTmU1QU9kNVk">
 </iframe>
 
 Catapult-side design docs:
 
 <iframe width="100%" height="300px" src="https://docs.google.com/a/google.com/embeddedfolderview?id=0B3KuDeqD-lVJfm10bXd5YmRNWUpKOElOWS0xdU1tMmV1S3F4aHo0ZDJLTmtGRy1qVnQtVWM">
 </iframe>