fix typos

diff --git a/openpower/ISA_WG/Board_letter_26mar2021.mdwn b/openpower/ISA_WG/Board_letter_26mar2021.mdwn
index c63cb7472f5051c47b35757191324160b0d4d80c..8c30bd1387fe791c058474085c28ddd75f745bc8 100644 (file)
--- a/openpower/ISA_WG/Board_letter_26mar2021.mdwn
+++ b/openpower/ISA_WG/Board_letter_26mar2021.mdwn
@@ -6,6 +6,7 @@
 edit history:
 
 * 25mar2021 first revision
+* fix typos
 
 to be sent to:
 
@@ -30,7 +31,7 @@ Normally, such huge ISA development efforts would be instigated, organised and f
 
 From reading the PowerISA v3.0C sections we have learned and taken on board that a "Sandbox" opcode exists (EXT22) which is intended for "small private extensions" to the OpenPOWER ISA, and the expectation that these extensions not be supported by upstream tool-chains is something we agree wholeheartedly with,
 
-The problem is that our Bitmanipulation Extension alone, needed for Audio/Video and cryptographic workloads, struggles to fit into that space, and we have not yet added Custom 3D opcodes or the IEEE754 Transcendentals (SIN, COS).
+The problem is that our Bit-Manipulation Extension alone, needed for Audio/Video and Cryptographic workloads, struggles to fit into that space, and we have not yet added Custom 3D opcodes or the IEEE754 Transcendentals (SIN, COS).
 
 http://libre-soc.org/openpower/bitmanip