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")