@@ -16,21 +16,18 @@ It is of the utmost importance to follow the recommendations below.
 
 {% stepper %}
 {% step %}
-
 #### Prevent unauthorized access to signer infrastructure
 
 Prevent unauthorized access to the sBTC Signer infrastructure (the signer itself, its private key, and the associated PostgreSQL database).
 {% endstep %}
 
 {% step %}
-
 #### Keep an offline, secure backup of the Signer private key
 
 Keep an offline, secure backup of the sBTC Signer private key.
 {% endstep %}
 
 {% step %}
-
 #### Regularly backup PostgreSQL database
 
 Regularly backup the PostgreSQL database and store it in a secure location.
@@ -51,8 +48,6 @@ Note that these are in _addition_ to the hardware requirements for running a Sta
 
 ## Connection diagram
 
-<figure><img src="../.gitbook/assets/image%20(8).png" alt=""><figcaption></figcaption></figure>
-
 ## Configure your Bitcoin node
 
 ### Minimum version
@@ -74,21 +69,18 @@ The signer connects to Bitcoin Core via RPC and polls for new bitcoin blocks. Th
 
 {% stepper %}
 {% step %}
-
 #### Bitcoin Core validates a new block
 
 Bitcoin Core validates a new block.
 {% endstep %}
 
 {% step %}
-
 #### Signer detects the block via RPC polling
 
 Signer detects the block via RPC polling.
 {% endstep %}
 
 {% step %}
-
 #### Signer processes relevant sBTC transactions
 
 Signer processes relevant sBTC transactions.
 
@@ -6,7 +6,7 @@
 
 This guide is a step-by-step walkthrough for setting up and running a signer. It covers only the signer infrastructure: the signer software and the Stacks node it connects to.
 
-If you are not familiar with the concept of signing, be sure to check out the [Stackers and Signing concept guide](../../learn/block-production/signing.md).
+If you are not familiar with the concept of signing, be sure to check out the [Stackers and Signing concept guide](https://github.com/stacks-network/docs/blob/master/docs/learn/block-production/signing.md).
 
 ### Background and High-Level Process
 
@@ -17,7 +17,7 @@ This doc provides instructions to set up both using either Docker or the release
 ### Knowledge Prerequisites
 
 * Docker and basic knowledge of pulling and running images
-* Basic knowledge of [Stacks accounts](../../learn/network-fundamentals/wallets-and-accounts.md)
+* Basic knowledge of [Stacks accounts](https://github.com/stacks-network/docs/blob/master/docs/learn/network-fundamentals/wallets-and-accounts.md)
 
 {% stepper %}
 {% step %}
@@ -114,7 +114,7 @@ Signers are intended to work with a local node. The node<->signer connection is
 
 ## Create a Configuration File
 
-Create a file named `signer-config.toml`. Populate it with the example signer config file contents from the [Sample Configuration Files](../../reference/node-operations/signer-configuration.md) page. Each field is described on that page.
+Create a file named `signer-config.toml`. Populate it with the example signer config file contents from the [Sample Configuration Files](https://github.com/stacks-network/docs/blob/master/docs/reference/node-operations/signer-configuration.md) page. Each field is described on that page.
 
 ***
 
@@ -229,7 +229,7 @@ Start the Stacks node after the signer is running. The node will not run unless
 
 ### Stacks Node Configuration
 
-Create `node-config.toml`. See the [Sample Configuration Files](../../reference/node-operations/signer-configuration.md) page for the full contents.
+Create `node-config.toml`. See the [Sample Configuration Files](https://github.com/stacks-network/docs/blob/master/docs/reference/node-operations/signer-configuration.md) page for the full contents.
 
 Important fields to change:
 
 
@@ -16,7 +16,7 @@
 
 If you want to get up and running as an active signer as quickly as possible, here is a list of the commands you need to run and actions to take.
 
-If you are not familiar with how signing works yet, be sure to check out the [Signing concept guide](../../learn/block-production/signing.md).
+If you are not familiar with how signing works yet, be sure to check out the [Signing concept guide](https://github.com/stacks-network/docs/blob/master/docs/learn/block-production/signing.md).
 
 {% hint style="danger" %}
 The CLI examples below may show outdated release versions. For the latest releases, always refer to the links above in the top info block.
 
@@ -3,7 +3,7 @@
 This guide covers everything you need to stack independently as a solo stacker: starting, extending, increasing, and stopping your stacking position.
 
 {% hint style="info" %}
-This guide assumes you are familiar with stacking at a conceptual level. If not, read the [Stacking](../../learn/block-production/stacking.md) concept guide first.
+This guide assumes you are familiar with stacking at a conceptual level. If not, read the [Stacking](https://github.com/stacks-network/docs/blob/master/docs/learn/block-production/stacking.md) concept guide first.
 {% endhint %}
 
 Solo stacking requires meeting the minimum STX threshold and either running a signer or collaborating with one. The minimum amount is dynamic and can be found at the [pox endpoint](https://api.mainnet.hiro.so/v2/pox) under `min_threshold_ustx` (1 STX = 1,000,000 uSTX).
 
@@ -16,6 +16,10 @@ For STX-only staking, use [app.leather.io/staking](https://app.leather.io/stakin
 
 Whichever you use, the transaction goes to `pox-5` and locks your STX in your own account.
 
+<figure><img src="../.gitbook/assets/image.png" alt=""><figcaption></figcaption></figure>
+
+<figure><img src="../.gitbook/assets/image (1).png" alt=""><figcaption></figcaption></figure>
+
 [Watch the flow end to end](https://x.com/Stacks/status/2083267023916662923)
 
 {% hint style="warning" %}
@@ -24,6 +28,8 @@ Staking and staking updates are blocked during the prepare phase, the last 100 B
 
 A transaction ID confirms submission, not success. Confirm the position on-chain or in your wallet before treating yourself as staked.
 
+<figure><img src="../.gitbook/assets/image (2).png" alt=""><figcaption></figcaption></figure>
+
 {% hint style="warning" %}
 **One position per Stacks principal.** STX-only staking and a protocol bond are mutually exclusive. Registering a bond while staked fails with `ERR_ALREADY_STAKED (u19)`.
 {% endhint %}
@@ -37,7 +43,7 @@ If you took whichever manager your app offered, you can skip this. Everything be
 * **Admin set.** Who can change the fee and withdraw accrued fees. Some managers block an admin from removing themselves, so the contract can never be left with no admin. Others have no such guard.
 * **An active signer-key grant.** A manager without one cannot accept new stake, and your transaction fails with `ERR_SIGNER_KEY_GRANT_NOT_FOUND (u17)`.
 
-A manager needs 50,000 STX (`SIGNER_SET_MIN_USTX`) in aggregate across everyone staking to it before it enters the signer set. That threshold is fixed and applies to the manager rather than to you, so your own stake can be any size.
+A manager needs 50,000 STX (`SIGNER_SET_MIN_USTX`) in aggregate across everyone staking to it before it enters the signer set. That threshold is fixed and applies to the manager rather than to you, so your own stake can be any size as long as the signer-manager doesn't restrict it.
 
 {% hint style="info" %}
 **Immutable code, mutable terms.** A deployed contract's Clarity source can never change, but its parameters can. An admin can change the fee at any time, up to whatever ceiling that contract fixed at deployment. Read the current fee and the admin set rather than assuming the economics are settled.