Typo fixes #20

data-catalog/evm/corn/raw/traces.mdx

@@ -8,5 +8,4 @@ import { TracesSnippet } from '/snippets/evm/raw/traces-snippet.mdx';
 import { ColumnDescriptions } from "/snippets/column-descriptions.mdx";
 import { TableSample } from "/snippets/table-sample.mdx";
 
-
-<TracesSnippet blockchain="corn" />
+<TracesSnippet blockchain="corn" />

data-catalog/evm/degen/overview.mdx

@@ -7,7 +7,7 @@ description: degen data on Dune
 
 Degen, an ERC-20 token launched in January 2024, has reshaped the Farcaster ecosystem by enabling Casters to reward others with DEGEN for posting quality content. Our points system recognizes unique posts and comments, effectively bridging the gap between online contributions and real-world value.
 
-Degen has launched a layer3 solution that settles transactions on the base network. This solution is designed to provide a more efficient and scalable way to settle transactions related to $degen.
+Degen has launched a layer 3 solution that settles transactions on the Base network. This solution is designed to provide a more efficient and scalable way to settle transactions related to $DEGEN.
 Degen Chain uses Arbitrum Orbit for rollups, Base for transaction settlements, and Arbitrum AnyTrust for data availability. 
 
 

data-catalog/evm/ethereum/curated-data/dex/dex-aggregator-trades.mdx

@@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for ethereum
 import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx';
 import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx";
 import { ColumnDescriptions } from "/snippets/column-descriptions.mdx";
-import { TableSampleParam} from "/snippets/table-sample-with-param.mdx";
+import { TableSampleParam } from "/snippets/table-sample-with-param.mdx";
 
 
 <DexAggregatorTradesSnippet blockchain="ethereum" />

data-catalog/evm/ethereum/curated-data/dex/dex-trades.mdx

@@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc
 import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx';
 import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx";
 import { ColumnDescriptions } from "/snippets/column-descriptions.mdx";
-import { TableSampleParam} from "/snippets/table-sample-with-param.mdx";
+import { TableSampleParam } from "/snippets/table-sample-with-param.mdx";
 
 <DexTradesSnippet blockchain="ethereum" />

data-catalog/evm/ethereum/curated-data/nft/nft-trades.mdx

@@ -1,7 +1,7 @@
 ---
-title: NFT.trades on ethereum
+title: NFT Trades on Ethereum
 sidebarTitle: NFT Trades
-description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on ethereum."
+description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Ethereum."
 ---
 
 import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx';

data-catalog/evm/ethereum/decoded/call-tables.mdx

@@ -54,7 +54,7 @@ However, if one of these functions is invoked by another smart contract in the c
 
 In short: **State data stored in the memory of a smart contract is not available on Dune!**
 
