From bb7d709fb18024daab9af665873a438b9e6ce1b0 Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 20 Jan 2026 16:10:29 -0800
Subject: [PATCH 01/15] Update link in base.html to point to
 https://cookbook_ao.arweave.net/welcome/index.html

---
 docs/theme/templates/base.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/theme/templates/base.html b/docs/theme/templates/base.html
index 29b176fe0..7e110888f 100644
--- a/docs/theme/templates/base.html
+++ b/docs/theme/templates/base.html
@@ -664,7 +664,7 @@ <h2>
                                         </div>
 
                                     <a
-                                        href="https://cookbook_ao.arweave.net/welcome/ao-core-introduction.html"
+                                        href="https://cookbook_ao.arweave.net/welcome/index.html"
                                     >
                                         <button class="main-button">
                                             <svg
@@ -912,4 +912,4 @@ <h2>
 		{% endfor %}
 	  {% endblock %}
 	</body>
-  </html>
\ No newline at end of file
+  </html>

From 477ead97423a8789ca7da196705eec312ed17d8a Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 24 Feb 2026 22:10:46 +0000
Subject: [PATCH 02/15] Initial plan


From c8a14a1b6f6d30c40c905c1ffa7398fee8ee6e54 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Tue, 24 Feb 2026 22:12:06 +0000
Subject: [PATCH 03/15] docs: add Setting Up a Scheduler Device guide and link
 from Next Steps

Co-authored-by: Jonny-Ringo <92886988+Jonny-Ringo@users.noreply.github.com>
---
 .../setting-up-a-scheduler-device.md          | 35 +++++++++++++++++++
 docs/run/running-a-hyperbeam-node.md          |  1 +
 2 files changed, 36 insertions(+)
 create mode 100644 docs/run/reference/setting-up-a-scheduler-device.md

diff --git a/docs/run/reference/setting-up-a-scheduler-device.md b/docs/run/reference/setting-up-a-scheduler-device.md
new file mode 100644
index 000000000..84128cc3e
--- /dev/null
+++ b/docs/run/reference/setting-up-a-scheduler-device.md
@@ -0,0 +1,35 @@
+# Setting Up a Scheduler Device
+
+This guide is for operators who are already running a production HyperBEAM node and want to register it as an AO scheduler.
+
+## Prerequisites
+
+If you started your node using the default device list, both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
+
+## Announcing Your Scheduler Location
+
+To register your node as a scheduler on the AO network, you need to call the `~location@1.0` device endpoint **from the node host itself** (i.e. run the command on the same machine running HyperBEAM). This ensures the request originates from the correct origin.
+
+Run the following curl command on your node host (Ubuntu):
+
+```bash
+curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node
+```
+
+### What Success Looks Like
+
+A successful call returns an **HTTP 200 OK** response from `~location@1.0`. This publishes a transaction to the network announcing your scheduler's location.
+
+## Emitted Transaction Tags
+
+The published transaction should include tags similar to the following:
+
+```
+Data-Protocol: ao
+Variant: ao.N.1
+Type: Scheduler-Location
+Url: https://your-node-domain.example.com
+nonce: <nonce-value>
+```
+
+> **Note:** The `Url` field should use `https` and point to your node's publicly accessible address (for example, `https://push.forward.computer`). The `nonce` value is generated automatically.
diff --git a/docs/run/running-a-hyperbeam-node.md b/docs/run/running-a-hyperbeam-node.md
index a0689c4b4..01ebfdbc3 100644
--- a/docs/run/running-a-hyperbeam-node.md
+++ b/docs/run/running-a-hyperbeam-node.md
@@ -248,3 +248,4 @@ To stop the node running *within the `rebar3 shell`*, press `Ctrl+C` twice or us
 *   **Configure Your Node:** Deep dive into [configuration options](./configuring-your-machine.md).
 *   **TEE Nodes:** Learn about running nodes in [Trusted Execution Environments](./tee-nodes.md) for enhanced security.
 *   **Routers:** Understand how to configure and run a [router node](./joining-running-a-router.md).
+*   **Scheduler Device:** Learn how to [set up a Scheduler device](./reference/setting-up-a-scheduler-device.md) to announce your node as an AO scheduler.

