added information about testnet

src/brain/intro.md

@@ -1,6 +1,6 @@
 # DeTEE Brain
 
-The Brain works similarly to a decentralized oracle that runs on TEEs. It has the capability to scale data distribution by leveraging [DHTs](https://en.wikipedia.org/wiki/Distributed_hash_table), and is tailored to offer a secure and redundant database for the contracts of the DeTEE network. The contracts define the relationship between user and node (resources, price of resources, [SLA](https://en.wikipedia.org/wiki/Service-level_agreement)).
+The Brain works similary to a decentralized oracle that runs on TEEs. It has the capability to scale data distribution by leveraging [DHTs](https://en.wikipedia.org/wiki/Distributed_hash_table), and is tailored to offer a secure and redundant database for the contracts of the DeTEE network. The contracts define the relationship between user and node (resources, price of resources, [SLA](https://en.wikipedia.org/wiki/Service-level_agreement)).
 
 Similar to the hacker challenge, the brain will create smart contracts on various blockchains, which will allow users to deposit tokens into the DeTEE network, and withdraw tokens from the network. The tokens that are in the network can be used for:
 - consuming resources on the network (VMs or containers)
@@ -11,4 +11,4 @@ Similar to the hacker challenge, the brain will create smart contracts on variou
   - escrow can be used to compensate for low rating, based on the free market principle
 - delegating escrow to servers and to users
 
-This component is currently under development. The high level mechanics of the brain are simulated in a centralized API, that will be used to power the testnet till the release of the decentralized brain.
+This components is currently under development. The high level mechanics of the brain are simulated in a centralized API, that will be used to power the testnet till the release of the decentralized brain.

src/cloud/access.md

@@ -17,4 +17,4 @@ Please be aware that the airdrops are awarded based on the activity, meaning bei
 
 To collect the airdrops after performing the activities above, write to us on Discord in the [📦claim-airdrops](https://discord.gg/zmR3Bzxz) channel. Summarize your activity with links (for example, links to social media posts you made about DeTEE).
 
-Once you secure an airdrop in your DeTEE wallet, you can start using the DeTEE CLI.
+Once you secured an airdrop in your DeTEE wallet, you can start using the DeTEE CLI.

src/cloud/components.md

@@ -2,7 +2,7 @@
 
 DeTEE is built of multiple components that are already under development, as follows:
 - **The Brain**: a decentralized contract manager (functioning very much like an Oracle) that runs on top of the DeTEE encryption layer
-  - [x] stores your account balance (not matter if you are a user or a node operator)
+  - [x] stores your account balanace (not matter if you are a user or a node operator)
   - [x] allows you to create contracts for VMs and containers
   - [ ] allows you to create contracts for GPUs
   - [ ] allows users to vote for the upgrades of the platform
@@ -26,18 +26,18 @@ DeTEE is built of multiple components that are already under development, as fol
   - [x] allow you to manage VMs
   - [x] allow you to manage containers
   - [x] allow you to manage containers
-  - [ ] offers warning about containers and VMs facing performance issues or decommissioning
+  - [ ] offers warning about containers and VMs facing performance issues or decomissioning
   - [ ] enables withdrawal of tokens to public blockchains
   - [ ] manage access to resources based on teams
 
 - **DeTEE Web GUI**: Will offer the same features as the CLI in a user friendly manner
 
-- **Orchestrator**: advanced cloud service that offers high availability and clustering for software services running on the DeTEE platform
+- **Orchcestrator**: advanced cloud service that offers high availability and clustering for software services running on the DeTEE platform
   - [ ] management of secrets using DeTEE encryption
   - [x] deployment of swarms of containers across multiple nodes
   - [ ] create groups of highly available VMs based on the same template
   - [ ] automatic scaling of resources based on load
-  - [ ] automatic migration of resources in case of hardware failure (or decommissioning)
+  - [ ] automatic migration of resources in case of hardware failure (or decomissioning)
   - [ ] multi-region clusters
 
 Future components (currently not under development):

src/cloud/gui.md

@@ -2,4 +2,4 @@
 
 The DeTEE GUI will be designed by taking inspiration from existing cloud platforms. Expect a user friendly experience, focused on allowing easy deployment and migration of cloud applications.
 
-At this stage, development has not started, however we are confident in the architecture from a security point of view. The GUI will allow users to deploy and attest enclaves from the browser, without the need of installing an application. Details of implementation will be disclosed at a later stage.
+At this stage, development has not started, however we are confident on the architecture from a security point of view. The GUI will allow users to deploy and attest enclaves from the browser, without the need of installing an application. Details of implementation will be disclosed at a later stage.

src/cloud/overview.md

@@ -1,7 +1,9 @@
 # DeTEE Cloud
 
-The mission of DeTEE is to create a decentralized cloud solution that functions as an open market for hardware resources. The DeTEE protocol is connecting the customers (mostly software companies) and the service providers (node operators), ensuring the business activity of all participants runs smoothly. In order to make the decentralized network feel like a cloud platform, DeTEE inspired the user experience from popular cloud platforms (Kubernetes, Openstack, AWS, GCP), and optimized and simplified the flow to the benefit of the end user.
+The mission of DeTEE is to create a decentralized cloud solution that functions as an open market for hardware resources. The DeTEE protocol is connecting the customers (mostly software companies) and the service providers (node operators), ensuring the the business activity of all participants runs smooth. In order to make the decentralized network feel like a cloud platform, DeTEE inspired the user experience from popular cloud platforms (Kubernetes, Openstack, AWS, GCP), and optimized and simplified the flow to the benefit of the end user.
 
-In order to make the environment business-friendly, guarantees regarding security and privacy must be offered by the software powering the platform. In order to achieve this, DeTEE leverages the hardware capabilities of TEEs into the core of the platform, working already with Intel SGX and AMD SEV-SNP, and planning to integrate Intel TDX, AMD Trustzone and NVIDIA H100 GPUs in the future. As we can’t be responsible for the reliability of the hardware itself, the strategy of DeTEE involves offering users the possibility to choose the hardware they work with, and to easily migrate their applications from one system to another.
+In order to make the environment business-friendly, guarantees regarding security and privacy must be offered by the software powering the platform. In order to achieve this, DeTEE leverages the hardware capabilities of TEEs into the core of the platform, working already with Intel SGX and AMD SEV-SNP, and planning to integrate Intel TDX, AMD Trustzone and NVIDIA H100 GPUs in the future. As we can't be responsible for the reliability of the hardware itself, the strategy of DeTEE envolves offering users the possibility to chose the hardware they work with, and to easily migrate their applications from one system to another.
 
 The DeTEE cloud will soon enter the testnet phase, allowing members of our community to deploy containers and VMs on the DeTEE network. The testnet does not guarantee stability (actually it guarantees disruptions, as we are actively developing the software).
+
+

src/cloud/tokens.md

@@ -3,8 +3,8 @@
 > Considering how young this project is, everything on this page will probably change in the future.
 
 The token payment and reward mechanism of DeTEE is based on the core concepts of the open market and the requirements of creating a TEE-based decentralized cloud platform:
-- nodes are free to choose their price
-- users are free to choose nodes based on their rating and price
+- nodes are free to chose their price
+- users are free to chose nodes based on their rating and price
 - nodes are free to refuse contracts (or users)
 - the cost of an enclave must be based on the amount of resources used
 - enclaves can not be migrated (they are bound to the server)
@@ -17,9 +17,9 @@ Though nodes get paid for resource reservation, during the testnet nodes will al
 
 ## Resource calculation
 
-Before calculating the price per month for a VM or a container, we must define the formula to calculate the multiplier for each hardware resource that is part of the contract. To simplify the formula, we will define “units”, each class of hardware warning units based on their own multiplier.
+Before calculating the price per month for a VM or a container, we must define the formula to calculate the the multiplier for each hardware resources that is part of the contract. To simplify the formula, we will define "units", each class of hardware awarning units based on their own multiplier.
 
-Based on our experience when using cloud services, we decided that the price of a resource will be calculated based on the number of minutes the resource is being used. As a consequence, using a resource for 10 seconds will qualify as using that resource for 1 minute, and using the resource for 70 seconds will qualify as using the resource for 2 minutes.
+Based on our experience when using cloud services, we decided that the price of a resource will be calculated based on the number of minutes the resource is being used. As a consequence, using a resource for 10 seconds will quality as using that resource for 1 minute, and using the resource for 70 seconds will quality as using the resource for 2 minutes.
 
 A server is also free to choose the price per unit per minute for his service. This price is defined in nanotokens. The current recommended value is 20k nanotokens per unit per minute. With the current calculation, a VM with 1 vCPU, 1 GB of memory, 20 GB of storage and one public IP will cost 24.4 tokens per month.
 
@@ -43,7 +43,7 @@ total_units = (vcpus * 10) + (memory_mb + 256) / 200) + (disk_gb / 10) + (public
 
 ## Price and time
 
-The node is free to choose the price for its services, expressed in nanotokens per unit. The recommended value is 20k. Please find below calculations for a price of 10k, 20k and 40k nanotokens per unit per minute.
+The node is free to chose the price for its services, expressed in nanotokens per unit. The recommended value is 20k. Please find below calculations for a price of 10k, 20k and 40k nanotokens per unit per minute.
 
 For this example, let's take into consideration 3 types of VMs:
 - a mini VM: 1 vCPUs, 1 GBs of memory and 10GBs of storage
@@ -60,4 +60,4 @@ In this table you can see the rounded price in tokens per month for the these VM
 | 20k nanoT/unit/min | ~24 T/mo  | ~105 T/mo  | ~320 T/mo | 
 | 40k nanoT/unit/min | ~47 T/mo  | ~210 T/mo  | ~641 T/mo | 
 
-As a result, a node selling 31 mini VMs for one month at a default price of 20k/unit/min will earn 730 tokens.
+As a result, a node selling 31 mini VMs for one month at default price of 20k/unit/min will earn 730 tokens.

src/cloud/using.md

@@ -6,6 +6,6 @@ Please be aware this product has been designed for:
 - Software developers
 - Cybersecurity enthusiasts
 
-Having basic understanding of operating systems, containers, virtual machines and deployment of software is required in order to use the CLI. The product was heavily inspired from existing open source cloud apps (Docker, Kubernetes, Proxmox, OpenStack).
+Having basic understand of operating systems, containers, virtual machines and deployment of software is required in order to use the CLI. The product was heavily inspired from existing open source cloud apps (Docker, Kubernetes, Proxmox, OpenStack).
 
 As we are currently in a testnet phase, you will first have to get some tokens in order to be able to test the app. Details on how to get access can be found in the next chapter.

src/operators/AMD.md

@@ -8,7 +8,7 @@ To be able to run the server on the network, it must support SEV SNP, meaning it
 - AMD EPYC 9004 (Genoa or Bergamo)
 - AMD EPYC 9005 (Turin)
 
-More information about the capabilities of each generation can be found on the [AMD website](https://www.amd.com/en/products/processors/server/epyc/infinity-guard.html). Our focus is strictly focused on the SEV-SNP capability.
+More information about the capabilities of each generation be found on the [AMD website](https://www.amd.com/en/products/processors/server/epyc/infinity-guard.html). Our focus is strictly focused on the SEV-SNP capability.
 
 The server must have a public IP.
 

src/operators/intro.md

@@ -3,7 +3,7 @@
 DeTEE currently supports Intel SGX and AMD SNP servers. In the future, we are planning to also support Arm TrustZone and NVIDIA GPUs. Our mission is to support all hardware that offers TEEs.
 
 Please be aware that this is a cloud product oriented for businesses, which has some implications:
-- You will be judged by the community based on the performance of your server.
+- You will be judget by the community based on the performance of your server.
 - Nodes must have a public IP. SNP nodes can optionally offer dedicated private IPs for VMs.
 - In production, node operators will be encouraged to offer escrow as a guarantee for users.