message: fix list markup
diff: @@ -25,16 +25,16 @@ number versus int is esential for bitwise operations), language style and older
  ### Rules
  -* Keep all types as close to the original as possible.
  -* Keep detailed type information in comments where applicable (example int will become `number /*int*/`) as the code is extensively using bitwise operations that can overflow.
  -* Use TypedArray whenever possible (example `int[]` will become `Int32Array`) - see below for more info.
  -* Use constructor property whenever possible.
  -* Take care of array initialisation with capacity, especially when using length and push later on. Basically only use when setting with index accesor only .
  -* Use utility classes to implement platform dependencies (like `System` or `Arrays`), avoid inline implementation for anything that is not trivial.
  -* Use single class|enum|interface per module, export with default. Move internal classes to separate modules if used from other modules.
  -* Package level visibility will transform to public to avoid module complexity.
  -* Keep enum as similar with the original interface as possible (transform to class and use static fields for enum values).
  -* Allways use `===` for `==` to avoid gliches from type transforms.
  +- Keep all types as close to the original as possible.
  +- Keep detailed type information in comments where applicable (example int will become `number /*int*/`) as the code is extensively using bitwise operations that can overflow.
  +- Use TypedArray whenever possible (example `int[]` will become `Int32Array`) - see below for more info.
  +- Use constructor property whenever possible.
  +- Take care of array initialisation with capacity, especially when using length and push later on. Basically only use when setting with index accesor only .
  +- Use utility classes to implement platform dependencies (like `System` or `Arrays`), avoid inline implementation for anything that is not trivial.
  +- Use single class|enum|interface per module, export with default. Move internal classes to separate modules if used from other modules.
  +- Package level visibility will transform to public to avoid module complexity.
  +- Keep enum as similar with the original interface as possible (transform to class and use static fields for enum values).
  +- Allways use `===` for `==` to avoid gliches from type transforms.
  ## Types
  