From d3252fe0fef7d207a334daa354e3a36192d8ae57 Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:35:25 -0800
Subject: [PATCH 04/15] Update link for setting up Scheduler device

---
 docs/run/running-a-hyperbeam-node.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/run/running-a-hyperbeam-node.md b/docs/run/running-a-hyperbeam-node.md
index 01ebfdbc3..65098ee2f 100644
--- a/docs/run/running-a-hyperbeam-node.md
+++ b/docs/run/running-a-hyperbeam-node.md
@@ -248,4 +248,4 @@ To stop the node running *within the `rebar3 shell`*, press `Ctrl+C` twice or us
 *   **Configure Your Node:** Deep dive into [configuration options](./configuring-your-machine.md).
 *   **TEE Nodes:** Learn about running nodes in [Trusted Execution Environments](./tee-nodes.md) for enhanced security.
 *   **Routers:** Understand how to configure and run a [router node](./joining-running-a-router.md).
-*   **Scheduler Device:** Learn how to [set up a Scheduler device](./reference/setting-up-a-scheduler-device.md) to announce your node as an AO scheduler.
+*   **Scheduler Device:** Learn how to [set up a Scheduler device](./setting-up-a-scheduler-device.md) to announce your node as an AO scheduler.

From a09119530c70c90a2e31f1f321480309d584cf75 Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:40:35 -0800
Subject: [PATCH 05/15] Add setting up a scheduler device documentation

---
 docs/run/{reference => }/setting-up-a-scheduler-device.md | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename docs/run/{reference => }/setting-up-a-scheduler-device.md (100%)

diff --git a/docs/run/reference/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
similarity index 100%
rename from docs/run/reference/setting-up-a-scheduler-device.md
rename to docs/run/setting-up-a-scheduler-device.md

From 86f8fc00b829f0736955548aba57ba9a1d21132e Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:48:27 -0800
Subject: [PATCH 06/15] Update setup guide for scheduler device clarity

Clarified that the default device list is in hb_opts.erl and updated the success response location.
---
 docs/run/setting-up-a-scheduler-device.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index 84128cc3e..542164aee 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -4,7 +4,7 @@ This guide is for operators who are already running a production HyperBEAM node
 
 ## Prerequisites
 
