Name no node in nodered's, netcheck's, telegram's and nfs-server's fixtures (issue 1838)

2026-10-22 21:26:05 +02:00
parent 2f05e70734
commit d33e6baa73
8 changed files with 52 additions and 52 deletions
@@ -8,7 +8,7 @@
 //
 // **Which broker nodes are the mesh's.** Never guessed: a flow may talk to a broker that has nothing
 // to do with this mesh. The step owns the node it creates itself (id `mesh-mqtt-topic`, "mesh:
-// mqtt-topic") and the ones an assignment names in settings (`mqtt.brokers`: node ids — how ace's
+// mqtt-topic") and the ones an assignment names in settings (`mqtt.brokers`: node ids — how node-a's
 // existing broker node, which every one of its MQTT flows uses, is handed over). With none named and
 // none made yet, it makes one, so a fresh Node-RED has a broker the flows can pick.
 //