@@ -22,15 +22,15 @@ namespace Adaptive.SimpleBinaryEncoding.ir
2222 /// <summary> 
2323 /// Class to encapsulate a token of information for the message schema stream. This Intermediate Representation (IR) 
2424 /// is intended to be language, schema, platform independent. 
25-  /// <p/>  
25+  /// 
2626 /// Processing and optimization could be run over a list of Tokens to perform various functions 
2727 /// <ul> 
2828 /// <li>re-ordering of fields based on size</li> 
2929 /// <li>padding of fields in order to provide expansion room</li> 
3030 /// <li>computing offsets of individual fields</li> 
3131 /// <li>etc.</li> 
3232 /// </ul> 
33-  /// <p/>  
33+  /// 
3434 /// IR could be used to generate code or other specifications. It should be possible to do the 
3535 /// following: 
3636 /// <ul> 
@@ -39,18 +39,18 @@ namespace Adaptive.SimpleBinaryEncoding.ir
3939 /// <li>generate a GPB spec from IR</li> 
4040 /// <li>etc.</li> 
4141 /// </ul> 
42-  /// <p/>  
42+  /// 
4343 /// IR could be serialized to storage or network via code generated by SBE. Then read back in to 
4444 /// a List of <seealso cref="Token"/>s. 
45-  /// <p/>  
45+  /// 
4646 /// The entire IR of an entity is a <see cref="List{Token}"/>. The order of this list is 
4747 /// very important. Encoding of fields is done by nodes pointing to specific encoding <seealso cref="PrimitiveType"/> 
4848 /// objects. Each encoding node contains size, offset, byte order, and <seealso cref="Encoding"/>. Entities relevant 
4949 /// to the encoding such as fields, messages, repeating groups, etc. are encapsulated in the list as nodes 
5050 /// themselves. Although, they will in most cases never be serialized. The boundaries of these entities 
5151 /// are delimited by BEGIN and END <seealso cref="Adaptive.SimpleBinaryEncoding.ir.Signal"/> values in the node <seealso cref="Encoding"/>. 
5252 /// A list structure like this allows for each concatenation of encodings as well as easy traversal. 
53-  /// <p/>  
53+  /// 
5454 /// An example encoding of a message headerStructure might be like this. 
5555 /// <ul> 
5656 /// <li>Token 0 - Signal = BEGIN_MESSAGE, schemaId = 100</li> 
@@ -59,7 +59,7 @@ namespace Adaptive.SimpleBinaryEncoding.ir
5959 /// <li>Token 3 - Signal = END_FIELD</li> 
6060 /// <li>Token 4 - Signal = END_MESSAGE</li> 
6161 /// </ul> 
62-  /// <p/>  
62+  /// 
6363 /// </summary> 
6464 public  class  Token 
6565 { 
0 commit comments