settlemint · bl0up · Mar 28, 2025 · Mar 28, 2025 · sourcery-ai · Mar 28, 2025
diff --git a/content/docs/blockchain-and-ai/ai-code-assistant.mdx b/content/docs/blockchain-and-ai/ai-code-assistant.mdx
diff --git a/content/docs/building-with-settlemint/evm-chains-guide/integration-studio.mdx b/content/docs/building-with-settlemint/evm-chains-guide/integration-studio.mdx
@@ -58,7 +58,7 @@ minutes—providing API endpoints that are automatically hosted and secured by
 SettleMint infrastructure.
 <br> </br>
 Developers can configure API Keys to restrict access to these endpoints and
-monitor calls using the platform’s access token management system. Every
+monitor calls using the platform's access token management system. Every
 endpoint is served over HTTPS and can be integrated with frontend dApps, backend
 services, or third-party platforms.
 <br> </br>
@@ -136,7 +136,7 @@ recognizable in your dashboards (eg. Crowdsale Flow)
 
 Choose a deployment plan. Select the type, cloud provider, region and resource
 pack.
-[More about deployment plans](/launching-the-platform/managed-cloud-deployment/deployment-plans)
+[More about deployment plans](/launching-the-platform/managed-cloud-saas/deployment-plans)
 
 ### Confirm setup
 
@@ -169,7 +169,7 @@ Before we show you how to set up your own flow, we recommend reading this
 Now let's set up an example flow together and build an endpoint to get the
 latest block number of the Polygon Mumbai Testnet using the Integration Studio.
 If you do not have a Polygon Mumbai Node, you can easily
-[deploy a node](/platfrom-components/add-a-node-to-a-network) first.
+[deploy a node](/platform-components/blockchain-infrastructure/blockchain-nodes) first.
 
 <Steps>
 ### Add http input node
@@ -191,7 +191,7 @@ Under the **Connect tab** of your Polygon Mumbai node, you will find its RPC url
 
 `accessToken` - You will need an access token for your application. If you do
 not have one, you can easily
-[create an access token](/platfrom-components/application-access-tokens) first.
+[create an access token](/platform-components/security-and-authentication/application-access-tokens) first.
 
 </Callout>
 

diff --git a/content/docs/index.mdx b/content/docs/index.mdx
@@ -266,14 +266,7 @@ import Link from "next/link";
           Deploy Chain Code
         </Link>
       </td>
-      <td className="py-2 pl-3 text-slate-800 dark:text-slate-200">
-        <Link
-          href="/building-with-settlemint/hyperledger-fabric-guide/setup-api-portal"
-          className="no-underline text-sm-accent hover:underline"
-        >
-          Setup API Portal
-        </Link>
-      </td>
+
     </tr>
     <tr className="align-top">
       <td className="py-2 pl-3 text-slate-800 dark:text-slate-200">
@@ -397,15 +390,15 @@ import Link from "next/link";
     <tr className="align-top">
       <td className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/blockchain-infrastructure/health-monitoring-tools"
+          href="/platform-components/usage-and-logs/monitoring-tools"
           className="no-underline text-sm-accent hover:underline"
         >
           Health Monitoring Tools
         </Link>
       </td>
       <td colSpan="2" className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/blockchain-infrastructure/resource-usage"
+          href="/platform-components/usage-and-logs/resource-usage"
           className="no-underline text-sm-accent hover:underline"
         >
           Resource Usage
@@ -507,10 +500,10 @@ import Link from "next/link";
       </td>
       <td colSpan="2" className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/middleware-and-api-layer/integration-studio"
+          href="/platform-components/middleware-and-api-layer/fabconnect"
           className="no-underline text-sm-accent hover:underline"
         >
-          Integration Studio
+          Setup API Portal
         </Link>
       </td>
     </tr>
@@ -557,23 +550,23 @@ import Link from "next/link";
     <tr className="align-top">
       <td className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/seecurity-and-authentication/private-keys"
+          href="/platform-components/security-and-authentication/private-keys"
           className="no-underline text-sm-accent hover:underline"
         >
           Private Keys
         </Link>
       </td>
       <td className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/seecurity-and-authentication/user-wallets"
+          href="/platform-components/security-and-authentication/user-wallets"
           className="no-underline text-sm-accent hover:underline"
         >
           User Wallets
         </Link>
       </td>
       <td className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/seecurity-and-authentication/personal-access-tokens"
