update docs (#534)

Co-authored-by: Mariano A. Nicolini <mariano.nicolini.91@gmail.com>

Author: cliraa

docs/SUMMARY.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-* [What is Aligned?](introduction/0_what_is_aligned.md)
+* [About Aligned](introduction/0_about_aligned.md)
 * [Getting started](introduction/1_getting_started.md)
 * [FAQ](introduction/2_faq.md)
 * [Core concepts](introduction/3_core_concepts.md)
@@ -22,7 +22,7 @@
 ## Useful links
 
 * [All the proof aggregation solutions will use RISC-V zkvms](https://blog.alignedlayer.com/all-the-proof-aggregation-solutions-will-use-risc-v-zkvms/)
-* [Manifesto](https://blog.alignedlayer.com/aligned_manifesto/)
+* [Manifesto](https://mirror.xyz/0x7794D1c55568270A81D8Bf39e1bcE96BEaC10901/rOya8TwZvj_8kTpjDPVwTuNc1UcS0VLUr1t2nhCxYj8)
 
 ## Contacts
 

docs/architecture/0_fast_mode.md

@@ -2,7 +2,9 @@
 
 ## Architecture
 Aligned’s architecture is shown in the figure below:
+
 ![Figure 1: Architecture fast mode](../images/aligned_architecture.png)
+
 The validators/AVS operators are responsible for proof verification. We also provide a light client to sample and check proofs at random. If there is a difference between Aligned’s results and the light clients, a proof service can trigger re-execution of the proof of Ethereum, leading to slashing if malicious behavior is detected.
 
 ### Flow for sending a proof and publishing the result on Ethereum (Fast Mode)
@@ -20,4 +22,4 @@ The flow for sending a proof and having the results on Ethereum is as follows:
 4. The operators, using the data in Ethereum, download the proofs from the DataService. They then verify that the Merkle root is equal to the one in Ethereum, and verifies all the proofs.
 5. If the proofs are valid, they sign the root and send this to the BLS signature aggregator.
 6. The signature aggregator accumulates the signed responses until reaching the quorum, then sends the aggregated signature to Ethereum.
-7. Ethereum verifies the aggregated signatures and changes the state of the batch to verified.
+7. Ethereum verifies the aggregated signatures and changes the state of the batch to verified.

docs/architecture/1_aggregation_mode.md

@@ -2,8 +2,8 @@
 
 General Prover/Verifier: Every several days, takes the proofs from the DA layer and generates a proof of the verification of all the proofs. The general prover can be based on the SP1, Risc0 or Nexus virtual machine, which is a virtual machine able to prove general Rust code. The proof of the verification of the proofs is done using the corresponding verifier codes in Rust. The verification can be done using a tree structure.
 
-To aggregate all the proofs, in the first step, all proofs are transformed into proofs of execution of the virtual machine, achieving proof uniformity (see Figure 2). We can then shrink proof size by recursively proving the verification of proofs, as shown in the tree diagram (see Figure 3).
+To aggregate all the proofs, in the first step, all proofs are transformed into proofs of execution of the virtual machine, achieving proof uniformity (see Figure 1). We can then shrink proof size by recursively proving the verification of proofs, as shown in the tree diagram (see Figure 2).
 
-![Figure 4: Prover](../images/prover.png)
+![Figure 1: Prover](../images/prover.png)
 
-![Figure 5: Recursion tree](../images/recursion.png)
+![Figure 2: Recursion tree](../images/recursion.png)

docs/introduction/0_what_is_aligned.md docs/introduction/0_about_aligned.mddocs/introduction/0_what_is_aligned.md renamed to docs/introduction/0_about_aligned.md

@@ -72,4 +72,4 @@ Aligned works in:
 
 If you don't meet these requirements, you can compile the binaries yourself following the [README](https://github.com/yetanotherco/aligned_layer)
 
-To try Aligned with other proving systems, check the [this]() guide
+To try Aligned with other proving systems, check [this](https://docs.alignedlayer.com/guides/0_proving_systems) guide