-A good example of this is the function `decimals` of the [erc20 token contract](https://etherscan.io/token/0x1f9840a85d5af5bf1d1762f925bdaddc4201f984#readContract) `Uni` which is a `constant` state variable that is able to be accessed through an automatically created "[getter function](https://docs.soliditylang.org/en/v0.7.4/contracts.html#getter-functions)". Should a smart contract invoke this function in the context of transaction, this message call will be recorded in the Dune table [`uniswap_ethereum.UNI_call_decimals"`](https://dune.com/queries/741354).
+A good example of this is the function `decimals` of the [ERC20 token contract](https://etherscan.io/token/0x1f9840a85d5af5bf1d1762f925bdaddc4201f984#readContract) `Uni` which is a `constant` state variable that is able to be accessed through an automatically created "[getter function](https://docs.soliditylang.org/en/v0.7.4/contracts.html#getter-functions)". Should a smart contract invoke this function in the context of a transaction, this message call will be recorded in the Dune table [`uniswap_ethereum.UNI_call_decimals`](https://dune.com/queries/741354).
 
 This is in contrast to anyone calling this function locally using web3.py/web3.js or using the Etherscan frontend to access this state. These local calls are not recorded in Dune.
 

data-catalog/evm/ethereum/decoded/event-logs.mdx

@@ -47,7 +47,7 @@ Let's take the [uniswap v3 factory](https://etherscan.io/address/0x1f98431c8ad98
 
 ## Multiple Instances
 
-If there is multiple instances of a contract we will collect all event logs across all instances of this smart contract in one table. For example, all uniswap v3 pool `swap` events (on ethereum) are stored in the table: `uniswap_v3_ethereum.Pair_evt_Swap`
+If there are multiple instances of a contract we will collect all event logs across all instances of this smart contract in one table. For example, all uniswap v3 pool `swap` events (on ethereum) are stored in the table: `uniswap_v3_ethereum.Pair_evt_Swap`
 
 The column `contract_address` indicates as to which smart contract emitted this event.
 

data-catalog/evm/ethereum/decoded/logs-decoded.mdx

@@ -8,7 +8,7 @@ description: Description of the ethereum.logs_decoded table on Dune
 
 The `logs_decoded` table contains decoded logs from Ethereum transactions. The table matches `topic0` to the event signature and the corresponding event name. The table does not contain the full event data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Event Logs](/data-catalog/evm/ethereum/decoded/event-logs). 
 
-This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol.
+This table is great for gaining a high-level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol.
 
 ## Column Descriptions
 

data-catalog/evm/ethereum/decoded/overview.mdx

@@ -37,7 +37,7 @@ Dune's decoded data approach offers several benefits:
 
 ## Which contracts have decoded data?
 
-Contract submission on Dune are driven by the community. Usually the odds are good that the contract you are looking at is already decoded, but esepecially for new projects or new contracts, it might be that the contract is not decoded yet. In those cases you can submit the contract to be decoded. Decoding usually takes about 24 hours, in special cases it might take longer.
+Contract submissions on Dune are driven by the community. Usually the odds are good that the contract you are looking at is already decoded, but especially for new projects or new contracts, it might be that the contract is not decoded yet. In those cases you can submit the contract to be decoded. Decoding usually takes about 24 hours, in special cases it might take longer.
 
 You can check if contracts are already decoded by querying [`[blockchain].contracts`](/data-catalog/evm/ethereum/decoded/contracts) tables, the [data explorer](/web-app/query-editor/data-explorer) or use [this dashboard](https://dune.com/dune/is-my-contract-decoded-yet-v2).
 
@@ -108,7 +108,7 @@ WHERE evt_tx_hash = 0x2bb7c8283b782355875fa37d05e4bd962519ea294678a3dcf2fdffbbd0
 
 How exactly does this work?
 
-Since we know which event we are looking at here, we can simply convert the encoded bytecode to decoded data by decoding the bytecode according to it's datatype.
+Since we know which event we are looking at here, we can simply convert the encoded bytecode to decoded data by decoding the bytecode according to its datatype.
 
 The structure for the `Transfer` event log of an ERC20 token will always be:
 
@@ -139,6 +139,6 @@ It's not always easy for a human to understand what exactly is going on in these
 
 If you are not able to make sense of the data by just searching the tables, it usually helps to look at single transactions using the transaction hash and Etherscan.
 
-Furthermore, actually going into the smart contracts code (our favorite way to do this is [DethCode](https://etherscan.deth.net)) to read the comments or the actual logic can help to understand the smart contract's emitted data.
+Furthermore, actually going into the smart contract's code (our favorite way to do this is [DethCode](https://etherscan.deth.net)) to read the comments or the actual logic can help to understand the smart contract's emitted data.
 
 If that also doesn't lead to satisfactory results, scouring the relevant docs and GitHub of the project can lead you to the desired answers. Furthermore, talking to the developers and core community of a project can also help you to get an understanding of the smart contracts.

data-catalog/evm/ethereum/decoded/traces-decoded.mdx

@@ -6,7 +6,7 @@ description: Description of the ethereum.traces_decoded table on Dune
 
 ## Table Description
 
-The `traces_decoded` table contains decoded traces from Ethereum transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/ethereum/decoded/traces-decoded). 
+The `traces_decoded` table contains decoded traces from Ethereum transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/ethereum/decoded/call-tables). 
 
 This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol.