Minor documentation updates

Author: endurodave

README.md

@@ -311,7 +311,7 @@ auto conn2 = dmq::DataBus::Subscribe<int>("status", [](int s) {
 
 <img src="docs/dmq-spy-screenshot.png" alt="DelegateMQ Spy Screenshot" style="max-width: 800px; width: 100%;">
 
-To use the Spy tool, simply enable the `DMQ_DATABUS_SPY` option in your application's build and start the `dmq-spy` console. See the [DelegateMQ-Tools repository](https://github.com/endurodave/DelegateMQ-Tools) for implementation details.
+To use the Spy tool, simply enable the `DMQ_DATABUS_TOOLS` option in your application's build and start the `dmq-spy` console. See the [DelegateMQ-Tools repository](https://github.com/endurodave/DelegateMQ-Tools) for implementation details.
 
 # Modular Architecture
 

docs/DETAILS.md

@@ -597,7 +597,7 @@ The sender calls `(*m_channel)(value)` or `RemoteInvokeWait(*m_channel, value)`.
 
 **[DelegateMQ Spy](https://github.com/endurodave/DelegateMQ-Tools)** is a standalone TUI diagnostic tool that provides a "Software Logic Analyzer" view of the DataBus. It captures, filters, and displays all bus traffic in real-time without blocking the main application thread. 
 
-To enable spy support in a sample project, build with `-DDMQ_DATABUS_SPY=ON`. This activates an asynchronous "Spy Bridge" that exports packets over UDP to the standalone console.
+To enable spy support in a sample project, build with `-DDMQ_DATABUS_TOOLS=ON`. This activates an asynchronous "Spy Bridge" that exports packets over UDP to the standalone console.
 
 ### Example: Local Pub/Sub
 

example/sample-projects/databus-multicast/README.md

@@ -40,10 +40,10 @@ This example demonstrates a distributed system using `dmq::DataBus` over **UDP M
 This project includes optional support for the **DelegateMQ Spy Console**. When enabled, the application exports all bus traffic to a multicast group, allowing multiple consoles to monitor the system at once.
 
 ### Enabling Spy
-To enable the spy bridge, configure the project with the `DMQ_DATABUS_SPY` option set to `ON`:
+To enable the spy bridge, configure the project with the `DMQ_DATABUS_TOOLS` option set to `ON`:
 
 ```bash
-cmake -B build -DDMQ_DATABUS_SPY=ON .
+cmake -B build -DDMQ_DATABUS_TOOLS=ON .
 cmake --build build --config Release
 ```
 

example/sample-projects/databus-shapes/README.md

@@ -37,7 +37,7 @@ The **Shapes Demo** is a graphical demonstration of the **DelegateMQ DataBus** c
 This project is fully integrated with the **DelegateMQ Spy Console**. 
 
 ### Enabling the Spy Bridge
-The server-side bridge is enabled by default in the `CMakeLists.txt` via the `DMQ_DATABUS_SPY` option. To monitor the raw coordinate data flowing through the bus:
+The server-side bridge is enabled by default in the `CMakeLists.txt` via the `DMQ_DATABUS_TOOLS` option. To monitor the raw coordinate data flowing through the bus:
 
 1. Start the **Spy Console** from the `DelegateMQ-Tools` project:
    ```bash

example/sample-projects/databus/README.md

@@ -44,10 +44,10 @@ This project includes optional support for the **DelegateMQ Spy Console**. When
 - `Bitsery` must be available in the workspace (fetched via `01_fetch_repos.py`).
 
 ### Enabling Spy
-To enable the spy bridge, configure the project with the `DMQ_DATABUS_SPY` option set to `ON`:
+To enable the spy bridge, configure the project with the `DMQ_DATABUS_TOOLS` option set to `ON`:
 
 ```bash
-cmake -B build -DDMQ_DATABUS_SPY=ON .
+cmake -B build -DDMQ_DATABUS_TOOLS=ON .
 cmake --build build --config Release
 ```