docs: add suggestions from notion (#574)

JuArce · entropidelic · glpecile · web-flow · commit 42be6edb8538 · 2024-07-05T15:39:03.000-03:00
Co-authored-by: Mariano A. Nicolini &lt;mariano.nicolini.91@gmail.com&gt;
Co-authored-by: Gian &lt;58370608+glpecile@users.noreply.github.com&gt;
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
@@ -4,7 +4,7 @@
 
 * [About Aligned](introduction/0_about_aligned.md)
 * [Getting started](introduction/1_getting_started.md)
-* [Core concepts](introduction/2_core_concepts.md)
+* [Key Terms](introduction/2_key_terms)
 * [Use cases](introduction/3_use_cases.md)
 * [FAQ](introduction/4_faq.md)
 
diff --git a/docs/architecture/0_supported_verifiers.md b/docs/architecture/0_supported_verifiers.md
@@ -1,5 +1,7 @@
 # Supported verifiers
 
+Aligned Layer's support for multiple proof systems is a significant advantage, as it allows users to choose the most suitable system based on their specific requirements.
+
 The following is the list of the verifiers currently supported by Aligned:
 
 - :white_check_mark: gnark - Groth16 (with BN254)
diff --git a/docs/introduction/0_about_aligned.md b/docs/introduction/0_about_aligned.md
@@ -14,7 +14,11 @@ Currently, proof verification in Ethereum is expensive and throughput is limited
 
 Proof technology has been evolving over the last decade, with new arguments, fields, commitments and other tools appearing every day. It is hard to try new ideas if verification costs are high and there is a considerable go-to-market time, as a consequence of development time of new, gas-optimized smart contracts, or the inclusion of new precompiles to make them affordable.
 
-Aligned provides an alternative to reduce costs and increase throughput significantly. This is achieved by two different modes: the fast mode and the aggregation/slow mode. The fast mode works with a subset of Ethereum’s validators via restaking. Validators (also called Operators) receive proofs, verify them using the verification code written in Rust or another higher-level language, and sign messages with BLS signatures. If a two-thirds majority agrees, the results are posted in Ethereum. Since Aligned’s operators only need to run the verification code on bare metal, we have several advantages compared to running it on top of the EVM:
+Aligned provides an alternative to reduce costs and increase throughput significantly. This is achieved by two different modes: **fast mode** and **aggregation mode**. 
+
+The fast mode works with a subset of Ethereum’s validators via restaking. Validators (also known as Operators) receive proofs, verify them using the verification code written in Rust or any other higher-level language, and then sign messages with BLS signatures. If a two-thirds (2/3) majority agrees, the results are posted in Ethereum. 
+
+Since Aligned’s operators only need to run the verification code on bare metal, we have several advantages compared to running it on top of the EVM:
 
 - The code can be optimized for speed, not gas consumption.
 - We can leverage parallelization to increase throughput.
diff --git a/docs/introduction/2_core_concepts.md b/docs/introduction/2_core_concepts.md
diff --git a/docs/introduction/2_key_terms.md b/docs/introduction/2_key_terms.md
@@ -0,0 +1,49 @@
+## Key Terms
+
+### Proof
+
+A **Proof** is cryptographic data that can attest to the validity of a given computation. The concrete data and size depend on the proof system and program used.
+
+### Verification
+
+The **Verification** is an algorithm that takes the proof, and associated public data and verification key/program and outputs whether the proof is valid or not.
+
+### Proof Batch
+
+A **Proof batch** is a collection of verification tasks to be carried out by the Operators.
+
+### User CLI
+
+The **User CLI** is used to interact with the Verifier Task Batcher. It sends proof and public input data and receives the verification data in Aligned.
+
+### Verifier Task Batcher
+
+The **Verifier Task Batcher** receives tasks from users, creates batches of tasks, publishes the proof and public data in the Data service, and sends the batches’ data to Ethereum. This service is permissionless, meaning users have the option to run their own batcher.
+
+### Service Manager
+
+The **Service Manager (Ethereum smart contract)** receives the batches’ data and signatures from the BLS signature aggregator. This contract provides information to validators and Light Clients on the batches/tasks.
+
+### Data Service
+
+The **Data Service** temporarily stores the data for the proof and public input.
+
+### Operators
+
+The **Operators** are responsible for performing the verification of the proofs in each batch and signing messages with the results.
+
+### BLS Signature Aggregator
+
+The **BLS Signature Aggregator** receives the signatures from the Operators, checks if a quorum is reached, if so, it performs the aggregation of the signatures.
+
+### Light Clients
+
+The **Light Client** samples random tasks from the Service Manager, checks the proofs, and compares against the results posted to Ethereum by Aligned. If there are differences, it can trigger an L1 verification via the proof service. In case of malicious behavior by Aligned’s Operators, this would lead to slashing.
+
+### Proof Service
+
+The **Proof Service** receives results from the Light Clients; in case there are differences with the results posted by Aligned, it triggers a re-verification on Ethereum. Note that this re-verification can also be triggered by any user.
+
+### Proof Aggregator
+
+The **Proof aggregator**, once tasks have been verified by Aligned’s Operators, performs recursive proof verification to create one proof that will attest to the validity of all proofs contained in the batch. This proof is verified on-chain.
