Fixed clt opcode page (#2230)

The stack transitional order is messed up that you can see the problem from here: https://docs.microsoft.com/en-us/dotnet/api/system.reflection.emit.opcodes.clt?view=netframework-4.7.2

Author: TheCowboyHermit

xml/System.Reflection.Emit/OpCodes.xml

@@ -2722,13 +2722,15 @@
 |------------|---------------------|-----------------|  
 |FE 04|clt|Pushes 1 if `value1` is less than `value2`; else pushes 0.|  
 
- The stack transitional behavior, in sequential order, is: `value1` is pushed onto the stack.  
+ The stack transitional behavior, in sequential order, is: 
+
+1.  `value1` is pushed onto the stack.  
 
-1.  `value2` is pushed onto the stack.  
+2.  `value2` is pushed onto the stack.  
 
-2.  `value2` and `value1` are popped from the stack; `clt` tests if `value1` is less than `value2`.  
+3.  `value2` and `value1` are popped from the stack; `clt` tests if `value1` is less than `value2`.  
 
-3.  If `value1` is less than `value2`, 1 is pushed onto the stack; otherwise 0 is pushed onto the stack.  
+4.  If `value1` is less than `value2`, 1 is pushed onto the stack; otherwise 0 is pushed onto the stack.  
 
  The `clt` instruction compares `value1` and `value2`. If `value1` is strictly less than `value2`, then an `int32` value of 1 is pushed on the stack. Otherwise, an `int32` value of 0 is pushed on the stack.  
 
@@ -14216,4 +14218,4 @@ callvirt m
       </Docs>
     </Member>
   </Members>
-</Type>
+</Type>