Enhance documentation and .gitignore updates

- Added new log files to .gitignore to prevent unnecessary tracking.
- Updated links and fixed formatting in various documentation files, including coinpath and examples.
- Improved clarity in filtering sections across multiple schema documents by adding new lines for better readability.
- Corrected minor typographical errors in documentation headings and links.

Author: divyasshree-BQ

.gitignore

@@ -28,4 +28,6 @@ audit.log
 audit2.log
 fix.log
 force.log
-serialize_javascript.log
+serialize_javascript.log
+docs/Schema/algorand/coinpath.md
+build.log

docs/Examples/coinpath/money-flow-api.md

@@ -73,7 +73,7 @@ Follow the steps here to create one: [How to generate Bitquery API token ➤](ht
 
 ### 3. Multi-Chain Examples
 
-- [Cardano Wallet Inflows](#getting-inflows--fund-moving-in-to-a-cardano-wallet-address)
+- [Cardano Wallet Inflows](#getting-inflows-funds-moving-in-to-a-cardano-walletaddress)
 - [Ethereum Multi-Hop Tracking](#get-transactions-from-multiple-addresses-to-a-final-destination-address)
 
 ### 4. Funding History & Bundle Detection

docs/Examples/dexTrades/dex-trading-data-api.md

@@ -18,9 +18,12 @@ In the case of Buy/Sell Currency, we look into only 1 side of the swap.
 However, in the case of Base/Quote Currency, we look at both sides of the swap.
 
 For example - Let's say there are 3 trades.
-1 - A <-> B
-2 - B <-> C
-3 - C <-> A
+
+```
+1 - A < - > B
+2 - B < - > C
+3 - C < - > A
+```
 
 Now when you query, give me all trades where sellCurrency is B, and we will give only 1st trade (Swap). However, if you query saying give me all trades where quoteCurrency is B, we will give both 1st and 2nd because Base/Quote currency looks at both sides of the trade.
 
@@ -55,7 +58,7 @@ If you see this [query](https://ide.bitquery.io/Ethereum-Trades-for-specific-tim
 Protocols are basically rules or behavior to explain how a system will work. In the context of DEX, A DEX protocol is a set of smart contracts showing how DEX will work. When a protocol is deployed by any entity on the blockchain, it becomes an actual exchange. 
 For example, Uniswap is an exchange and a protocol. Uniswap protocol deployed by the Uniswap team created the Uniswap exchange. In the case of PancakeSwap, the exchange is PancakeSwap, but the protocol is still Uniswap.
 
-## How to check if exchange is indexed by Bitquery?
+## How to check if an exchange is indexed by Bitquery?
 
 If Bitquery index a protocol (ex - Uniswap v2 protocol), therefore any other exchange which is implemented this Uniswap V2, we have already indexed them. We might not be naming them, but you can get their trades using [**this API**](https://ide.bitquery.io/query/pzizr56shpq6wQrX), by simply replacing exchangeAddress with that exchange's factory address.
 
@@ -502,7 +505,7 @@ https://ide.bitquery.io/Trades-for-a-trading-pair-on-Ethereum
 ## Get Ethereum DEX Trades for a Liquidity Pool Contract Address
 
 To get trades for pair tokens, you should use buy/sell; in the case of using Base/Quote, it will replicate the result.
-For example, if there is a swap A <-> B, using Base/Quote, it will give two results in one A as the base currency and in another B as the quote currency.
+For example, if there is a swap A < - > B, using Base/Quote, it will give two results in one A as the base currency and in another B as the quote currency.
 
 [Open this query in IDE](https://ide.bitquery.io/Trades-for-a-pair-token-on-ethereum)
 

docs/Schema/Avalanche/address.md

@@ -68,7 +68,10 @@ query ($network: EthereumNetwork!) {
 }
 ```
 
-<details><summary>Filtering Address</summary>
+<details>
+
+<summary>Filtering Address</summary>
+
 
 `limit`: The maximum number of results to return.
 

docs/Schema/Avalanche/blocks.md

@@ -74,7 +74,10 @@ query ($network: EthereumNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Da
 
 ```
 
-<details><summary> Filtering Blocks</summary>
+<details>
+
+<summary> Filtering Blocks</summary>
+
 
 - **options** : A set of options that can be used to filter the results.
   - **desc** or **asc** : The order of the results, either "asc" (ascending) or "desc" (descending).

docs/Schema/Avalanche/transactions.md

@@ -100,7 +100,10 @@ query ($network: EthereumNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTim
 }
 ```
 
-<details><summary>Filtering Transactions</summary>
+<details>
+
+<summary>Filtering Transactions</summary>
+
 
 
 `limit`: The maximum number of results to return.

docs/Schema/Avalanche/transfers.md

@@ -88,7 +88,10 @@ query ($network: EthereumNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTim
 }
 ```
 
-<details><summary>Filtering Transfers</summary>
+<details>
+
+<summary>Filtering Transfers</summary>
+
 
 `options`: A set of options that control the behavior of the query.
 
@@ -118,6 +121,7 @@ query ($network: EthereumNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTim
 `txFrom`: The address of the sender of the transaction that the transfer was included in.
 
 `txHash`: The hash of the transaction that the transfer was included in
+
 </details>
 
 

docs/Schema/Cronos/address.md

@@ -45,6 +45,7 @@ query {
 
 <details>
 <summary>Filtering Addresses</summary>
+
 - `address`: Filter by a specific address or a list of addresses.
 
 </details>

docs/Schema/Cronos/coinpath.md

@@ -24,6 +24,7 @@ Coinpath data can be filtered using following arguments:
 - `sender`: Filter by the sender's address.
 - `time`: Filter by the time of the transaction.
 
+
 </details>
 
 The following are available fields for the `coinpath`:

docs/Schema/Cronos/references.md

@@ -29,6 +29,7 @@ References can be filtered using following arguments:
 - `txFrom`:
 - `txHash`:
 
+
 </details>
 
 - `any`: