Merge branch 'main' into docs/openrpc/add-solana-simulateTransaction

Author: oskarciupider-alchemy

content/api-reference/arbitrum-nova/arbitrum-nova-chain-api-faq.mdx

@@ -43,7 +43,7 @@ Similar to Ethereum, Arbitrum Nova supports a range of programming languages for
 
 Arbitrum Nova uses ETH, Ethereum's native cryptocurrency, for transaction fees, gas, and other network activities.
 
-## What methods does Alchemy support for the Arbitrum Nova API?
+## Supported Arbitrum Nova methods
 
 You can find the list of all the methods Alchemy supports for the Arbitrum Nova API on the [Arbitrum Nova API Endpoints](/docs/chains#arbitrum-nova-apis) page.
 

content/api-reference/avalanche-p/avalanche-p-api-faq.mdx

@@ -43,7 +43,7 @@ Any language that can send HTTP POST requests and handle JSON works with the Ava
 
 The Avalanche P-Chain uses AVAX (and nAVAX) for staking, delegation, and transaction fees. Fee configuration can be queried via `platform.getFeeConfig` and `platform.getFeeState`.
 
-## What methods does Alchemy support for the Avalanche P-Chain API?
+## Supported Avalanche P-Chain methods
 
 You can find the list of supported Avalanche P-Chain methods on the [Avalanche P-Chain API Overview](/docs/avalanche-p/avalanche-p-api-overview) page.
 

content/api-reference/data/nft-api/nft-api-faq.mdx

@@ -25,7 +25,7 @@ All NFTs made with the ERC-721 and ERC-1155 standards are supported by the NFT A
 
 Alchemy is actively working on adding support for as many blockchains / NFT standards as we can. If you find that NFTs are missing in wallets you are calling, please provide details about the missing NFT over email: support@alchemy.com
 
-## How does Alchemy determine NFT standard (ERC-721 vs ERC-1155)?
+## How NFT standard is determined
 
 First, we collect the following data (each of which is an eth\_call):
 
@@ -68,7 +68,7 @@ NFT creators/developers can also "pin" their content, effectively caching and st
 
 While NFT gateway and raw URIs tend to be pointed at the same links, gateway URIs generally offer better performance.
 
-## What is the difference between `getNFTsForOwner` & `getNFTMetadata`?
+## `getNFTsForOwner` vs `getNFTMetadata`
 
 `getNFTsForOwner` is most commonly used when querying all NFTs owned by an address. By default, it will return both NFTs and any associated metadata per asset in the response. Common use cases include dashboards/wallets for viewing NFT assets held by a particular address.
 
@@ -85,7 +85,7 @@ Given a contract address, we look at a few things:
 
 If any of these are satisfied, we will mark an NFT as spam.
 
-## How can I understand why a particular NFT collection is marked as "Spam"?
+## Why an NFT collection is marked as spam
 
 The response object of Alchemy's `getNFTs` method contains a field called `classifications` inside `spamInfo`. This field is a list of tags, each of which map to a reason why the NFT was considered spam.
 
@@ -101,7 +101,7 @@ The tags are one of the below :-
 
 Floor price is queried per collection at request time and cached for 5 minutes. After that the floor price is refreshed by a best-effort fetch from the marketplace. The `retrievedAt` field is the timestamp of when the collection floor price was last updated for a marketplace.
 
-## Why does the `getFloorPrice` endpoint return slightly older floor price?
+## Why `getFloorPrice` returns older data
 
 The cache for the getFloorPrice function is only refreshed every 15 mins. So if your transaction has happened in the last 15 mins, you might want to wait to get the data.
 
@@ -157,13 +157,13 @@ Here's an example of a resized BAYC NFT asset cached by Alchemy: [https://res.cl
 
 ![378](https://alchemyapi-res.cloudinary.com/image/upload/v1764193029/docs/api-reference/data/nft-api/cdb00a2-Screenshot_2022-11-23_at_10.42.14_AM.png "Screenshot 2022-11-23 at 10.42.14 AM.png")
 
-## How can I get PNG images instead of SVG when using Alchemy's APIs?
+## Get PNG images instead of SVG
 
 By default Alchemy API returns the same image format as is in the metadata. Sometimes that means SVG images. In case you want to obtain the PNG format for those images instead, you can replace the string `/thumbnail` with `/convert-png` in the thumbnail URL value.
 
 Example: If the thumbnail URL is `https://res.cloudinary.com/alchemyapi/image/upload/thumbnail/eth-mainnet/<hash>`, you should replace it with `https://res.cloudinary.com/alchemyapi/image/upload/convert-png/eth-mainnet/<hash>` to get the PNG image
 
-## How can I resize a thumbnail and maintain the original resolution and aspect ratio?
+## Resize thumbnails with original aspect ratio
 
 In case you want to resize the media, you can make alterations to the original thumbnail URL or image URL to get the new URL that will return you a resized thumbnail with maintained aspect ratio.
 

content/api-reference/data/webhooks/custom-webhooks-quickstart/custom-webhooks-faq.mdx

@@ -35,10 +35,10 @@ Don't be alarmed if you're seeing blank data like the following!
 We send you notifications every time we run your GraphQL queries regardless of whether the filter results are *null*. This holds us accountable and serves as a receipt that we ran the query on each new canonical block!
 
 <Info>
-  If you want to turn this off and only receive webhooks for non-empty queries, check out instructions in the [next FAQ question](/docs/reference/custom-webhooks-faq#how-do-i-receive-webhooks-for-only-non-empty-results-ie-turn-off-the-heartbeat-mechanism-described-abovedont-receive-a-webhook-for-every-block)!
+  If you want to turn this off and only receive webhooks for non-empty queries, check out instructions in the [next FAQ question](/docs/reference/custom-webhooks-faq#receive-webhooks-only-for-non-empty-results)!
 </Info>
 
-## How do I receive webhooks for only non-empty results (i.e. turn off the heartbeat mechanism described above/don't receive a webhook for every block)?
+## Receive webhooks only for non-empty results
 
 To turn off the "heartbeat" mechanism for your webhook query (aka. only receive a webhook if the query on a block is not empty), you can change the `graphql_query` from a string to `{ query: string, skip_empty_messages: boolean }` and set the `skip_empty_messages` param to True. For example:
 
@@ -73,7 +73,7 @@ There is currently a limit of 100 GraphQL queries within each team account.
 
 If you're seeing 5xx error codes when creating webhooks, please ensure that you do not have *transactions.inputData* included as a parameter in your GraphQL query. We are heads-down working on ensuring reliable access across our entire API surface area!
 
-## Are there any constraints to the GraphQL interface in Custom Webhooks?
+## Custom Webhooks GraphQL constraints
 
 While logs and transactions can be self-referential entities, we only allow for a single-layer nested data structure to bound GraphQL queries. This helps us to to maintain a tidy API surface area.
 

content/api-reference/ethereum/ethereum-api-faq/ethereum-api-faq.mdx

@@ -66,7 +66,7 @@ Here is an [example request](https://composer.alchemy.com/?composer_state=%7B%22
 
 Block numbers themselves are Ethereum's measure of time, however standard timestamps are available by looking at the block data.
 
-## How do I distinguish between a contract address and a wallet address?
+## Contract vs wallet address
 
 A quick way to distinguish between a contract address and a wallet address is by calling [eth\_getCode](/docs/reference/eth-getcode), which returns contract code if it's a contract and nothing if it's a wallet. Here's an example of both using our composer tool:
 

content/api-reference/ethereum/ethereum-api-quickstart.mdx

@@ -97,7 +97,7 @@ Check out the following tutorials to learn how to build with Ethereum:
 
 * [Build a Web3 Dashboard](/docs/web3-dashboard-prompt)
 * [What is Proof of Stake?](/docs/what-is-proof-of-stake)
-* [How do I distinguish between a contract address and wallet address?](/docs/reference/ethereum-api-faq#how-do-i-distinguish-between-a-contract-address-and-a-wallet-address)
+* [How do I distinguish between a contract address and wallet address?](/docs/reference/ethereum-api-faq#contract-vs-wallet-address)
 
 For full documentation on Web3 libraries, check out the official documentation:
 

content/api-reference/lens/lens-api-faq.mdx

@@ -50,7 +50,7 @@ Lens Network aims to offer a smooth user experience comparable to Web2 applicati
 
 Yes, the new version of Lens Protocol will function as a cross-chain protocol. While the main hub will be on Lens Network with zkSync, instances can be deployed on other EVM (and non-EVM) networks, allowing developers to build social applications on various supported networks.
 
-## What happens to existing Lens Protocol users and applications?
+## Impact on existing Lens users and apps
 
 Users and applications can continue using the existing Lens Protocol and later migrate to Lens Network if they choose. The Lens team will support a smooth migration process for those who wish to transition.
 

content/api-reference/op-mainnet/op-mainnet-api-faq/op-mainnet-api-faq.mdx

@@ -134,7 +134,7 @@ The expected time for the upgrade to take place is between 2-4 hours.
 
 ***
 
-## Can developers still submit new transactions or access blockchain data via Alchemy while the upgrade is underway?
+## Accessing data during an upgrade
 
 You won't be able to send new transactions to the network during the upgrade. However, read access to the blockchain data through Alchemy will be available throughout the upgrade.
 

content/api-reference/polygon-zkevm/polygon-zkevm-api-faq/polygon-zkevm-api-faq.mdx

@@ -49,7 +49,7 @@ Polygon zkEVM does not have its own separate native token. Instead, it uses ETH
 
 The testnet you should use for Polygon zkEVM is the zkEVM Public Testnet. By connecting to this testnet, you can launch smart contracts, execute transactions, and test applications on the zkEVM network.
 
-## What methods does Alchemy support for the Polygon zkEVM API?
+## Supported Polygon zkEVM methods
 
 You can find the list of all the methods Alchemy supports for the Polygon zkEVM API on the [Polygon zkEVM API Endpoints](/docs/chains#polygon-zkevm-apis) page.
 

content/api-reference/pricing-resources/resources/error-reference.mdx

@@ -133,7 +133,7 @@ Here are some guidelines to limit client side issues:
 
 If you have any questions or feedback, contact us at support@alchemy.com or open a ticket in the Alchemy Dashboard.
 
-# How we define “successful” vs. “failed” requests in the Alchemy Dashboard
+# Successful vs failed request definitions
 
 The Alchemy Dashboard includes various charts that indicate the number of successful or failed requests across your applications. A few examples include: