Update content

Author: brunopgalvao

.ai/pages/node-infrastructure-run-a-collator-collator.md

@@ -97,18 +97,22 @@ This guide provides two deployment options. Select the option that best fits you
 
 === "Manual Setup"
 
-    Extract the binary from the official Docker image:
+    Download the `polkadot-parachain` binary from the latest stable [Polkadot SDK release](https://github.com/paritytech/polkadot-sdk/releases){target=\_blank}:
 
     ```bash
-    # Create a temporary container and copy the binary
-    docker create --name temp-parachain parity/polkadot-parachain:stable2509-2
-    sudo docker cp temp-parachain:/usr/local/bin/polkadot-parachain /usr/local/bin/
-    docker rm temp-parachain
+    # Download the latest stable release (check releases page for current version)
+    wget https://github.com/paritytech/polkadot-sdk/releases/download/polkadot-stable2509-2/polkadot-parachain
+
+    # Make it executable and move to system path
+    chmod +x polkadot-parachain
+    sudo mv polkadot-parachain /usr/local/bin/
 
     # Verify installation
     polkadot-parachain --version
     ```
 
+    Check the [Polkadot SDK releases](https://github.com/paritytech/polkadot-sdk/releases){target=\_blank} page for the latest stable version.
+
 ## Generate Node Key
 
 Generating a stable node key enables a consistent peer ID across the network. Follow these steps to generate a node key:
@@ -305,7 +309,9 @@ Sync time depends on:
 
 The relay chain uses warp sync for faster synchronization.
 
-**Important**: Do not proceed with registration until both chains are fully synced. Monitor sync progress using the log viewing commands in the [Log Management](#log-management) section.
+!!! warning
+
+    Do not proceed with registration until both chains are fully synced. Monitor sync progress using the log viewing commands in the [Log Management](#log-management) section.
 
 ## Generate Session Keys
 
@@ -383,10 +389,20 @@ The registration process varies by system parachain. General steps include the f
 
 Monitoring the following items will help ensure your collator runs efficiently to avoid service interruptions or down time:
 
-- **Block Production**: monitor for block production using the following command:
-    ```bash
-    sudo journalctl -u polkadot-collator | grep -i "prepared block"
-    ```
+- **Block Production**: Monitor for block production using the appropriate command for your setup:
+
+    === "Docker Setup"
+
+        ```bash
+        docker logs polkadot-collator 2>&1 | grep -i "prepared block"
+        ```
+
+    === "systemd Setup"
+
+        ```bash
+        sudo journalctl -u polkadot-collator | grep -i "prepared block"
+        ```
+
 - **Peer Connections**: Maintain a sufficient amount of peers for good connectivity and set up alerts to notify if peer connections falls below ten.
 - **Resource Usage**: Monitor CPU, RAM, and disk I/O and set up alerts for unusual or high usage.
 - **Sync Status**: Ensure both chains stay synced and set up alerts for sync issues.
@@ -416,32 +432,64 @@ Key metrics to monitor via Prometheus include the following:
 
 ## Log Management
 
-Effecient log management is essential to ensure collator performance and uptime. Use the following commands to help you manage logs to monitor and maintain your collator:
+Efficient log management is essential to ensure collator performance and uptime. Use the following commands to help you manage logs to monitor and maintain your collator:
+
+=== "Docker Setup"
+
+    - View logs:
+        ```bash
+        docker logs -f polkadot-collator
+        ```
+    - View recent logs (last 100 lines):
+        ```bash
+        docker logs --tail 100 polkadot-collator
+        ```
+    - Filter for errors:
+        ```bash
+        docker logs polkadot-collator 2>&1 | grep -i error
+        ```
+    - Filter for block production:
+        ```bash
+        docker logs polkadot-collator 2>&1 | grep -i "imported"
+        ```
+
+=== "systemd Setup"
+
+    - View recent logs:
+        ```bash
+        sudo journalctl -u polkadot-collator -n 100
+        ```
+    - Follow logs in real-time:
+        ```bash
+        sudo journalctl -u polkadot-collator -f
+        ```
+    - Filter for errors:
+        ```bash
+        sudo journalctl -u polkadot-collator | grep -i error
+        ```
+    - Filter for block production:
+        ```bash
+        sudo journalctl -u polkadot-collator | grep -i "imported"
+        ```
+
+## Database Maintenance
+
+Check database size periodically using the commands for your selected setup:
+
+=== "Docker Setup"
 
-- View recent logs:
-    ```bash
-    sudo journalctl -u polkadot-collator -n 100
-    ```
-- Follow logs in real-time:
-    ```bash
-    sudo journalctl -u polkadot-collator -f
-    ```
-- Filter for errors:
     ```bash
-    sudo journalctl -u polkadot-collator | grep -i error
+    # Replace with your mounted data directory path
+    du -sh ./collator-data
     ```
-- Filter for block production:
+
+=== "systemd Setup"
+
     ```bash
-    sudo journalctl -u polkadot-collator | grep -i "imported"
+    du -sh /var/lib/polkadot-collator
     ```
 
-## Database Maintenance
-
-You can check database size using the following command:
-```bash
-du -sh /var/lib/polkadot-collator
-```
-The collator node handles pruning automatically.
+The collator node handles pruning automatically based on configuration.
 
 ## Updates and Upgrades
 
@@ -492,12 +540,11 @@ Updates or upgrades can happen on either the runtime or client. Runtime upgrades
         sudo cp -r /var/lib/polkadot-collator /var/lib/polkadot-collator.backup
         ```
 
-    3. Pull the new image and extract the binary:
+    3. Download the new binary from [GitHub releases](https://github.com/paritytech/polkadot-sdk/releases){target=\_blank}:
         ```bash
-        docker pull parity/polkadot-parachain:<NEW_TAG>
-        docker create --name temp-parachain parity/polkadot-parachain:<NEW_TAG>
-        sudo docker cp temp-parachain:/usr/local/bin/polkadot-parachain /usr/local/bin/
-        docker rm temp-parachain
+        wget https://github.com/paritytech/polkadot-sdk/releases/download/<NEW_VERSION>/polkadot-parachain
+        chmod +x polkadot-parachain
+        sudo mv polkadot-parachain /usr/local/bin/
         ```
 
     4. Verify `polkadot-parachain` version to confirm successful update: