Pectra fees: use a table to summarize actions

pages/notices/pectra-fees.mdx

@@ -31,21 +31,34 @@ Chains configured for blob data availability remain entirely unaffected by the P
 
 Since the Ecotone upgrade, the Optimism protocol prices L2 transactions using a function that incorporates the L1 base fee as well as the L1 blob base fee. The other inputs are the so-called "Ecotone scalars": operator-controlled parameters stored in the SystemConfig contract which can be used to tune the chain's (approximate) target profit margin for DA.
 
-Please review your [Ecotone scalar chain configuration](/operators/chain-operators/management/blobs). 
+Please review your [Ecotone scalar chain configuration](/operators/chain-operators/management/blobs).
 
 <Callout type="info">
-If your chain uses a zero blob base fee scalar, meaning it's configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary and the rest of this section does not apply.
+  If your chain uses a zero blob base fee scalar, meaning it is configured to price for calldata only, you may need to update the base fee scalar and/or the blob base fee scalar. Otherwise, no action is necessary.
 </Callout>
 
+The impact and recommended actions for each of the possible configurations are summarized in the following table, and explained in more detail below:
+
+| `baseFeeScalar` | `blobBaseFeeScalar` | batcher DA                    | Impact                                 | Action                                                                                           |
+| --------------- | ------------------- | ----------------------------- | -------------------------------------- | ------------------------------------------------------------------------------------------------ |
+| any             | >\~10^4             | `calldata`, `blob`, or `auto` |                                        | No action required                                                                               |
+| `x`             | 0                   | `calldata`                    | Undercharging L2 Users                 | Check scalar config and consider setting `baseFeeScalar` to `x * 10/4` to preserve profit margin |
+| any             | 0                   | `blob` or `auto`              | Overcharging L2 Users most of the time | Check scalar config and consider setting a positive `blobBaseFeeScalar`                          |
+
 ### Chains charging for calldata DA and spending on calldata DA
+
 If your chain uses a zero blob base fee scalar and your batcher is configured to submit using calldata *only*, then you should take the opportunity to check your chain's profit margin according to [this guide](/operators/chain-operators/management/blobs) and make any adjustments to your Ecotone scalars as necessary. This will ensure that, since you are paying exclusively for calldata DA, you are charging users appropriately such that your target profit margin is as desired.
 
 If your profit margin was perfectly tuned before Pectra, then you should scale your base fee scalar by 10/4.
 
 ### Chains charging for calldata DA and spending on blob DA
+
 If your chain uses a zero blob base fee scalar and your batcher is configured to submit using blob DA, or configured to automatically choose the cheaper of the two DA modes, then you should adjust your Ecotone scalars for blob DA pricing (meaning a nonzero blob base fee scalar). You are referred back to [this guide](/operators/chain-operators/management/blobs). Doing so will ensure that you are charging accurately for using blob DA. Without such a change it is likely that you are overcharging users most of the time, and undercharging them in the rare occasions where blob DA is more expensive than calldata DA on Ethereum mainnet.
 
-As ever, you may continue to tweak the Ecotone scalars as desired in order to adjust the profitability of your chain.
+### General remarks
+
+Continue tweaking the Ecotone scalars as desired to adjust your chain's profitability.
+Chain operators should monitor profitability continuously so that scalars can be adjusted as necessary.
 
 ### Technical references