diff --git a/Design:-msg.parts---description-of-usage.md b/Design:-msg.parts---description-of-usage.md
index 7d62f28..1134406 100644
--- a/Design:-msg.parts---description-of-usage.md
+++ b/Design:-msg.parts---description-of-usage.md
@@ -90,7 +90,7 @@ If the condition evaluates to true for an input message, the message is send to
 
  - Should it have two outputs ? one for things that match and one for things that don't ? Would save having two nodes if both types of message are required. (DCJ - I think yes)
  - Is javascript the right expression language to use (given we already have jsonata etc - is another one a good idea ?)
- - Tail mode - is end only triggered by comparison to `count` ? I think yes.
+ - Tail mode - is end only triggered by comparison to `count` ? (DCJ - I think yes.)
  - Head mode - if n messages don't arrive for that group - drop any currently accumulated ? send part msg ? eg if we ask for 10 - and a group of 5 arrive... does it get sent ? or dropped ? (DCJ - I think send)
  - Apart from head and tail modes - this is similar to the switch node - should that be enhanced to handle parts instead ? (DCJ - I think no - but ?)
  - In non head and tail mode this node could work on messages without `parts` also. Should that be supported ? (DCJ - I think yes)