diff --git a/markdown/docs/supporting-articles/using-filler-noise.md b/markdown/docs/supporting-articles/using-filler-noise.md
index e06b155..c3c93af 100644
--- a/markdown/docs/supporting-articles/using-filler-noise.md
+++ b/markdown/docs/supporting-articles/using-filler-noise.md
@@ -2,7 +2,7 @@
 
 Sometimes in conversational AI scenarios there may be significant latency while the remote application processes a user response and is determing the next action to take.  In these scenarios it is common to play a typing sound or other audio to provide an audio cue to the caller that the system is processing the response, that the agent is thinking or retrieving, etc.  
 
-Support for "filler noise" can enabled either at the session level using the `config.fillerNoise` property or at the individual `gather` level using the same property.  In the example below, we set a session-wide setting for filler noise (in the form of a typing sound) to kick in after waiting 2 seconds for the remote app to respond to user input.
+Support for "filler noise" can enabled either at the session level using the [config.fillerNoise](/docs/webhooks/config) property or at the individual [gather](/docs/webhooks/gather) level using the same property.  In the example below, we set a session-wide setting for filler noise (in the form of a typing sound) to kick in after waiting 2 seconds for the remote app to respond to user input.
 
 ```js
 /* websocket application */
diff --git a/markdown/docs/ws/command.md b/markdown/docs/ws/command.md
index 040f835..a13f048 100644
--- a/markdown/docs/ws/command.md
+++ b/markdown/docs/ws/command.md
@@ -22,8 +22,10 @@ The `command` property must be one of the values shown below.
 |conf:mute-status|mute or unmute all non-moderator conference legs|data must include a `conf_mute_status` property with a value of either 'mute' or 'unmute'|
 |conf:hold-status|place a conference leg on hold or take off hold|data must include a `conf_hold_status` property with a value of either 'hold' or 'unhold'|
 |listen:status|Change the status of a listen stream|data must include a `listen_status` property with a value of 'pause' or 'resume'|
+|record|manage call recording that is done via SIPREC to a remote recording server|data must include an `action` with one of "startCallRecording", "stopCallRecording", "pauseCallRecording", or "resumeCallRecording".  When starting a recording you must also supply "recordingID" and  "siprecServerURL".  You may optionally supply a `headers` object with custom headers to be sent to the remote SIPREC recording server.|
 |whisper|Play a whisper prompt to the caller (i.e only one party hears the prompt)|data must include a `whisper` property that can be an array of say or play verbs|
 |sip:request|Send a SIP INFO, NOTIFY, or MESSAGE request to the far end party|data must include a 'method' property (allowed values: 'INFO', 'NOTIFY', 'MESSAGE') and can include 'content_type', 'content', and 'headers' properties.|
+|dub|add, remove or operate on a dub track.|The data must include the properties defined for the [dub](./docs/webhooks/dub) verb|
 
 
 > Note: In the data payload when `redirect` is used, each jambonz verb in the `data` array may optionally include an `id` property.  If present, jambonz will provide `verb:status` notifications when the verb starts and ends execution.