diff --git a/fm/msg-schema-implementers-draft.adoc b/fm/msg-schema-implementers-draft.adoc
index 855338a..083006f 100644
--- a/fm/msg-schema-implementers-draft.adoc
+++ b/fm/msg-schema-implementers-draft.adoc
@@ -11,7 +11,7 @@ Reference: Message schema https://docs.google.com/document/d/1jS2eyBXV49hs29WSAJ
 
 Consume messages consisting of outer resourceTypes:
 
-*FMperson*
+=== *FMperson*
 
 ==== eventType "create":
 These messages should be processed into COmanage person add actions where a person with a matching ePPN and/or email address does not exist in COmanage. The ePPN and/or email address sent in the message should be mapped into upstream / source system ePPN and email address in the new person record.
@@ -21,7 +21,7 @@ These messages should be processed into COmanage person update actions where a p
 
 In the case where a person record does not yet exist for this person, the message should be treated as an eventType of "create".
 
-*FMrole*
+=== *FMrole*
 
 ==== eventType "create"
 These messages should be processed into Grouper using Grouper API calls. They should result in groups within the folder/group structure
@@ -47,7 +47,7 @@ An existing group matching the full computed group path determined using the fol
 ==== eventType "personremove"
 An existing group matching the full computed group path determined using the folder/group structure noted in the "create" eventType for this resourceType should be treated as the target of this message. Any FMperson resourceType messages embedded within the message should be removed from existing group membership. In the event that a group cannot be found matching the computed group path, the message should be treated as an eventType of "create" and a WARN log event should be generated noting this, along with appropriate diagnostic details.
 
-*FMorg*
+=== *FMorg*
 
 These messages are only relevant in the context of a wrapping FMrole resourceType message, for the time being.