Bump minimum sBTC requirements (#1683)

Author: aldur

guides-and-tutorials/sbtc/best-practices-for-running-an-sbtc-signer.md

@@ -23,15 +23,15 @@ your sBTC Signer.
 - Optionally, allow traffic to the P2P ports of your Stacks and Bitcoin node.
 - Deny traffic to any other port and service, unless required, e.g. for SSH.
 
-### Monitor and observer your sBTC Signer
-
-{% hint style="info" %}
-This section is in progress as the core developers improve the sBTC Signer
-observability.
-{% endhint %}
-
-- Retain at least 1 day of logs for both the sBTC Signer, the Stacks node, and the
-  Bitcoin node.
+### Monitor and observe your sBTC Signer
+
+- Retain at least 1 day of logs for both the sBTC Signer, the Stacks node, and
+  the Bitcoin node.
+- The sBTC signer can optionally expose Prometheus metrics (see
+  `prometheus_exporter_endpoint` configuration option).
+  - You can use them to monitor its health ([this guide shows how to configure
+    Alloy to collect metrics on Grafana
+    cloud](../running-a-signer/how-to-monitor-signer.md)).
 
 ### Downstream components
 

guides-and-tutorials/sbtc/how-to-run-sbtc-signer.md

@@ -10,8 +10,8 @@ before deploying it.
 
 Below are the **minimum required specs** to be able to run a sBTC signer.
 
-- 1 cpu
-- 256MB memory
+- 2 CPU
+- 4GB memory
 - 50GB storage
 
 Note that these are in _addition_ to the hardware requirements for running a