fix(docs): add JsonApi and remove the guides

Author: swarna1101

docs/fdc/1-overview.mdx

@@ -62,8 +62,7 @@ FDC currently supports seven attestation types, each serving specific verificati
 
 - **AddressValidity**: Validates the format and checksum of addresses on specified chains.
 - **EVMTransaction**: Verifies and retrieves transaction details from EVM-compatible chains (`ETH`, `FLR`, `SGB`).
-- **JsonApi**:
-  {/* TODO */}
+- **JsonApi**: Fetches and processes any Web2 data using a JQ transformation, then returns it as ABI-encoded output. (Currently only on Coston & Coston2).
 - **Payment**: Confirms and fetches payment transaction details from non-EVM chains (`BTC`, `DOGE`, `XRP`).
 - **ConfirmedBlockHeightExists**: Verifies block existence and confirmation status.
 - **BalanceDecreasingTransaction**: Validates if a transaction reduces an address's balance.

docs/fdc/guides/evm-connectivity.mdx

@@ -9,7 +9,7 @@ sidebar_position: 8
 unlisted: true
 ---
 
-In [Part 1](quickstart-guide) and [Part 2](/fdc/attestation-types) of the series, you you have learned how the Data Connector works and what kind of different attestations you can get from it. In this guide, you will:
+In [Part 1](/fdc/getting-started) and [Part 2](/fdc/attestation-types) of the series, you you have learned how the Data Connector works and what kind of different attestations you can get from it. In this guide, you will:
 
 - Move from the world of UTXO chains to the world of EVM chains with a new `EVMTransaction` attestation type.
 - Understand the implications of connecting account-based chains, and the additional possibilities that smart contracts bring.