From 18b588f82ed0668bf64d3878f1d0db88159354c6 Mon Sep 17 00:00:00 2001 From: alchemy-bot <80712764+alchemy-bot@users.noreply.github.com> Date: Wed, 8 Jul 2026 09:39:41 +0000 Subject: [PATCH] [docs-agent] Fix three text errors on trace API reference pages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * trace_call vs debug_traceCall page: fix copy-paste error in the debug_traceCall section — the sentence describing client support was copied from the trace_call section. Corrected to say debug_traceCall is supported by most Ethereum clients (Geth, Erigon, reth, and others). * Same page: add missing space after "Under the hood," in the trace_call section. * what-is-trace_transaction page: remove leading "As" that turned the Transaction Tracers intro into a sentence fragment. Refs DOCS-134 Requested-by: @seansing --- .../trace-api-resources/trace-call-vs-debug-tracecall.mdx | 4 ++-- .../trace-api-resources/what-is-trace-transaction.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/api-reference/trace-api/trace-api-resources/trace-call-vs-debug-tracecall.mdx b/content/api-reference/trace-api/trace-api-resources/trace-call-vs-debug-tracecall.mdx index 16d41617b..f098b175c 100644 --- a/content/api-reference/trace-api/trace-api-resources/trace-call-vs-debug-tracecall.mdx +++ b/content/api-reference/trace-api/trace-api-resources/trace-call-vs-debug-tracecall.mdx @@ -21,7 +21,7 @@ Before reading this article you should know about [Ethereum Clients](https://www # The trace\_call method -The [trace\_call](/docs/reference/trace-call) method executes the given call (transaction) and returns a number of possible traces for it. It’s helpful for debugging transactions and analyzing state changes due to a transaction. Under the hood,[trace\_call](/docs/reference/trace-call) is only supported by OpenEthereum or Erigon clients, but if you’re using an Alchemy API key we’ll automatically route the request for you so you don’t have to worry about the node client. +The [trace\_call](/docs/reference/trace-call) method executes the given call (transaction) and returns a number of possible traces for it. It’s helpful for debugging transactions and analyzing state changes due to a transaction. Under the hood, [trace\_call](/docs/reference/trace-call) is only supported by OpenEthereum or Erigon clients, but if you’re using an Alchemy API key we’ll automatically route the request for you so you don’t have to worry about the node client. Here are the parameters and response payloads for `trace_call` @@ -138,7 +138,7 @@ The `trace_call` method returns an array of traces. The structure of these trace # The debug\_traceCall method -The [debug\_traceCall](/docs/reference/debug-tracecall) method executes the given call (transaction) and returns a number of possible traces for it. It’s helpful for debugging transactions and analyzing state changes due to a transaction. Under the hood,[debug\_traceCall](/docs/reference/debug-tracecall) is only supported by OpenEthereum or Erigon clients, but if you’re using an Alchemy API key we’ll automatically route the request for you so you don’t have to worry about the node client. +The [debug\_traceCall](/docs/reference/debug-tracecall) method executes the given call (transaction) and returns a number of possible traces for it. It’s helpful for debugging transactions and analyzing state changes due to a transaction. Under the hood, `debug_traceCall` is supported by most Ethereum clients (Geth, Erigon, reth, and others). Here are the parameters and response payloads for `debug_traceCall` diff --git a/content/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx b/content/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx index cbd557b78..920510862 100644 --- a/content/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx +++ b/content/api-reference/trace-api/trace-api-resources/what-is-trace-transaction.mdx @@ -173,7 +173,7 @@ Here is the [link](https://etherscan.io/tx/0xda8c0b80d8e240a83c8f6b067c4656babeb ### **Transaction Tracers** -As you can get the traces for a previously executed transaction using `trace_call`. Transaction tracers help us better understand the flow of a transaction. They extract the EVM traces for a transaction and display them in a way that’s readable by us. +You can get the traces for a previously executed transaction using `trace_call`. Transaction tracers help us better understand the flow of a transaction. They extract the EVM traces for a transaction and display them in a way that’s readable by us. ![1998](https://alchemyapi-res.cloudinary.com/image/upload/v1764192960/docs/api-reference/trace-api/trace-api-resources/3571567-txs-fyi.png "txs-fyi.png")