some corrections

docs/user/dappnode-cloud/overview.md

@@ -25,15 +25,17 @@ With Dappnode Cloud, you can easily scale your resources up or down based on you
 
 It is much better to run a physical Dappnode at your place for these 2 main reasons:
 
-### 1. Economics
-A physical machine has a higher initial cost, but leverages your existing internet connection and consumes less energy than your fridge. This initial cost is pretty much the only cost you will have for the lifetime of the hardware you use. 
+### 1. Economics 💲
+
+A physical machine has a higher initial cost, but leverages your existing internet connection and consumes less energy than your fridge. This initial cost is pretty much the only cost you will have for the lifetime of the hardware you use.
 Cloud servers have monthly costs associated with it that never go away, resulting in higher cost in the long term.
 
 In summary, you will be better off with a physical machine if you plan to use your Dappnode for a long time, and better off with a Dappnode Cloud if you only want to use the instance for a short period of time.
 
-### 2. Decentralization
-The networks you will run on your Dapppnode become more resilient to corporate capture, government interference and localized events the more decentralized their nodes are. By running a Node in the cloud it is very likely that there is already a node of that network in the same data center, therefore adding no extra value to the decentralization of the network. 
-If instead you run the same node in a home setup from your home, you are adding a node that is much harder to censor, block, locate and subjugate than a node controlled by a big infrastructure corporation. 
+### 2. Decentralization 🗽
+
+The networks you will run on your Dapppnode become more resilient to corporate capture, government interference and localized events the more decentralized their nodes are. By running a Node in the cloud it is very likely that there is already a node of that network in the same data center, therefore adding no extra value to the decentralization of the network.
+If instead you run the same node in a home setup from your home, you are adding a node that is much harder to censor, block, locate and subjugate than a node controlled by a big infrastructure corporation.
 
 Remember, "The Cloud" is just someone else's computer.
 

docs/user/dappnode-cloud/providers/aws/faqs.md

@@ -96,20 +96,6 @@ Having SSH access is crucial for maintaining and managing your Dappnode instance
 
 </details>
 
-<details>
-    <summary><strong>Why do I want to connect via SSH to my Dappnode?</strong></summary>
-
-Connecting via SSH to your Dappnode allows you to access your instance's terminal directly. Even if you have obtained your Wireguard credentials via Telegram, having SSH access is important for several reasons:
-
-- **Full Control:** SSH access gives you complete control over your Dappnode instance, allowing you to perform advanced configurations and manage the system directly.
-
-- **Troubleshooting:** In case of potential issues or errors, accessing the terminal via SSH enables you to diagnose and fix problems efficiently.
-- **Advanced Management:** You can run commands, update software, monitor system performance, and manage services that may not be accessible through the standard Dappnode UI.
-
-Having SSH access is crucial for maintaining and managing your Dappnode instance effectively, ensuring you can handle any technical challenges that arise.
-
-</details>
-
 <details>
     <summary><strong>I've already launched my instance and I'm not getting my Wireguard credentials</strong></summary>
 

docs/user/dappnode-cloud/providers/aws/set-up-instance.md

