diff --git a/pages/en/developing/creating-a-subgraph.mdx b/pages/en/developing/creating-a-subgraph.mdx
index 9efdde65196c..b48d23691da2 100644
--- a/pages/en/developing/creating-a-subgraph.mdx
+++ b/pages/en/developing/creating-a-subgraph.mdx
@@ -712,7 +712,7 @@ While events provide an effective way to collect relevant changes to the state o
 
 Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
 
-> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain, Arbitrum, Polygon, and Optimism do not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing with a NodeCapabilities error. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
 
 ### Defining a Call Handler