+          href="/platform-components/security-and-authentication/personal-access-tokens"
           className="no-underline text-sm-accent hover:underline"
         >
           Personal Access Tokens
@@ -583,7 +576,7 @@ import Link from "next/link";
     <tr className="align-top">
       <td colSpan="3" className="py-2 pl-3 text-slate-800 dark:text-slate-200">
         <Link
-          href="/platform-components/seecurity-and-authentication/application-access-tokens"
+          href="/platform-components/security-and-authentication/application-access-tokens"
           className="no-underline text-sm-accent hover:underline"
         >
           Application Access Tokens

diff --git a/content/docs/launching-the-platform/managed-cloud-saas/deployment-plans.mdx b/content/docs/launching-the-platform/managed-cloud-saas/deployment-plans.mdx
@@ -146,7 +146,7 @@ choice, and easily build cross-cloud provider and cross-geographical region
 networks. All leading cloud providers are supported and we are continously
 working on adding support for more regions.
 
-[Discover all supported cloud providers and available regions](/launching-the-platform/managed-cloud-deployment/supported-cloud-providers)
+[Discover all supported cloud providers and available regions](/launching-the-platform/managed-cloud-saas/supported-cloud-providers)
 
 ## Resource pack
 

diff --git a/content/docs/launching-the-platform/self-hosted-onprem/introduction.mdx b/content/docs/launching-the-platform/self-hosted-onprem/introduction.mdx
@@ -36,7 +36,7 @@ below to learn more:
     - Network and storage specifications
     - Access and security requirements
 
-    👉 [View Requirements Guide](/launching-the-platform/self-hosted/infrastructure-requirements)
+    👉 [View Requirements Guide](/launching-the-platform/self-hosted-onprem/infrastructure-requirements)
 
   </Tab>
 
@@ -50,7 +50,7 @@ below to learn more:
     - Configuration requirements
     - Information collection checklists
 
-    👉 [View Prerequisites Guide](/launching-the-platform/self-hosted/installation-guide/prerequisites/overview)
+    👉 [View Prerequisites Guide](/launching-the-platform/self-hosted-onprem/prerequisites/overview)
 
   </Tab>
 
@@ -63,7 +63,7 @@ below to learn more:
     - Flexible configuration options
     - Production-ready setup
 
-    👉 [View Installation Guide](/launching-the-platform/self-hosted/installation-guide/platform-installation)
+    👉 [View Installation Guide](/launching-the-platform/self-hosted-onprem/platform-installation)
 
   </Tab>
 </Tabs>
@@ -181,7 +181,7 @@ prerequisite setup.
   **Next Step**
 
 Start by reviewing the
-[Infrastructure Requirements](/launching-the-platform/self-hosted/infrastructure-requirements)
+[Infrastructure Requirements](/launching-the-platform/self-hosted-onprem/infrastructure-requirements)
 to ensure your environment meets all necessary specifications.
 
 </Callout>
diff --git a/content/docs/launching-the-platform/self-hosted-onprem/prerequisites/overview.mdx b/content/docs/launching-the-platform/self-hosted-onprem/prerequisites/overview.mdx
@@ -39,18 +39,18 @@ collect the necessary information for installation.
     ### Ingress Controller
     - Traffic management and load balancing
     - SSL/TLS termination
-    - [Setup Guide](/launching-the-platform/self-hosted/prerequisites/ingress-controller)
+    - [Setup Guide](/launching-the-platform/self-hosted-onprem/prerequisites/ingress-controller)
 
     ### Domain and TLS
     - Domain name configuration
     - SSL/TLS certificates
-    - [Setup Guide](/launching-the-platform/self-hosted/prerequisites/domain-and-tls)
+    - [Setup Guide](/launching-the-platform/self-hosted-onprem/prerequisites/domain-and-tls)
 
     ### Metrics and Logs
     - Prometheus metrics collection
     - Grafana visualization
     - Loki log aggregation
-    - [Setup Guide](/launching-the-platform/self-hosted/prerequisites/metrics-and-logs)
+    - [Setup Guide](/launching-the-platform/self-hosted-onprem/prerequisites/metrics-and-logs)
 
   </Tab>
 
@@ -139,12 +139,12 @@ required for the platform installation.
 ## Next steps
 
 1. Start with the
