fix: < and > in headers are turned into tags

src/documents/IoCReferences.md

@@ -157,7 +157,7 @@ following the context name in the reference expression are not empty, the framew
 Components which are not in scope for resolution from the reference site (shown as a green pentagon) are shown as blue
 squares.
 
-## Examples of {<componentRef>}
+## Examples of {\<componentRef\>}
 
 In the example below, the IoC reference `{that}` refers to the component in which it is being used.
 
@@ -230,7 +230,7 @@ fluid.defaults("fluid.prefs.enactor.tableOfContents", {
 });
 ```
 
-## Examples of {<componentRef>}.<path to member>
+## Examples of {\<componentRef\>}.\<path to member\>
 
 The example below includes several IoC references. All of them are inside a subcomponent declaration and all include
 `{controllers}`, which in this case is a reference to the parent component. Specifically:
@@ -289,7 +289,7 @@ fluid.defaults("fluid.moduleLayoutHandler", {
 });
 ```
 
-## Examples of {<iocss expression>}
+## Examples of {\<iocss expression\>}
 
 The example below uses an [IoCSS](IoCSS.md) expression `{that > moreText}.options.selectors.images`. The expression
 refers to the `images` selector in the `moreText` subcomponent that is a direct descendent of the current component.