Fixes after Jesse review

Author: fabrizio-stacks

docs/operate/run-a-signer/README.md

@@ -6,18 +6,18 @@
 
 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](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/signing).
+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).
 
 ### Background and High-Level Process
 
 To run a signer you'll run a signer and a Stacks node side-by-side. Specifically, run a follower node. The signer monitors events from the Stacks node and uses the generated account (see Preflight Setup) to sign incoming Stacks blocks sent from the Stacks node.
 
-This doc provides instructions to set up both using either Docker or the release binaries available in the [stacks core releases](https://github.com/stacks-network/stacks-core/releases) repository, and how to configure them so the signer and Stacks node communicate correctly.
+This doc provides instructions to set up both using either Docker or the release binaries available in the [stacks core releases](https://github.com/stacks-network/stacks-core/releases/latest) repository, and how to configure them so the signer and Stacks node communicate correctly.
 
 ### Knowledge Prerequisites
 
 * Docker and basic knowledge of pulling and running images
-* Basic knowledge of [Stacks accounts](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/network-fundamentals/wallets-and-accounts)
+* Basic knowledge of [Stacks accounts](../../learn/network-fundamentals/wallets-and-accounts.md)
 
 {% stepper %}
 {% step %}
@@ -114,13 +114,13 @@ 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](https://app.gitbook.com/s/GVj1Z9vMuEOMe7oH7Wnq/node-operations/signer-configuration) 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](../../reference/node-operations/signer-configuration.md) page. Each field is described on that page.
 
 ***
 
 ## Running the Signer
 
-Two options: Docker (recommended) or binary. Binaries are available on the [Stacks Core releases page](https://github.com/stacks-network/stacks-core/releases).
+Two options: Docker (recommended) or binary. Binaries are available on the [Stacks Core releases page](https://github.com/stacks-network/stacks-core/releases/latest).
 
 ### Running the Signer with Docker
 
@@ -168,7 +168,7 @@ CMD ["stacks-signer", "run", "--config", "/config.toml"]
 
 ### Running the Signer as a Binary
 
-Download the pre-built binaries from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases), unzip the archive for your architecture. It includes the `stacks-signer` binary.
+Download the pre-built binaries from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases/latest), unzip the archive for your architecture. It includes the `stacks-signer` binary.
 
 Run the signer:
 
@@ -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](https://app.gitbook.com/s/GVj1Z9vMuEOMe7oH7Wnq/node-operations/signer-configuration) page for the full contents.
+Create `node-config.toml`. See the [Sample Configuration Files](../../reference/node-operations/signer-configuration.md) page for the full contents.
 
 Important fields to change:
 
@@ -296,7 +296,7 @@ If you get connection refused errors, you may need to point `events_observer.end
 
 ### Run a Stacks Node with a Binary
 
-Download the pre-built `stacks-node` binary from the [Stacks Core releases](https://github.com/stacks-network/stacks-core/releases).
+Download the pre-built `stacks-node` binary from the [Stacks Core releases](https://github.com/stacks-network/stacks-core/releases/latest).
 
 Start the node:
 

docs/operate/run-a-signer/best-practices-to-run-a-signer.md

@@ -193,6 +193,13 @@ sudo systemctl status stacks-signer.service
 sudo systemctl status stacks-node.service
 ```
 
+View logs with:
+
+```bash
+journalctl -xefu stacks-signer
+journalctl -xefu stacks-node
+```
+
 ### Backup signer keys in cold-storage
 
 * Keep an offline, secure backup of all Signer private keys (e.g., hardware security modules or encrypted storage devices).

docs/operate/run-a-signer/signer-quickstart.md

@@ -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](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/signing).
+If you are not familiar with how signing works yet, be sure to check out the [Signing concept guide](../../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.
@@ -88,7 +88,7 @@ From this file, you'll need the `privateKey` value.
 
 **Download the stacks-signer binary**
 
-Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases). Each release includes pre-built binaries. Download the [latest signer release ZIP file](https://github.com/stacks-network/stacks-core/releases/latest) for your server’s architecture and decompress it. Inside of that folder is a `stacks-signer` binary.
+Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases/latest). Each release includes pre-built binaries. Download the [latest signer release ZIP file](https://github.com/stacks-network/stacks-core/releases/latest) for your server’s architecture and decompress it. Inside of that folder is a `stacks-signer` binary.
 
 Assuming a `Linux x64 glibc` machine, the commands to download and uncompress the signer binary look like this:
 
@@ -201,7 +201,7 @@ We have created guides for running both a [full Bitcoin node](../run-a-node/run-
 
 **Download the stacks-node binary**
 
-Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases). Each release includes pre-built binaries. Download the [latest node release ZIP file](https://github.com/stacks-network/stacks-core/releases/latest) for your server’s architecture and decompress it. Inside of that folder is a `stacks-node` binary.
+Official binaries are available from the [Stacks Core releases page on Github](https://github.com/stacks-network/stacks-core/releases/latest). Each release includes pre-built binaries. Download the [latest node release ZIP file](https://github.com/stacks-network/stacks-core/releases/latest) for your server’s architecture and decompress it. Inside of that folder is a `stacks-node` binary.
 
 Assuming a `Linux x64 glibc` machine, the commands to download and uncompress the node binary look like this:
 

docs/operate/stacking-stx/README.md

@@ -1,6 +1,6 @@
 # Stacking STX
 
-Stacking is the process of locking STX tokens to support the network's consensus and earn BTC rewards. If you aren't familiar with how stacking works, read the [Stacking](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/stacking) and [Stackers and Signing](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/signing) concept guides first.
+Stacking is the process of locking STX tokens to support the network's consensus and earn BTC rewards. If you aren't familiar with how stacking works, read the [Stacking](../../learn/block-production/stacking.md) and [Stackers and Signing](../../learn/block-production/signing.md) concept guides first.
 
 Stacking utilizes the `pox-4` contract. You can view it on the [Explorer](https://explorer.hiro.so/txid/SP000000000000000000002Q6VF78.pox-4?chain=mainnet) and review the detailed [stacking contract walkthrough](/broken/spaces/GVj1Z9vMuEOMe7oH7Wnq/pages/fc4fa1c229d8cb4deedf49de6dc1de0dc0b1ed72) to understand what each function does.
 

docs/operate/stacking-stx/operate-a-pool.md

@@ -3,7 +3,7 @@
 This guide covers how to operate a stacking pool: accepting delegated STX from stackers, committing them to reward cycles, and managing the pool's stacked position.
 
 {% hint style="info" %}
-This guide assumes you are familiar with stacking at a conceptual level. If not, read the [Stacking](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/stacking) concept guide first.
+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.
 {% endhint %}
 
 If you want to delegate your STX to a pool instead, see the [Stack with a Pool](stack-with-a-pool.md) guide.

docs/operate/stacking-stx/solo-stacking.md

@@ -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](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/stacking) concept guide first.
+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.
 {% 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).

docs/operate/stacking-stx/stack-with-a-pool.md

@@ -3,7 +3,7 @@
 This guide covers delegated stacking from the **delegator** perspective: how to delegate your STX to a pool, increase your delegation, revoke it, and stop stacking.
 
 {% hint style="info" %}
-This guide assumes you are familiar with stacking at a conceptual level. If not, read the [Stacking](https://app.gitbook.com/s/H74xqoobupBWwBsVMJhK/block-production/stacking) concept guide first.
+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.
 {% endhint %}
 
 Delegating is the most common stacking scenario. It applies when you do not meet the minimum STX threshold to solo stack and want a pool operator to stack on your behalf. This is a **non-custodial** delegation. Your STX do not leave your wallet.