fix(docs): add enhancement to the FDC guides

Author: swarna1101

docs/fdc/attestation-types/json-api.mdx

@@ -1,42 +1,48 @@
 ---
 title: JsonApi
-description: An attestation request that fetches data from the given url and then edits the information with a jq transformation.
-keywords: [fdc, oracle, flare-data-connector, flare-network]
+description: An attestation type that fetches and transforms JSON data from web APIs using JQ transformations.
+keywords: [fdc, oracle, flare-data-connector, flare-network, json, api, web2]
 sidebar_position: 1
 ---
 
-An attestation request that fetches data from the given url and then edits the information with a jq transformation.
+An attestation type that enables secure data retrieval from Web2 JSON APIs with custom JQ transformations. This attestation type allows smart contracts to access and process external JSON data in a verifiable way.
+
+:::warning[Testing Networks Only]
+JsonApi attestation type is currently only available on Coston and Coston2 test networks.
+:::
 
 ## Supported sources
 
-- `WEB2`
-- test networks: `testWEB2`
+- `WEB2` (Web 2.0 JSON APIs)
+- Test networks: `testWEB2`
 
 ## Request
 
-| Field           | Solidity type | Description                                              |
-| --------------- | ------------- | -------------------------------------------------------- |
-| `url`           | `string`      | URL of the data source.                                  |
-| `postprocessJq` | `string`      | JQ filter to postprocess the json received from the url. |
-| `abi_signature` | `string`      | ABI signature of struct for encoding.                    |
+| Field           | Solidity Type | Description                                                                      |
+| --------------- | ------------- | -------------------------------------------------------------------------------- |
+| `url`           | `string`      | URL of the JSON API endpoint to query.                                           |
+| `postprocessJq` | `string`      | JQ filter expression to transform the retrieved JSON data.                       |
+| `abi_signature` | `string`      | ABI signature defining the struct format for encoding the transformed JSON data. |
 
 ## Response
 
-| Field              | Solidity type | Description       |
-| ------------------ | ------------- | ----------------- |
-| `abi_encoded_data` | `bytes`       | ABI encoded data. |
-
-## Lowest Used Timestamp
+| Field              | Solidity Type | Description                                      |
+| ------------------ | ------------- | ------------------------------------------------ |
+| `abi_encoded_data` | `bytes`       | ABI-encoded data result after JQ transformation. |
 
-For `lowestUsedTimestamp`, `0xffffffffffffffff` ($2^{64}-1$ in hex) is used.
+## Verification Process
 
-## Verification process
+1. The attestation service performs a GET request to the specified `url`.
 
-Query the URL with GET method.
-If the query is unsuccessful or does not return a json, reject the request.
+   - If the request fails or returns non-JSON data, the attestation request is rejected.
+   - The service validates that the response is valid JSON data.
 
-Apply the jq filter specified in the request to the received json.
+2. The specified `postprocessJq` filter is applied to the retrieved JSON:
 
-ABI encode the filtered json with the abi_signature provided in the request and return it as abi_encoded_data.
+   - The JQ filter must be a valid JQ expression.
+   - The filter's output must match the structure defined in `abi_signature`.
+   - If the JQ transformation fails, the attestation request is rejected.
 
-`LowestUsedTimestamp` is unlimited.
+3. The transformed data is ABI-encoded according to the provided `abi_signature`:
+   - The encoding must match the Solidity ABI specification.
+   - The encoded bytes are returned in `abi_encoded_data`.