fix links

Author: badgersrus

README.md

@@ -5,13 +5,13 @@ Documentation for TEN Protocol, built with [Docusaurus 2](https://docusaurus.io/
 ### Installation
 
 ```
-$ yarn
+$ npm install
 ```
 
 ### Local Development
 
 ```
-$ yarn start
+$ npm run serve
 ```
 
 This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

docs/3-smart-contract-features/1-data-access.md

@@ -23,7 +23,7 @@ To achieve this, we had to:
 Here, we'll list the platform rules. The examples below will showcase how exactly to use these rules in practice.
 
 - Any contract can be configured to be "transparent" or "private". By default, it is "private", which means the internal storage is not accessible. "Transparent" contracts behave exactly like Ethereum.
-- Any RPC call accessing data like: `eth_call`, `eth_estimateGas`, `eth_getTransactionReceipt`, `eth_logs`, must be signed by a [viewing key (VK)](./4-smart-contracts.md). The VK itself must be signed by the main account. (Note that this is behind the scenes.)
+- Any RPC call accessing data like: `eth_call`, `eth_estimateGas`, `eth_getTransactionReceipt`, `eth_logs`, must be signed by a [viewing key (VK)](../4-write-ten-dapp/1-high-level-concepts.md#ten-gateway). The VK itself must be signed by the main account. (Note that this is behind the scenes.)
 - Event log visibility is configurable. Each event log can be visible to one or multiple of the topics (indexed fields), and the sender of the transaction, only if the topic is the `address` of an "Externally owned Account" (EOA). The event log can also be configured to be "public" - visible to everyone.
 - When there is no configuration, the default event log visibility is:
   - Rule 1: Event logs that contain EOAs as topics are only visible to those EOAs.

docs/4-write-ten-dapp/1-high-level-concepts.md

@@ -8,7 +8,7 @@ Below are the core concepts that make TEN unique while maintaining complete comp
 
 ## End-to-End Encryption
 
-All contract execution runs inside TEEs; inputs, state, and (optionally) logs can be private. See the [Overview](../1-overview/overview.md) for architecture and threat model.
+All contract execution runs inside TEEs; inputs, state, and (optionally) logs can be private. See the [Overview](../1-overview.md) for architecture and threat model.
 
 Clients establish HTTPS connections that terminate inside TEEs via the TEN Gateway, preventing plaintext exposure on intermediaries; smart contracts then execute entirely within the enclave boundary, and contract state plus sensitive metadata are stored encrypted at rest, with read access enforced through Viewing Keys and policy logic.
 
@@ -30,7 +30,7 @@ Web service running in TEEs that provides the secure edge for dApps and user wal
 - Manages Session Keys to enable no-click UX under developer-defined policies
 - Caches encrypted metadata and frequently accessed data for performance and availability
 
-See [TEN Gateway](./9-testnet.md#ten-gateway) for more information.
+See [TEN Gateway](./6-testnetmd#ten-gateway) for more information.
 
 ## Personal Data
 

docs/4-write-ten-dapp/2-setup-dev-env.md

@@ -11,8 +11,8 @@ To start building on TEN, you first need to set up and configure your wallet wit
 2. **Configure MetaMask for TEN**:
    - Visit the [TEN Gateway](https://gateway.ten.xyz/) for wallet setup.
    - Click on “Connect to TEN Testnet” and follow the on-screen instructions.
-   - Learn more about the [TEN Gateway](/docs/tools-infrastructure/hosted-gateway).
-3. **Acquire Testnet ETH Tokens**: To perform transactions, you'll need testnet ETH tokens. Refer to our [Getting tokens](/docs/getting-started/for-users/get-tokens).
+   - Learn more about the [TEN Gateway](../4-write-ten-dapp/1-high-level-concepts.md#ten-gateway).
+3. **Acquire Testnet ETH Tokens**: To perform transactions, you'll need testnet ETH tokens. Refer to our [Getting tokens](../4-write-ten-dapp/6-testnet.md#requesting-testnet-eth).
 
 ### Supported Wallets
 
@@ -24,7 +24,7 @@ These wallets are confirmed to work smoothly with the TEN Gateway:
 
 Once your wallet is ready, you can proceed with the development and deployment of your smart contracts.
 
-1. **Choose an IDE**: Use your preferred development environment or Integrated Development Environment (IDE) like Truffle, Remix, Hardhat, or Foundry. Check out IDE compatibility and its features [here](/docs/tools-infrastructure/compatible-tools).
+1. **Choose an IDE**: Use your preferred development environment or Integrated Development Environment (IDE) like Truffle, Remix, Hardhat, or Foundry.
 2. **Connect IDE to MetaMask**: Ensure your chosen IDE is connected to your MetaMask wallet.
 
 ## 3. Docker Configuration