Main

.github/workflows/build-manual.yml

@@ -53,7 +53,7 @@ jobs:
             type=raw,value=${{ env.REPO_NAME }}-${{ github.ref_name }}-build-${{ github.run_id }}
 
       - name: "Build and push Docker image"
-        uses: docker/build-push-action@v4
+        uses: docker/build-push-action@v6
         with:
           context: .
           tags: ${{ steps.meta.outputs.tags }}

.github/workflows/docker-image.yml

@@ -19,18 +19,18 @@ jobs:
 
     steps:
       - name: Checkout repository
-        uses: actions/checkout@v2
+        uses: actions/checkout@v4
 
       - name: Log in to the Container registry
-        uses: docker/login-action@f054a8b539a109f9f41c372932f1ae047eff08c9
+        uses: docker/login-action@v3
         with:
           registry: ${{ env.REGISTRY }}
           username: ${{ github.actor }}
           password: ${{ secrets.GITHUB_TOKEN }}
 
       - name: Extract metadata (tags, labels) for Docker
         id: meta
-        uses: docker/metadata-action@98669ae865ea3cffbcbaa878cf57c20bbf1c6c38
+        uses: docker/metadata-action@v5
         with:
           images: ${{ env.REGISTRY }}/${{ env.IMAGE_NAME }}
           tags: |
@@ -42,7 +42,7 @@ jobs:
             type=raw,value=build-${{ github.run_id }}
 
       - name: Build and push Docker image
-        uses: docker/build-push-action@ad44023a93711e3deb337508980b4b5e9bcdc5dc
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true

docs/fundamentals/certification.md

@@ -5,13 +5,13 @@ slug: "/certification"
 sidebar_position: 6
 ---
 
-Super Protocol uses a certification system for signing data, verifying signatures, and ensuring applications operate within a trusted confidential computing environment. Verified data is published on the blockchain on behalf of confidential containers, allowing anyone to validate application integrity and ensure confidentiality. End users only interact with issued certificates and verify signatures, while the complexities of Remote Attestation are seamlessly managed in the background.
+Super Protocol uses a certification system for signing data, verifying signatures, and ensuring applications operate within a trusted <a id="tee"><span className="dashed-underline">confidential computing environment</span></a>. Verified data is published on the blockchain on behalf of confidential containers, allowing anyone to validate application integrity and ensure confidentiality. End users only interact with issued certificates and verify signatures, while the complexities of Remote Attestation are seamlessly managed in the background.
 
 All the system components are open-source, ensuring transparency and verifiability.
 
 ## Architecture
 
-The backbone of the system is a hierarchical structure of Certification Authorities operating inside Trusted Execution Environments (TEE)—Intel SGX enclaves.
+The backbone of the system is a hierarchical structure of <a id="ca"><span className="dashed-underline">Certification Authorities</span></a> operating inside Trusted Execution Environments (TEE)—Intel SGX enclaves.
 
 <img src={require('./images/certification-system-architecture.png').default} width="auto" height="auto"/>
 <br/>
@@ -43,9 +43,9 @@ The Workload Info includes an array called `runtimeInfo[]` with metadata about s
 
 The hash of the Workload Info is included in the order certificate.
 
-The system generates and publishes a report in the blockchain, allowing anyone to validate the order. The order report includes:
+Trusted Loader generates and publishes a report in the blockchain, allowing anyone to validate the order. This order report includes:
 
 - The public components of all the certificates in the chain
 - Workload Info:
     + Order creation date
-    + `runtimeInfo[]`
+    + The `runtimeInfo[]` array

docs/fundamentals/index.md

@@ -5,23 +5,24 @@ slug: "/"
 sidebar_position: 1
 ---
 
+import { Tooltip } from 'react-tooltip';
+
 This section describes the most essential concepts of Super Protocol.
 
 ## Marketplace
 
-Governed by smart contracts, the Super Protocol Marketplace is a distributed blockchain-based ecosystem that connects the sellers and the buyers of digital products and services. It consists of the following:
+Super Protocol Marketplace is a distributed blockchain-based ecosystem governed by smart contracts. It connects the sellers and buyers of digital products and services:
 
-- Providers of solutions, data, storage, and compute resources.
-- Offers that providers create.
-- Customers who rent the offers and pay for the usage.
+- Providers who offer solutions, data, and compute resources.
+- Customers who lease the offers and pay for the usage.
 
