fix: Fixed spelling in examples/mx readme

Signed-off-by: Brandon Groth <brandon.m.groth@gmail.com>

Author: BrandonGroth

.spellcheck-en-custom.txt

@@ -27,8 +27,10 @@ dequantization
 dq
 DQ
 dev
+dtype
 eval
 fms
+fmsmo
 fp
 FP
 FP8Arguments
@@ -127,5 +129,9 @@ xs
 zp
 microxcaling
 MX
+mx
 MXINT
+mxint
 MXFP
+mxfp
+OCP

examples/MX/README.md

@@ -1,5 +1,5 @@
-# `microscaling` Examples Using a Toy Model and Direct Quantization (DQ)
-Microscaling, or "MX", format, such as `MXFP8`, is a different numeric format compared to commonly used FP8 formats. For example, PyTorch provides two FP8 formats, which are 1 sign bit, 4 exponent bits, and 3 mantissa bits (denoted as `e4m3`) or 1 sign bit, 5 exponent bits, and 2 mantissa bits (`e5m2`), see our other [FP8 example](../FP8_QUANT/README.md) for more details.  On the other hand, all the `mx` formats are group-based data structure where each member of the group is using the specified format, e.g. FP8 for MXFP8, while each group has a shared (usually 8-bit) "scale".  Group size could be as small as 32 or 16, depending on hardware design.  One may consider each MXFP8 number actually requires 8.25 bits (when group size is 32) instead of 8 bits.  More details about microscaling can be found in [this OCP document](https://www.opencompute.org/documents/ocp-microscaling-formats-mx-v1-0-spec-final-pdf).
+# `microxcaling` Examples Using a Toy Model and Direct Quantization (DQ)
+Microxcaling, or "MX", format, such as `MXFP8`, is a different numeric format compared to commonly used FP8 formats. For example, PyTorch provides two FP8 formats, which are 1 sign bit, 4 exponent bits, and 3 mantissa bits (denoted as `e4m3`) or 1 sign bit, 5 exponent bits, and 2 mantissa bits (`e5m2`), see our other [FP8 example](../FP8_QUANT/README.md) for more details.  On the other hand, all the `mx` formats are group-based data structure where each member of the group is using the specified format, e.g. FP8 for MXFP8, while each group has a shared (usually 8-bit) "scale".  Group size could be as small as 32 or 16, depending on hardware design.  One may consider each MXFP8 number actually requires 8.25 bits (when group size is 32) instead of 8 bits.  More details about Microxcaling can be found in [this OCP document](https://www.opencompute.org/documents/ocp-microxcaling-formats-mx-v1-0-spec-final-pdf).
 
 Here, we provide two simple examples of using MX format in `fms-mo`.