-If you started your node using the default device list, both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
+If you started your node using the default device list in [hb_opts.erl](../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
 
 ## Announcing Your Scheduler Location
 
@@ -18,7 +18,7 @@ curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node
 
 ### What Success Looks Like
 
-A successful call returns an **HTTP 200 OK** response from `~location@1.0`. This publishes a transaction to the network announcing your scheduler's location.
+A successful call returns an **HTTP 200 OK** response from `~location@1.0` in the node logs. This publishes a transaction to the network announcing your scheduler's location.
 
 ## Emitted Transaction Tags
 

From dc860a9614a5e54a64670ec301c4ca7d6bf9a7fa Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:49:04 -0800
Subject: [PATCH 07/15] Fix link to hb_opts.erl in setup guide

---
 docs/run/setting-up-a-scheduler-device.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index 542164aee..b7b029cab 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -4,7 +4,7 @@ This guide is for operators who are already running a production HyperBEAM node
 
 ## Prerequisites
 
-If you started your node using the default device list in [hb_opts.erl](../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
+If you started your node using the default device list in [hb_opts.erl](~/src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
 
 ## Announcing Your Scheduler Location
 

From 0920e20057dd7e81a80df048407c6a93ebe2fc47 Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:49:25 -0800
Subject: [PATCH 08/15] Fix link to hb_opts.erl in setup guide

---
 docs/run/setting-up-a-scheduler-device.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index b7b029cab..c4b24b6f4 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -4,7 +4,7 @@ This guide is for operators who are already running a production HyperBEAM node
 
 ## Prerequisites
 
-If you started your node using the default device list in [hb_opts.erl](~/src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
+If you started your node using the default device list in [hb_opts.erl](.../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
 
 ## Announcing Your Scheduler Location
 

From 3a941775f5245762c32351a845c91ef1d104639b Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:50:25 -0800
Subject: [PATCH 09/15] Fix link to hb_opts.erl in setup guide

---
 docs/run/setting-up-a-scheduler-device.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index c4b24b6f4..b5e2b7079 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -4,7 +4,7 @@ This guide is for operators who are already running a production HyperBEAM node
 
 ## Prerequisites
 
-If you started your node using the default device list in [hb_opts.erl](.../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
+If you started your node using the default device list in [hb_opts.erl](../../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
 
 ## Announcing Your Scheduler Location
 

From 65d7b91f4be6a43edb406ed9f7aad36ce64f67cb Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 24 Feb 2026 15:58:48 -0800
Subject: [PATCH 10/15] Clarify scheduler setup instructions and response

Updated command instructions and success response details for clarity.
---
 docs/run/setting-up-a-scheduler-device.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index b5e2b7079..f54b3e91c 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -10,7 +10,7 @@ If you started your node using the default device list in [hb_opts.erl](../../sr
 
 To register your node as a scheduler on the AO network, you need to call the `~location@1.0` device endpoint **from the node host itself** (i.e. run the command on the same machine running HyperBEAM). This ensures the request originates from the correct origin.
 
-Run the following curl command on your node host (Ubuntu):
+Run the following curl command on your node host (Linux/Mac):
 
 ```bash
 curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node
@@ -18,7 +18,7 @@ curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node
 
 ### What Success Looks Like
 
-A successful call returns an **HTTP 200 OK** response from `~location@1.0` in the node logs. This publishes a transaction to the network announcing your scheduler's location.
+A successful call returns an **HTTP 200 OK** response from `~location@1.0` in the node logs and will give you some details in your local console. This publishes a transaction to the network announcing your scheduler's location.
 
 ## Emitted Transaction Tags
 
@@ -32,4 +32,4 @@ Url: https://your-node-domain.example.com
 nonce: <nonce-value>
 ```
 
-> **Note:** The `Url` field should use `https` and point to your node's publicly accessible address (for example, `https://push.forward.computer`). The `nonce` value is generated automatically.
+> **Note:** The `Url` field should point to your node's publicly accessible address (for example, `https://push.forward.computer`). The `nonce` value is generated automatically.

From 5722f2f007b8bd3a9072891f877645cd4c00f6ac Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Tue, 3 Mar 2026 09:02:19 -0800
Subject: [PATCH 11/15] Update field names in scheduler device setup
 documentation

---
 docs/run/setting-up-a-scheduler-device.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index f54b3e91c..47923151b 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -25,11 +25,13 @@ A successful call returns an **HTTP 200 OK** response from `~location@1.0` in th
 The published transaction should include tags similar to the following:
 
 ```
-Data-Protocol: ao
-Variant: ao.N.1
-Type: Scheduler-Location
-Url: https://your-node-domain.example.com
+data-Protocol: ao
+variant: ao.N.1
+type: location
+url: https://your-node-domain.example.com
 nonce: <nonce-value>
+time-to-live:  TTL
+codec-device: Codec
 ```
 
-> **Note:** The `Url` field should point to your node's publicly accessible address (for example, `https://push.forward.computer`). The `nonce` value is generated automatically.
+> **Note:** The `url` field should point to your node's publicly accessible address (for example, `https://push.forward.computer`). The `nonce` value is generated automatically.

From 6dd78b6c689c36bd7adfec52db6b35cc5d69a73f Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Wed, 29 Apr 2026 17:16:16 -0700
Subject: [PATCH 12/15] docs: clarify scheduler location re-announce and
 require host in config.flat

---
 docs/run/setting-up-a-scheduler-device.md | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/docs/run/setting-up-a-scheduler-device.md b/docs/run/setting-up-a-scheduler-device.md
index 47923151b..c4ad9c46d 100644
--- a/docs/run/setting-up-a-scheduler-device.md
+++ b/docs/run/setting-up-a-scheduler-device.md
@@ -1,14 +1,24 @@
 # Setting Up a Scheduler Device
 
+> **Note:** When your node launches, it will normally post (announce) its scheduler location automatically. This guide is useful if you need to re-announce the location or manually update the published location data.
+
 This guide is for operators who are already running a production HyperBEAM node and want to register it as an AO scheduler.
 
 ## Prerequisites
 
-If you started your node using the default device list in [hb_opts.erl](../../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required to enable them.
+If you started your node using the default device list in [hb_opts.erl](../../src/hb_opts.erl), both `~location@1.0` and `~scheduler@1.0` are already onboarded — no additional configuration is required.
+
+You must set `host` in your `config.flat` so the `~location@1.0` device announces the correct public URL for your node.
+
+Example:
+
+```erlang
+host = "your-node-domain.example.com".
+```
 
 ## Announcing Your Scheduler Location
 
-To register your node as a scheduler on the AO network, you need to call the `~location@1.0` device endpoint **from the node host itself** (i.e. run the command on the same machine running HyperBEAM). This ensures the request originates from the correct origin.
+To register your node as a scheduler on the AO network, you need to call the `~location@1.0` device endpoint **from the node host itself** (i.e. run the command on the same machine running HyperBEAM).
 
 Run the following curl command on your node host (Linux/Mac):
 
@@ -18,7 +28,7 @@ curl -sS -H 'Accept: application/json' http://127.0.0.1:8734/~location@1.0/node
 
 ### What Success Looks Like
 
-A successful call returns an **HTTP 200 OK** response from `~location@1.0` in the node logs and will give you some details in your local console. This publishes a transaction to the network announcing your scheduler's location.
+A successful call returns an **HTTP 200 OK** response from `~location@1.0` in the node logs and will give you some details in your local console. This publishes a transaction to the network announcing your scheduler location.
 
 ## Emitted Transaction Tags
 

From 794690ddb406656671ab946b4054cdfc2b77476d Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Thu, 14 May 2026 08:20:27 -0700
Subject: [PATCH 13/15] Add note about genesis_wasm for current process
 operations

---
 docs/run/running-a-hyperbeam-node.md | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/docs/run/running-a-hyperbeam-node.md b/docs/run/running-a-hyperbeam-node.md
index 65098ee2f..a9681cf76 100644
--- a/docs/run/running-a-hyperbeam-node.md
+++ b/docs/run/running-a-hyperbeam-node.md
@@ -38,7 +38,7 @@ To successfully build and run a HyperBEAM node, your system needs several softwa
 *   `git`: Version control for fetching the source code.
 *   `pkg-config`: Helps find installed libraries during compilation.
 *   `ncurses-dev` / `ncurses`: Required for some terminal interface elements used by Erlang/OTP.
-*   `libssl-dev` / `openssl`: Necessary for cryptographic operations and secure connections (HTTPS). You might need to set specific environment variables for `openssl` during Erlang compilation if building from source on macOS.
+*   `libssl-dev` / `openssl`: Necessary for cryptographic operations and secure connections (HTTPS). You might need to set specific environment variables for `openssl` during Erlang compilation if bui[...]
 *   `sudo` (Linux/macOS): Needed for system-level installations.
 *   `curl`: Used for downloading dependencies or interacting with web services.
 *   `ca-certificates` (Linux): Required for validating SSL certificates (often handled by the OS on macOS/Windows).
@@ -84,7 +84,7 @@ Installation methods:
     ```
 
 === "Linux / macOS (Direct Download)"
-    Get the `rebar3` binary from the [official website](https://rebar3.org/). Place the downloaded `rebar3` file in your system's `PATH` (e.g., `/usr/local/bin`) and make it executable (`chmod +x rebar3`).
+    Get the `rebar3` binary from the [official website](https://rebar3.org/). Place the downloaded `rebar3` file in your system's `PATH` (e.g., `/usr/local/bin`) and make it executable (`chmod +x reba[...]
 
 <!-- === "asdf (Recommended)"
     If using `asdf`, you can install it via the `rebar` plugin:
@@ -137,7 +137,7 @@ Before starting a node, ensure you have:
 *   Installed the [system dependencies](#system-dependencies) mentioned above.
 *   Cloned the [HyperBEAM repository](https://github.com/permaweb/HyperBEAM) (`git clone ...`).
 *   Compiled the source code (`rebar3 compile` in the repo directory).
-*   An Arweave **wallet keyfile** (e.g., generated via [Wander](https://www.wander.app)). The path to this file is typically set via the `hb_key` configuration option (see [Configuring Your HyperBEAM Node](./configuring-your-machine.md)).
+*   An Arweave **wallet keyfile** (e.g., generated via [Wander](https://www.wander.app)). The path to this file is typically set via the `hb_key` configuration option (see [Configuring Your HyperBEAM [...]
 
 ## Starting a Basic Node
 
@@ -147,6 +147,9 @@ The simplest way to start a HyperBEAM node for development or testing is using `
 rebar3 shell
 ```
 
+!!! note
+    For current process operations, start HyperBEAM with the `genesis_wasm` profile by running `rebar3 as genesis_wasm shell`.
+
 This command:
 
 1.  Starts the Erlang Virtual Machine (BEAM) with all HyperBEAM modules loaded.
@@ -180,7 +183,7 @@ rebar3 as rocksdb, genesis_wasm shell
 
 ## Node Configuration
 
-HyperBEAM offers various configuration options (port, key file, data storage, logging, etc.). These are primarily set using a `config.flat` file and can be overridden by environment variables or command-line arguments.
+HyperBEAM offers various configuration options (port, key file, data storage, logging, etc.). These are primarily set using a `config.flat` file and can be overridden by environment variables or comma[...]
 
 See the dedicated [Configuring Your HyperBEAM Node](./configuring-your-machine.md) guide for detailed information on all configuration methods and options.
 
@@ -196,7 +199,7 @@ A JSON response containing node information indicates success.
 
 ## Running for Production (Mainnet)
 
-While you can connect to the main AO network using the `rebar3 shell` for testing purposes (potentially using specific configurations or helper functions like `hb:start_mainnet/1` if available and applicable), the standard and recommended method for a stable production deployment (like running on the mainnet) is to build and run a **release**.
+While you can connect to the main AO network using the `rebar3 shell` for testing purposes (potentially using specific configurations or helper functions like `hb:start_mainnet/1` if available and app[...]
 
 **1. Build the Release:**
 
@@ -214,7 +217,7 @@ This command compiles the project and packages it along with the Erlang Runtime
 
 **2. Configure the Release:**
 
-Navigate into the release directory (e.g., `cd _build/default/rel/hb`). Ensure you have a correctly configured `config.flat` file here. See the [configuration guide](./configuring-your-machine.md) for details on setting mainnet parameters (port, key file location, store path, specific peers, etc.). Environment variables can also be used to override settings in the release's `config.flat` when starting the node.
+Navigate into the release directory (e.g., `cd _build/default/rel/hb`). Ensure you have a correctly configured `config.flat` file here. See the [configuration guide](./configuring-your-machine.md) for[...]
 
 **3. Start the Node:**
 

From 6fe5f8bc10365c3cf17a7af4bf4f46c93ed760b6 Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Thu, 14 May 2026 08:24:50 -0700
Subject: [PATCH 14/15] Fix note block rendering for genesis_wasm process
 operations

---
 docs/run/running-a-hyperbeam-node.md | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/docs/run/running-a-hyperbeam-node.md b/docs/run/running-a-hyperbeam-node.md
index a9681cf76..f798c5aaf 100644
--- a/docs/run/running-a-hyperbeam-node.md
+++ b/docs/run/running-a-hyperbeam-node.md
@@ -38,7 +38,7 @@ To successfully build and run a HyperBEAM node, your system needs several softwa
 *   `git`: Version control for fetching the source code.
 *   `pkg-config`: Helps find installed libraries during compilation.
 *   `ncurses-dev` / `ncurses`: Required for some terminal interface elements used by Erlang/OTP.
-*   `libssl-dev` / `openssl`: Necessary for cryptographic operations and secure connections (HTTPS). You might need to set specific environment variables for `openssl` during Erlang compilation if bui[...]
+*   `libssl-dev` / `openssl`: Necessary for cryptographic operations and secure connections (HTTPS). You might need to set specific environment variables for `openssl` during Erlang compilation if[...]
 *   `sudo` (Linux/macOS): Needed for system-level installations.
 *   `curl`: Used for downloading dependencies or interacting with web services.
 *   `ca-certificates` (Linux): Required for validating SSL certificates (often handled by the OS on macOS/Windows).
@@ -84,7 +84,7 @@ Installation methods:
     ```
 
 === "Linux / macOS (Direct Download)"
-    Get the `rebar3` binary from the [official website](https://rebar3.org/). Place the downloaded `rebar3` file in your system's `PATH` (e.g., `/usr/local/bin`) and make it executable (`chmod +x reba[...]
+    Get the `rebar3` binary from the [official website](https://rebar3.org/). Place the downloaded `rebar3` file in your system's `PATH` (e.g., `/usr/local/bin`) and make it executable (`chmod +x [...]`
 
 <!-- === "asdf (Recommended)"
     If using `asdf`, you can install it via the `rebar` plugin:
@@ -147,8 +147,10 @@ The simplest way to start a HyperBEAM node for development or testing is using `
 rebar3 shell
 ```
 
-!!! note
-    For current process operations, start HyperBEAM with the `genesis_wasm` profile by running `rebar3 as genesis_wasm shell`.
+<div class="admonition note">
+<p class="admonition-title">Note</p>
+<p>For current process operations, start HyperBEAM with the <code>genesis_wasm</code> profile by running <code>rebar3 as genesis_wasm shell</code>.</p>
+</div>
 
 This command:
 
@@ -183,7 +185,7 @@ rebar3 as rocksdb, genesis_wasm shell
 
 ## Node Configuration
 
-HyperBEAM offers various configuration options (port, key file, data storage, logging, etc.). These are primarily set using a `config.flat` file and can be overridden by environment variables or comma[...]
+HyperBEAM offers various configuration options (port, key file, data storage, logging, etc.). These are primarily set using a `config.flat` file and can be overridden by environment variables or [...]
 
 See the dedicated [Configuring Your HyperBEAM Node](./configuring-your-machine.md) guide for detailed information on all configuration methods and options.
 
@@ -199,7 +201,7 @@ A JSON response containing node information indicates success.
 
 ## Running for Production (Mainnet)
 
-While you can connect to the main AO network using the `rebar3 shell` for testing purposes (potentially using specific configurations or helper functions like `hb:start_mainnet/1` if available and app[...]
+While you can connect to the main AO network using the `rebar3 shell` for testing purposes (potentially using specific configurations or helper functions like `hb:start_mainnet/1` if available an[...]
 
 **1. Build the Release:**
 
@@ -217,7 +219,7 @@ This command compiles the project and packages it along with the Erlang Runtime
 
 **2. Configure the Release:**
 
-Navigate into the release directory (e.g., `cd _build/default/rel/hb`). Ensure you have a correctly configured `config.flat` file here. See the [configuration guide](./configuring-your-machine.md) for[...]
+Navigate into the release directory (e.g., `cd _build/default/rel/hb`). Ensure you have a correctly configured `config.flat` file here. See the [configuration guide](./configuring-your-machine.md[...] 
 
 **3. Start the Node:**
 

From 0e8180cbc3be4e32f2447aef61abbb32353b9ec3 Mon Sep 17 00:00:00 2001
From: JonnyRingo <92886988+Jonny-Ringo@users.noreply.github.com>
Date: Thu, 14 May 2026 08:30:28 -0700
Subject: [PATCH 15/15] Update note formatting in running-a-hyperbeam-node.md

Replaced HTML admonition with Markdown note for clarity.
---
 docs/run/running-a-hyperbeam-node.md | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/docs/run/running-a-hyperbeam-node.md b/docs/run/running-a-hyperbeam-node.md
index f798c5aaf..a8c06cda2 100644
--- a/docs/run/running-a-hyperbeam-node.md
+++ b/docs/run/running-a-hyperbeam-node.md
@@ -147,10 +147,8 @@ The simplest way to start a HyperBEAM node for development or testing is using `
 rebar3 shell
 ```
 
-<div class="admonition note">
-<p class="admonition-title">Note</p>
-<p>For current process operations, start HyperBEAM with the <code>genesis_wasm</code> profile by running <code>rebar3 as genesis_wasm shell</code>.</p>
-</div>
+>[!NOTE]
+>For current process operations, start HyperBEAM with the <code>genesis_wasm</code> profile by running <code>rebar3 as genesis_wasm shell</code>.
 
 This command: