Remove Validate command

docs/build/manifest/algorand.md

@@ -292,7 +292,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/arbitrum.md

@@ -338,7 +338,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/avalanche.md

@@ -345,7 +345,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/bsc.md

@@ -336,7 +336,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/cosmos.md

@@ -389,7 +389,3 @@ Some Cosmos chains, like Juno, have hard forks that intentionally skip blocks. T
 5. Continue indexing
 
 :::
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/ethereum.md

@@ -332,7 +332,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/flare.md

@@ -241,7 +241,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/gnosis.md

@@ -347,7 +347,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/near.md

@@ -348,7 +348,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/optimism.md

@@ -344,7 +344,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/polkadot.md

@@ -456,7 +456,3 @@ Here is a list of supported custom datasources:
 | Kind                                         | Supported Handlers                                                                                                               | Filters                         | Description                                                                                                                                           |
 | -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
 | [substrate/FrontierEvm](../substrate-evm.md) | [substrate/FrontierEvmEvent](../substrate-evm.md#event-handlers), [substrate/FrontierEvmCall](../substrate-evm.md#call-handlers) | See filters under each handlers | Provides easy interaction with EVM transactions and events on the Frontier EVM (widely used across Polkadot including in Moonbeam and Astar networks) |
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/polygon.md

@@ -337,7 +337,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.

docs/build/manifest/stellar.md

@@ -345,7 +345,3 @@ When declaring a `range` use an string in the format of `"start - end"`. Both st
   }
 }
 ```
-
-## Validating
-
-You can validate your project manifest by running `subql validate`. This will check that it has the correct structure, valid values where possible and provide useful feedback as to where any fixes should be made.