docs: improve docs folder (#1988)

Co-authored-by: Marcos Nicolau <[email protected]>
Co-authored-by: Julian Arce <[email protected]>
Co-authored-by: Mauro Toscano <[email protected]>

Author: 4 people

docs/1_introduction/1_try_aligned.md

@@ -14,15 +14,15 @@ We will download a previously generated SP1 proof, send it to Aligned for verifi
 1. Download and install Aligned to send proofs in the testnet:
 
 ```bash
-curl -L https://raw.githubusercontent.com/yetanotherco/aligned_layer/main/crates/cli/install_aligned.sh | bash
+curl -L https://raw.githubusercontent.com/yetanotherco/aligned_layer/testnet/crates/cli/install_aligned.sh | bash
 ```
 
 2. Run the `source` command that should appear in the shell
 
 3. Download the example SP1 proof file together with the ELF file of the proved program using:
 
 ```bash
-curl -L https://raw.githubusercontent.com/yetanotherco/aligned_layer/main/crates/cli/get_proof_test_files.sh | bash
+curl -L https://raw.githubusercontent.com/yetanotherco/aligned_layer/testnet/crates/cli/get_proof_test_files.sh | bash
 ```
 
 4. Send the proof to be verified in Aligned with

docs/1_introduction/3_faq.md

@@ -25,12 +25,16 @@ The batcher cannot transfer user's funds to other accounts, only spend them to c
 
 ### How do I send proofs without a batcher?
 
+You can see the steps to do it in [this guide](../3_guides/8_submitting_batch_without_batcher.md).
+
 ### How do I run my own batcher?
 
 ### Why build Aligned on top of Ethereum?
 
 Ethereum is the most decentralized and most significant source of liquidity in the crypto ecosystem. We believe it is the most ambitious and long-term project on the internet. Aligned is being built to help Ethereum achieve its highest potential, and we believe this is only possible through validity/zero-knowledge proofs.
 
+For further reading on this subject, you can refer to [this aligned blog article](https://blog.alignedlayer.com/why-ethereum/), which explains why we chose Ethereum.
+
 ### What is Aligned's throughput?
 
 Aligned runs the verifier’s code natively. Verification time depends on the proof system, program run, and public input. Generally, most verifiers can be run on the order of milliseconds on consumer-grade hardware. We can optimize the code for speed and leverage parallelization by running it natively. Our current testnet can verify more than 4000 proofs per second.

docs/2_architecture/components/3_service_manager_contract.md

@@ -19,20 +19,23 @@ Besides the base [EigenLayer middleware contracts](https://github.com/Layr-Labs/
 ```solidity
 function createNewTask(
     bytes32 batchMerkleRoot,
-    string calldata batchDataPointer
+    string calldata batchDataPointer,
+    uint256 respondToTaskFeeLimit
 ) external payable
 ```
 
 This method is called to create a new batch verification task that will broadcast an event to all operators, signaling that there are new proofs awaiting verification.
 
 * `batchMerkleRoot` is a 256 bit hash corresponding to the Merkle Root of the proofs batch to be verified by operators.
 * `batchDataPointer` is a string representing a link to some specific data storage location. This is used by operators to download the entire batch of proofs.
+* `respondToTaskFeeLimit` are the funds required for the operator to respond to the task
 
 #### Respond to task
 
 ```solidity
 function respondToTask(
     bytes32 batchMerkleRoot,
+    address senderAddress,
     NonSignerStakesAndSignature memory nonSignerStakesAndSignature
 ) external
 ```
@@ -41,6 +44,7 @@ This method is used by the Aggregator once the quorum for a particular task has
 
 * `batchMerkleRoot` is a 256 bit hash representing the Merkle Root of the batch that has been verified and signed by operators.
 * `nonSignerStakesAndSignature` is a struct provided by EigenLayer middleware with information about operators' signatures, stakes and quorum for the given task.
+* `senderAddress` is the address of the batcher that created the task being responded to.
 
 ### Verify batch inclusion
 

docs/3_guides/6_setup_aligned.md

@@ -101,7 +101,7 @@ Different configs for operators can be found in `config-files/config-operator`.
 If you wish to only register an operator you can run:
 
 ```bash
-make operator_full_registration CONFIG_FILE<path_to_config_file>
+make operator_full_registration CONFIG_FILE=<path_to_config_file>
 ```
 
 and to start it once it has been registered: