Apply suggestions from code review

Co-authored-by: Bradley Camacho <42678939+bradleycamacho@users.noreply.github.com>

Author: sbvegan

pages/stack/research/block-time-research.mdx

@@ -19,36 +19,35 @@ The following benchmarks are available in this [notebook](https://github.com/tes
 
 ## Benchmarks
 
-![Figure 1: op-geth / archive node / block 5492540 \~ 9816497
-.](/img/op-stack/protocol/block-time-research-figure-1.png)
+| ![Figure 1: op-geth / archive node / block 5492540 \~ 9816497.](/img/op-stack/protocol/block-time-research-figure-1.png)| 
+|:--:| 
+| **Figure 1**: op-geth / archive node / block 5492540 \~ 9816497 |
 
-**Figure 1**: op-geth / archive node / block 5492540 \~ 9816497
-
-![Figure 2: op-geth / full node / block 5492540 \~ 9816497.](/img/op-stack/protocol/block-time-research-figure-2.png)
-
-**Figure 2**: op-geth / full node / block 5492540 \~ 9816497
+| ![Figure 2: op-geth / full node / block 5492540 \~ 9816497.](/img/op-stack/protocol/block-time-research-figure-2.png) | 
+|:--:| 
+| **Figure 2**: op-geth / full node / block 5492540 \~ 9816497 |
 
 Figures 1 and 2 show the Base nodes' block-building time distribution with op-geth archive node & full node from block 5492540 to 9816497. We can see that the average block building time takes 0.58 and 0.36 seconds each for blocks that spent 25M \~ 30M gas, which is less than one second.
 
-![Figure 3: op-reth / archive node / block 5492540 \~ 9816497.](/img/op-stack/protocol/block-time-research-figure-3.png)
-
-**Figure 3**: op-reth / archive node / block 5492540 \~ 9816497
+| ![Figure 3: op-reth / archive node / block 5492540 \~ 9816497.](/img/op-stack/protocol/block-time-research-figure-3.png) | 
+|:--:| 
+| **Figure 3**: op-reth / archive node / block 5492540 \~ 9816497 |
 
 Figure 3 shows the Base nodes' block-building time distribution using the op-reth archive node from block 5492540 to 9816497. Compared to op-geth's archive node, we can see that op-reth shows a better performance in all ranges.
 
-![Figure 4: op-geth / archive node / block 13686867 \~ 15074141.](/img/op-stack/protocol/block-time-research-figure-4.png)
+| ![Figure 4: op-geth / archive node / block 13686867 \~ 15074141.](/img/op-stack/protocol/block-time-research-figure-4.png) | 
+|:--:| 
+| **Figure 4:** op-geth / archive node / block 13686867 \~ 15074141 |
 
-**Figure 4:** op-geth / archive node / block 13686867 \~ 15074141
-
-![Figure 5: op-geth / full node / block 14567037 \~ 15074141.](/img/op-stack/protocol/block-time-research-figure-5.png)
-
-**Figure 5:** op-geth / full node / block 14567037 \~ 15074141
+| ![Figure 5: op-geth / full node / block 14567037 \~ 15074141.](/img/op-stack/protocol/block-time-research-figure-5.png) | 
+|:--:| 
+| **Figure 5:** op-geth / full node / block 14567037 \~ 15074141 |
 
 Throughout the research, we found that the node meaningfully takes longer to build a block as the chain stores more states and transactions to access more historical data. Therefore, we benchmarked the latest blocks in Figures 4 and 5. On average, both the full node and archive node could build a congested block on time. It is worth noting that the average block-building time of high gas spending range is similar to the older blocks, but the average block-building time is higher on the newer blocks.
 
-![Figure 6: op-geth / archive node / block 13686867 \~ 15074141 / histogram of 25m\~30m gas range.](/img/op-stack/protocol/block-time-research-figure-6.png)
-
-**Figure 6**: op-geth / archive node / block 13686867 \~ 15074141 / histogram of 25m\~30m gas range
+| ![Figure 6: op-geth / archive node / block 13686867 \~ 15074141 / histogram of 25m\~30m gas range.](/img/op-stack/protocol/block-time-research-figure-6.png) | 
+|:--:| 
+| **Figure 6**: op-geth / archive node / block 13686867 \~ 15074141 / histogram of 25m\~30m gas range |
 
 If we zoom in on the 25m\~30m gas range of the archive node, the average could be potentially concerning–0.51 sec. It is worth noting that we can see the average is diverged from p50 (0.4 sec) because of outliers in the histogram (Figure 6), and p50 is a more important metric than the average for the block progression (Sequencer) because of its asynchronous nature.