-Users who register a provider create offers to share and monetize their solutions, scripts, datasets, AI models, libraries, frameworks, etc. Currently, only Super Protocol provides compute and storage resources. In future releases, users will receive this functionality as well. Read more about [offers and providers](/fundamentals/offers).
+Providers create offers to share and monetize their compute resources as well as solutions, scripts, datasets, AI models, libraries, frameworks, etc. Read more about [offers and providers](/fundamentals/offers).
 
 Customers place orders by adding offers and paying for them according to the prices set by the providers of these offers. To learn more about orders, order statuses, pricing, and possible usage scenarios, refer to the [documentation](/fundamentals/orders).
 
 The Super Protocol Marketplace is accessible via one of the following:
 
-- The command-line interface (CLI) using a special utility called SPCTL.
+- The command-line interface (CLI) using a utility called SPCTL.
 - The graphical user interface (GUI) using a browser-based [web application](https://marketplace.superprotocol.com/).
 
 ## Trusted Execution Environment

docs/marketplace/all-orders/index.md

@@ -13,15 +13,15 @@ This screens displays the full list of the orders you placed on Super Protocol.
 
 The table in the center of the screen provides essential information about your orders:
 
-- **Created Date**: the date and time when the customer placed the order.
-- **Modified Date**: the date and time of the latest change in the order status.
-- **Order ID**: a unique order identification number. It is incremental and continuous for all orders and suborders on Super Protocol.
-- **Status**: current status of the order. Read about [statuses](/fundamentals/orders#order-status).
-- **Cost to Date**: the total amount of SPPI tokens spent on the order so far.
-- **Balance**: the remaining order balance. When it reaches zero, the order processing stops. To replenish the balance, open the **Order** screen and click the **Extend Lease** button.
-- **Engine**: the AI engine that launches the model in the order.
-- **Model**: the main model used in the order.
-- **Datasets**: the main dataset used in the order. Note that there may be several datasets in the order.
+- **Created Date**: The date and time when the customer placed the order.
+- **Modified Date**: The date and time of the latest change in the order status.
+- **Order ID**: A unique order identification number. It is incremental and continuous for all orders and suborders on Super Protocol.
+- **Status**: Current status of the order. Read about [statuses](/fundamentals/orders#order-status).
+- **Cost to Date**: The total amount of SPPI tokens spent on the order so far.
+- **Balance**: The remaining order balance. When it reaches zero, the order processing stops. To replenish the balance, open the **Order** screen and click the **Extend Lease** button.
+- **Engine**: A solution necessary to deploy the model and provides a user interface.
+- **Model**: The main model used in the order.
+- **Datasets**: The main dataset used in the order. Support for datasets will be added in future releases.
 
 Clicking an order opens its [**Order**](/marketplace/all-orders/order) screen with detailed information.
 

docs/marketplace/confidentiality.md

@@ -37,13 +37,13 @@ The Tunnel Client signs the fingerprint of the domain SSL/TLS certificate with t
 
 You can compare the certificate fingerprint with the expected fingerprint, preventing possible man-in-the-middle attacks.
 
-The Check Confidentiality service displays the expected SSL/TLS certificate signature:
+The Check Confidentiality service displays the expected SSL/TLS certificate fingerprint:
 
 <img src={require('./images/check-confidentiality-fingerprint.png').default} width="auto" height="auto" border="1"/>
 <br/>
 <br/>
 
-To compare the expected SSL/TLS certificate signature with the domain SSL/TLS certificate signature, find the latter in your web browser:
+Find the domain SSL/TLS certificate fingerprint in your web browser to compare it with the expected fingerprint provided by the Check Confidentiality service:
 
 <img src={require('./images/check-confidentiality-connection-1.png').default} width="auto" height="auto" border="1"/>
 <br/>

docs/marketplace/guides/deploy-model.md

@@ -0,0 +1,6 @@
+---
+id: "deploy-model"
+title: "Deploy Your Model"
+slug: "/guides/deploy-model"
+sidebar_position: 4
+---

docs/marketplace/guides/index.md

@@ -8,7 +8,5 @@ sidebar_position: 2
 | **Guide** | **Description** |
 | :- | :- |
 | [Log In as a Web3 user](/marketplace/guides/log-in) | Log in as a Web3 user and set up the account. |
-| [Upload a Model (TGWUI)](/marketplace/guides/upload-tgwui) | Prepare and upload a model supported by Text Generation Web UI. |
-| [Upload a Model (ComfyUI)](/marketplace/guides/upload-comfyui) | Prepare and upload a model supported by ComfyUI. |
 | [Set Up Storage](/marketplace/guides/storage) | Set up your personal storage as a Web3 user. |
 | [Troubleshooting](/marketplace/guides/troubleshooting) | Fix the most common issues. |

docs/marketplace/guides/publish-offer.md

@@ -0,0 +1,6 @@
+---
+id: "publish-offer"
+title: "Publish an Offer"
+slug: "/guides/publish-offer"
+sidebar_position: 5
+---