@@ -12,12 +12,18 @@ To launch a Dappnode AMI instance, follow these steps:
 
 - In case you end up on another website after signing up, navigate again to the [AWS Marketplace](https://aws.amazon.com/marketplace/).
 
-### 3. **Choose Dappnode AMI** 📀
+### 3. **Subscribe to Dappnode AMI** 📀
 
 - Search "Dappnode" in the top search bar and choose the "Dappnode Cloud - Telegram Credentials - By Dappnode" option.
 
 - On our Dappnode AMI page, you can check some information about our image. When you are ready, click "Continue to Subscribe".
 
+- Accept the terms and click "Continue to Configuration".
+
+- Check the region and click "Continue to Launch" to proceed with the instance launch.
+
+- In the "Choose Action" dropdown, select "Launch through EC2" and click "Launch".
+
 ### 4. **Set Up Telegram for Wireguard Credentials (Optional)** 💬
 
 This step is only necessary if you are planning to get your Wireguard credentials via Telegram.
@@ -28,14 +34,6 @@ This step is only necessary if you are planning to get your Wireguard credential
 
 ### 5. **Launch Instance** 🚀
 
-After subscribing, you will need to follow these steps to launch your Dappnode instance:
-
-- Accept the terms and click "Continue to Configuration".
-- Check the region and click "Continue to Launch" to proceed with the instance launch.
-- In the "Choose Action" dropdown, select "Launch through EC2" and click "Launch".
-
-#### Instance Configuration
-
 Once in the EC2 "Launch an instance" UI you will have to choose the configuration of your instance. Next steps will explain you what configurations do you need to modify section by section.
 
 1.  **Name:** Give a name to your instance. This name is for you to identify it in the EC2 UI.
@@ -105,45 +103,48 @@ Once in the EC2 "Launch an instance" UI you will have to choose the configuratio
 
 To obtain the Wireguard credentials for your instance, you have two different approaches:
 
-1.  **Via SSH**
+1.  **Via Telegram Bot**
+
+    - Ensure you have completed the optional Telegram setup steps mentioned earlier in the guide.
 
-- After launching the instance, click the "Connect" button in the AWS console.
-- Go to the "SSH client" tab where it will provide you with a command like this:
-  `ssh -i "yourKeyPair-aws.pem" root@yourInstanceDNS`
-  Open your terminal and modify the command to use the `ubuntu` user and add `sudo` for permissions:
+    - After launching the instance, go to your new bot's chat using the link provided by BotFather.
 
-```sh
-sudo ssh -i "yourKeyPair-aws.pem" ubuntu@yourInstanceDNS
-```
+    - Send any message to your bot. If the configuration is correct, you should receive a message saying `✅ Successfully saved channel ID`.
 
-:::info
-Ensure this command is run in the directory where your key pair file is located.
-:::
+    - Send the command `/get_wireguard_credentials` in the bot chat. The bot should return your Wireguard credentials. Copy them, as the next step will explain how to use these credentials.
 
-- Once connected to your instance, run the following command:
+2.  **Via SSH**
 
-```sh
-dappnode_wireguard
-```
+    This approach is for more expiremented users, since you will have to use the terminal.
 
-This command will output your Wireguard credentials. Copy them from your terminal using `Ctrl+Shift+C` / `⌘+Shift+C`. The next step will explain how to use these credentials.
+    - After launching the instance, click the "Connect" button in the AWS console.
 
-2.  **Via Telegram Bot**
+    - Go to the "SSH client" tab where it will provide you with a command like this:
+      `ssh -i "yourKeyPair-aws.pem" root@yourInstanceDNS`
+      Open your terminal and modify the command to use the `ubuntu` user and add `sudo` for permissions:
 
-- Ensure you have completed the optional Telegram setup steps mentioned earlier in the guide.
+    ```sh
+    sudo ssh -i "yourKeyPair-aws.pem" ubuntu@yourInstanceDNS
+    ```
 
-- After launching the instance, go to your new bot's chat using the link provided by BotFather.
+    :::tip
+    Ensure this command is run in the directory where your key pair file is located.
+    :::
 
-- Send any message to your bot. If the configuration is correct, you should receive a message saying `✅ Successfully saved channel ID`.
+    - Once connected to your instance, run the following command:
 
-- Send the command `/get_wireguard_credentials` in the bot chat. The bot should return your Wireguard credentials. Copy them, as the next step will explain how to use these credentials.
+    ```sh
+    dappnode_wireguard
+    ```
 
-  :::info
-  The installation of Dappnode on your instance may take a few minutes. If you try to obtain the credentials before the installation is complete, you may not receive them. If this happens, wait a few minutes and try again.
+    This command will output your Wireguard credentials. Copy them from your terminal using `Ctrl+Shift+C` / `⌘+Shift+C`. The next step will explain how to use these credentials.
 
-  - **Via SSH**: If you encounter this issue, exit your SSH session with the `exit` command and reconnect as explained above.
-  - **Via Telegram Bot**: Simply retry the `/get_wireguard_credentials` command after a short wait.
-    :::
+    :::info
+    The installation of Dappnode on your instance may take a few minutes. If you try to obtain the credentials before the installation is complete, you may not receive them. If this happens, wait a few minutes and try again.
+
+    - **Via SSH**: If you encounter this issue, exit your SSH session with the `exit` command and reconnect as explained above.
+    - **Via Telegram Bot**: Simply retry the `/get_wireguard_credentials` command after a short wait.
+      :::
 
 ### 7. **Connect via Wireguard** 🔌