-   [Ingress Controller](/launching-the-platform/self-hosted/prerequisites/ingress-controller)
+   [Ingress Controller](/launching-the-platform/self-hosted-onprem/prerequisites/ingress-controller)
    setup
 2. Follow each prerequisite guide in order
 3. Validate your configurations
 4. Proceed to
-   [Platform Installation](/launching-the-platform/self-hosted/platform-installation)
+   [Platform Installation](/launching-the-platform/self-hosted-onprem/platform-installation)
 
 ## Need help?
 

diff --git a/content/docs/platform-components/database-and-storage/s3-storage.mdx b/content/docs/platform-components/database-and-storage/s3-storage.mdx
@@ -937,6 +937,4 @@ across all storage operations.
 - **[MinIO Official Documentation](https://docs.min.io/)**
 - **[MiniO S3 API Reference](https://docs.aws.amazon.com/AmazonS3/latest/API/Welcome.html)**
 - **[MinIO GitHub Repository](https://github.com/minio/minio)**
-- **[Storage Best Practices](https://min.io/docs/minio/)**
-
 ---
diff --git a/content/docs/platform-components/dev-tools/ai-code-assistant.mdx b/content/docs/platform-components/dev-tools/ai-code-assistant.mdx
@@ -36,8 +36,7 @@ your task for better results.
   your files grow or you switch between different parts of your project.
 - Extensibility via MCP: RooCode supports the Model Context Protocol (MCP) , a
   framework that lets the AI assistant use external tools and services,
-  including the (SettleMint MCP
-  server)[https://console.settlemint.com/documentation/platfrom-components/dev-tools/mcp].
+  including the [SettleMint MCP server](/platform-components/dev-tools/mcp).
   This is a big enhancement for Code Studio – it means the AI can potentially
   perform complex operations like looking up information in a knowledge base,
   running test suites, or controlling a web browser for web-related tasks, all

diff --git a/content/docs/platform-components/dev-tools/code-studio.mdx b/content/docs/platform-components/dev-tools/code-studio.mdx
@@ -17,7 +17,7 @@ build your dApp.
 
 Currently, we offer the following types of Code Studio:
 
-- [Smart contract sets](/platfrom-components/dev-tools/code-studio/code-studio) -
+- [Smart contract sets](/platform-components/dev-tools/code-studio#solidity-contracts-ide) -
   A powerful tool that accelerates the development of your smart contracts. This
   code studio comes with pre-built smart contract set templates for your chosen
   use case, which are easily customizable to match your needs. It also includes
@@ -27,13 +27,13 @@ Currently, we offer the following types of Code Studio:
 ![Smart Contract IDE](../../../img/platfrom-components/code-studio-ide.png)
 
 A Smart Contract Set is a
-[code studio](/platfrom-components/dev-tools/code-studio/code-studio) that comes
-with a [smart contract set template](./smart-contract-templates) for your chosen
+[code studio](/platform-components/dev-tools/code-studio) that comes
+with a [smart contract set template](/platform-components/dev-tools/code-studio#template-library) for your chosen
 use case. It is a powerful tool that accelerates the development of your smart
 contracts.
 
 You can choose from a wide variety of templates in our open-source
-[template library](smart-contract-templates). Each template includes pre-built
+[template library](/platform-components/dev-tools/code-studio#template-library). Each template includes pre-built
 smart contracts which you can then customize to meet your specific needs.
 
 ![Smart Contract Template](../../../img/platfrom-components/add-smart-contract-set.png)
@@ -59,7 +59,7 @@ at SettleMint.
 - **Picking Your Template**: Pick the template of your choice.
 
 For detailed instructions, please see
-[add a smart contract set](add-smart-contract-set).
+[add a smart contract set](/platform-components/dev-tools/code-studio#adding-a-smart-contract-set).
 
 ### 2. Compiling and configuring the smart contract
 

diff --git a/content/docs/platform-components/middleware-and-api-layer/attestation-indexer.mdx b/content/docs/platform-components/middleware-and-api-layer/attestation-indexer.mdx
@@ -123,7 +123,7 @@ project.
 4. **Save**: Save the configuration.
 
 For detailed instructions, visit the
-[Smart Contract Sets Documentation](/platfrom-components/dev-tools/code-studio/smart-contract-sets/smart-contract-sets).
+[Smart Contract Sets Documentation](/platform-components/dev-tools/code-studio).
 
 ---
 

diff --git a/...docs/platform-components/middleware-and-api-layer/smart-contract-api-portal.mdx b/...docs/platform-components/middleware-and-api-layer/smart-contract-api-portal.mdx
@@ -66,7 +66,7 @@ contract, including their names, input parameters, and output types.
 
 When deploying a smart contract the ABI file can be found as part of the
 artificats. See
-[Deploying the Smart Contract](/developer-guides/connect-frontend#adding-the-abi).
+[Deploying the Smart Contract](/building-with-settlemint/evm-chains-guide/deploy-smart-contracts).
 Download the ABI json files and save them on your local filesystem.
 
 When creating a new middleware you'll need to upload at least one ABI.
@@ -159,10 +159,10 @@ async function webhookConsumerBootstrap(secret: string) {
 
 ## Further reading
 
-- [The Graph Middleware](#the-graph-middleware)
-- [The Smart Contract Portal Middleware](#the-smart-contract-portal-middleware)
-- [Attestation Indexer](#attestation-indexer)
-- [Firefly FabConnect](#firefly-fabconnect)
+- [The Graph Middleware](/platform-components/middleware-and-api-layer/graph-middleware)
+- [The Smart Contract Portal Middleware](/platform-components/middleware-and-api-layer/smart-contract-api-portal)
+- [Attestation Indexer](/platform-components/middleware-and-api-layer/attestation-indexer)
+- [Firefly FabConnect](/platform-components/middleware-and-api-layer/fabconnect)
 
 <Callout type="info">
   All operations require appropriate permissions in your workspace.

diff --git a/content/docs/platform-components/platform-info/connect-external-network.mdx b/content/docs/platform-components/platform-info/connect-external-network.mdx
@@ -17,7 +17,7 @@ resource scaling, an intuitive JSON-RPC UI, and reliable uptime management.
 ## Joining a Network
 
 1. Navigate to the create network form (see
-   [how to do this here](/building-with-settlemint/add-a-network-to-an-application)).
+   [how to do this here](/building-with-settlemint/evm-chains-guide/add-network-and-nodes)).
 2. Select **Join permissioned network**.
 3. Choose **Hyperledger Besu** or **Quorum** depending on the network you want
    to join.
@@ -28,7 +28,7 @@ resource scaling, an intuitive JSON-RPC UI, and reliable uptime management.
    If a bootnode is specified in the genesis file, it will be added
    automatically as an external node, allowing you to skip this step.
 7. Choose the deployment plan for the node. For more information about
-   deployment plans, [see here](/building-with-settlemint/deployment-plans).
+   deployment plans, [see here](/launching-the-platform/managed-cloud-saas/deployment-plans).
 
 This process will create a new non-validator node in your existing network.
 

diff --git a/...docs/platform-components/security-and-authentication/personal-access-tokens.mdx b/...docs/platform-components/security-and-authentication/personal-access-tokens.mdx
@@ -11,7 +11,7 @@ import { Card } from "fumadocs-ui/components/card";
 # Personal access tokens
 
 Personal access tokens (or
-[Application access tokens](/platfrom-components/application-access-tokens)) let
+[Application access tokens](/platform-components/security-and-authentication/application-access-tokens)) let
 you connect your SettleMint services with other apps securely. They represent an
 individual user, and have the same rights as the user's role in the organization
 (admin or user). They can be used to connect to all services that the user has

diff --git a/content/docs/supported-blockchains/L2-public-networks/meta.json b/content/docs/supported-blockchains/L2-public-networks/meta.json
@@ -1,5 +1,5 @@
 {
   "label": "L2 Public Networks",
   "title": "L2 Public Networks",
-  "pages": ["polygon", "polygon-zkevm", "optimism", "soneium"]
+  "pages": ["polygon", "polygon-zkevm", "optimism", "soneium","arbitrum"]
 }
diff --git a/content/docs/use-case-guides/attestation-service.mdx b/content/docs/use-case-guides/attestation-service.mdx
@@ -123,7 +123,7 @@ project.
 4. **Save**: Save the configuration.
 
 For detailed instructions, visit the
-[Smart Contract Sets Documentation](/building-with-settlemint/dev-tools/code-studio/smart-contract-sets/smart-contract-sets).
+[Smart Contract Sets Documentation](/platform-components/dev-tools/code-studio).
 
 ---