From d3eceb6d6c61e507304e5f85cb196405b99148f3 Mon Sep 17 00:00:00 2001
From: Fred <fndecker@gmail.com>
Date: Fri, 3 Mar 2023 21:41:22 -0500
Subject: [PATCH] Update ThrottleAssists.md

---
 Release_Notes/ThrottleAssists.md | 46 +++++++++++++++++---------------
 1 file changed, 24 insertions(+), 22 deletions(-)

diff --git a/Release_Notes/ThrottleAssists.md b/Release_Notes/ThrottleAssists.md
index e704b42..2055618 100644
--- a/Release_Notes/ThrottleAssists.md
+++ b/Release_Notes/ThrottleAssists.md
@@ -13,14 +13,14 @@ The conventional turnout definition commands and the ```<H>``` responses do not
 ```<JT>``` command returns a list of turnout ids. The throttle should be uninterested in the turnout technology used but needs to know the ids it can throw/close and monitor the current state.  
 e.g.  response ```<jT 1 17 22 19>``` 
 
-```<JT 17>`` requests info on turnout 17.  
-e.g. response ```<jT 17 T "Coal yard exit">``` or ```<jT 17 C "Coal yard exit">``  
-(T=thrown, C=closed)  
-or ```<jT 17 C "">``` indicating turnout description not given.  
+```<JT 17>`` requests info on turnout 17.\
+e.g. response ```<jT 17 T "Coal yard exit">``` or ```<jT 17 C "Coal yard exit">``\
+(T=thrown, C=closed)\
+or ```<jT 17 C "">``` indicating turnout description not given.\
 or ```<jT 17 X>``` indicating turnout unknown (or possibly hidden.)  
   
-Note: It is still the throttles responsibility to monitor the status broadcasts.  
-(TBD I'm thinking that the existing broadcast is messy and needs cleaning up)  
+Note: It is still the throttles responsibility to monitor the status broadcasts.\
+(TBD I'm thinking that the existing broadcast is messy and needs cleaning up)\
 However, I'm not keen on dynamically created/deleted turnouts so I have no intention of providing a command that indicates the turnout list has been updated since the throttle started.  
 Also note that turnouts marked in EXRAIL with the HIDDEN keyword instead of a "description" will NOT show up in these commands. 
 
@@ -30,13 +30,13 @@ Also note that turnouts marked in EXRAIL with the HIDDEN keyword instead of a "d
 
  A throttle need to know which EXRAIL Automations and Routes it can show the user.  
  
- ```<JA>``` Returns a list of Automations/Routes  
- e.g. ```<jA 13 16 23>```  
- Indicates route/automation ids.  
- Information on each route needs to be obtained by  
- ```<JA 13>```  
- returns e.g. ```<jA 13 R "description">``` for a route  
- or  ```<jA 13 A "description">``` for an automation.  
+ ```<JA>``` Returns a list of Automations/Routes\
+ e.g. ```<jA 13 16 23>```\
+ Indicates route/automation ids.\
+ Information on each route needs to be obtained by\
+ ```<JA 13>```\
+ returns e.g. ```<jA 13 R "description">``` for a route\
+ or  ```<jA 13 A "description">``` for an automation.\
  or ```<jA 13 X>``` for id not found  
  
  What's the difference?
@@ -45,14 +45,15 @@ Also note that turnouts marked in EXRAIL with the HIDDEN keyword instead of a "d
 A *Route* is just a call to an **EXRAIL ROUTE**, traditionally to set some turnouts or signals but can be used to perform any kind of EXRAIL function... but its not expecting to know the loco.
  
 Thus, a route can be triggered by sending in for example ```</START 13>```. 
+
+An *Automation* is a handoff of the last accessed loco id to an EXRAIL AUTOMATION which would typically drive the loco away.
  
- An *Automation* is a handoff of the last accessed loco id to an EXRAIL AUTOMATION which would typically drive the loco away.
- 
-   Thus an Automation expects a start command with a cab id
+   Thus an Automation expects a start command with a cab id\
    e.g. ```</START 13 3>```
 
 
-   Roster Information:
+   Roster Information
+   ^^^^^^^^^^^^^^^^^^
    The ```<JR>``` command requests a list of cab ids from the roster.
    e.g. responding ```<jR 3 200 6336>```
    or <jR> for none. 
@@ -63,7 +64,8 @@ Thus, a route can be triggered by sending in for example ```</START 13>```.
    Refer to EXRAIL ROSTER command for function map format.
 
 
-  Obtaining throttle status.
+  Obtaining throttle status
+  ^^^^^^^^^^^^^^^^^^^^^^^^^^
   ```<t cabid>```  Requests a deliberate update on the cab speed/functions in the same format as the cab broadcast.
      ```<l cabid slot speedbyte functionMap>```
       Note that a slot of -1 indicates that the cab is not in the reminders table and this comand will not reserve a slot until such time as the cab is throttled.
@@ -72,10 +74,10 @@ Thus, a route can be triggered by sending in for example ```</START 13>```.
   COMMANDS TO AVOID
  ======================
 
-  ```<f cab func1 func2>```     Use ```<F cab function 1/0>```  
-  ```<t  slot cab speed dir>``` Just drop the slot number  
-  ```<T commands>``` other than ```<T id 0/1>```  
-  ```<s>```  
+  ```<f cab func1 func2>```     Use ```<F cab function 1/0>```\
+  ```<t  slot cab speed dir>``` Just drop the slot number\
+  ```<T commands>``` other than ```<T id 0/1>```\
+  ```<s>```\
   ```<c>```