From 79aaf57394c7c1ae0a9ed6ca5602a22a3849c718 Mon Sep 17 00:00:00 2001
From: Joan E <153745173+joaniefromtheblock@users.noreply.github.com>
Date: Sat, 13 Jul 2024 00:54:47 +0000
Subject: [PATCH] another pass and fix tables

---
 .../json-rpc-methods/trace-methods/index.md    | 18 +++++++++++++++++-
 snaps/how-to/request-permissions.md            |  4 +++-
 2 files changed, 20 insertions(+), 2 deletions(-)

diff --git a/services/reference/linea/json-rpc-methods/trace-methods/index.md b/services/reference/linea/json-rpc-methods/trace-methods/index.md
index cd548ee792d..2c93b9a5953 100644
--- a/services/reference/linea/json-rpc-methods/trace-methods/index.md
+++ b/services/reference/linea/json-rpc-methods/trace-methods/index.md
@@ -44,4 +44,20 @@ smart contract transaction. Excludes precompiled contracts.
 ]
 ```
 
-<table><thead><tr><th width="242">Key</th><th>Value</th></tr></thead><tbody><tr><td><code>action</code> </td><td>Transaction details.</td></tr><tr><td><code>callType</code></td><td> Whether the transaction is <code>call</code> or <code>create</code>.</td></tr><tr><td><code>from</code></td><td>Address of the transaction sender.</td></tr><tr><td><code>gas</code></td><td>Gas provided by sender.</td></tr><tr><td><code>input</code></td><td>Transaction data.</td></tr><tr><td><code>to</code></td><td>Target of the transaction.</td></tr><tr><td><code>value</code></td><td>Value transferred in the transaction.</td></tr><tr><td><code>result</code></td><td>Transaction result.</td></tr><tr><td><code>gasUsed</code></td><td>Gas used by the transaction. Includes any refunds of unused gas.</td></tr><tr><td><code>output</code></td><td>Return value of the contract call. Contains only the actual value sent by a <code>RETURN</code> operation. If a <code>RETURN</code> was not executed, the output is empty bytes.</td></tr><tr><td><code>subTraces</code></td><td>Traces of contract calls made by the transaction.</td></tr><tr><td><code>traceAddress</code></td><td>Tree list address of where the call occurred, address of the parents, and order of the current sub call.</td></tr><tr><td><code>transactionHash</code></td><td>Hash of the transaction.</td></tr><tr><td><code>transactionPosition</code></td><td>Transaction position.</td></tr><tr><td><code>type</code></td><td>Whether the transaction is a <code>CALL</code> or <code>CREATE</code> series operation.</td></tr></tbody></table>
+| Key                 |Value                                                                                                      |
+|---------------------|-----------------------------------------------------------------------------------------------------------|
+| `action`            | Transaction details.                                                                                      |
+| `callType`          | Whether the transaction is `call` or `create`.                                                            |
+| `from`              | Address of the transaction sender.                                                                        |
+| `gas`               | Gas provided by sender.                                                                                   |
+| `input`             | Transaction data.                                                                                         |
+| `to`                | Target of the transaction.                                                                                |
+| `value`             | Value transferred in the transaction.                                                                     |
+| `result`            | Transaction result.                                                                                       |
+| `gasUsed`           | Gas used by the transaction. Includes any refunds of unused gas.                                          |
+| `output`            | Return value of the contract call. Contains only the actual value sent by a `RETURN` operation. If a `RETURN` was not executed, the output is empty bytes.  |
+| `subTraces`         | Traces of contract calls made by the transaction.                                                         |
+| `traceAddress`      | Tree list address of where the call occurred, address of the parents, and order of the current sub call.  |
+| `transactionHash`   | Hash of the transaction.                                                                                  |
+| `transactionPosition`| Transaction position.                                                                                    |
+| `type`              | Whether the transaction is a `CALL` or `CREATE` series operation.                                         |
diff --git a/snaps/how-to/request-permissions.md b/snaps/how-to/request-permissions.md
index ce6a9a8c055..f1b71eec312 100644
--- a/snaps/how-to/request-permissions.md
+++ b/snaps/how-to/request-permissions.md
@@ -28,13 +28,15 @@ following to the manifest file:
 ```
 
 :::note
+
 All Snaps API methods except the following interactive UI methods require requesting permission in
 the manifest file:
 
 - [`snap_createInterface`](../reference/snaps-api.md#snap_createinterface)
 - [`snap_getInterfaceState`](../reference/snaps-api.md#snap_getinterfacestate)
 - [`snap_updateInterface`](../reference/snaps-api.md#snap_updateInterface)
-  :::
+
+:::
 
 ### Endowments