docs: minor fix in memory-infra compositor doc

docs/memory-infra/probe-cc.md

 # Memory Usage in CC
 
 This document gives an overview of memory usage in the CC component, as well as
 information on how to analyze that memory.
 
 [TOC]
 
 ## Types of Memory in Use
 
 CC uses a number of types of memory:
@@ skipping 25 matching lines @@
 size will be attributed to cc/tile_memory (effective_size of cc/resource_memory
 will not include these resources).
 
 If the one-copy tile update path is in use, the cc category will also enumerate
 staging resources used as intermediates when drawing tiles. These resources are
 like tile_memory, in that they are shared with cc/resource_memory.
 
 Note that depending on the path being used, CC memory may be either shared
 memory or GPU memory:
 
+```
 Path         | Tile Memory Type     | Staging Memory Type
 -------------|-------------------------------------------
 Bitmap       | Shared Memory        | N/A
 One Copy     | GPU Memory           | Shared Memory
 Zero Copy    | GPU or Shared Memory | N/A
 GPU          | GPU Memory           | N/A
+```
 
 Note that these values can be determined from a memory-infra dump. For a given
 resource, hover over the small green arrow next to it's "size". This will show
 the other allocations that this resource is aliased with. If you see an
 allocation in the GPU process, the memory is generally GPU memory. Otherwise,
 the resource is typically Shared Memory.
 
 Tile and Staging memory managers are set up to evict any resource not used
 within 1s.
 
@@ skipping 54 matching lines @@
     Shared Memory GpuMemoryBuffer objects are allocated by the browser and will
     also tracked in this category.
 
 ## Memory TODOs
 
 The following areas have insufficient memory instrumentation.
 
 1.  DisplayLists - DisplayLists can be quite large and are currently
     un-instrumented. These use malloc memory and currently contribute to
     malloc/allocated_objects/<unspecified>. [BUG](https://crbug.com/567465)