Replace API FAQ with design goals section (#20)

* Replace API FAQ with design goals section

* Remove extra words

src/SUMMARY.md

@@ -32,7 +32,6 @@
     - [Sourcify](./config/options/sourcify.md)
 - [User guide]()
 - [API Spec](./api-docs/README.md)
-  - [FAQ](./api-docs/faq.md)
   - [ots namespace spec](./api-docs/ots-api.md)
   - [ots2 EXPERIMENTAL namespace spec](./api-docs/ots2-api.md)
 - [Contract verification](./contract-verification/README.md)

src/api-docs/README.md

@@ -2,9 +2,7 @@
 
 > This chapter only makes sense if you intend to dive deep into Otterscan source code or want to integrate directly with the Otterscan APIs.
 
-First, some context about why we chose the approach of implementing a custom API directly inside Ethereum clients.
-
-- [FAQ](./faq.md)
+## Specification
 
 There is an ongoing effort to formalize the Otterscan API spec in the same format as the standard JSON-RPC APIs.
 
@@ -18,3 +16,7 @@ A more detailed explanation of the `ots` namespace:
 There is an experimental `ots2` namespace, which is likely to change, but here is an overview:
 
 - [ots2 namespace spec](./ots2-api.md)
+
+## Design Goals
+
+Otterscan's RPC namespaces aim to provide a minimalistic solution for Ethereum data access which overcomes the limitations of the standard JSON-RPC API. Implementing features directly in-node eliminates the need for additional indexer middleware, databases, or dependencies. Our design prioritizes simplicity and flexibility over high-performance scalability.