(no commit message)

diff --git a/openpower/ISA_WG/Board_letter_26mar2021.mdwn b/openpower/ISA_WG/Board_letter_26mar2021.mdwn
index d78c646dcc87bf1d6459033656145b6d3e11b251..1bc208896e16fa13f40c636f424d3bd467903755 100644 (file)
--- a/openpower/ISA_WG/Board_letter_26mar2021.mdwn
+++ b/openpower/ISA_WG/Board_letter_26mar2021.mdwn
@@ -53,7 +53,7 @@ At this point however it is important to provide some context as to why RED Semi
 
 Therefore whilst we in LibreSOC as individuals are the actual non-affiliated architects of the ISA Extensions, RED Semiconductor will not own the Copyright but will be in exactly the same boat as any other Corporation!
 
-The key person acting as the bridge between both world will be myself (Luke Legton), and I will ensure *and require* that RED Semiconductor provides adequate funds and resources for the long haul, in order to not only see through the proposals but also ensure that the associated toolchains, test duites, documentation etc. are properly written and maintained, long-term.  Yet I stress, again, that despite committing the financial resources,  RED Semiconductor will *not* own the Copyright or any patents on LibreSOC work.
+The key person acting as the bridge between both world will be myself (Luke Leighton), and I will ensure *and require* that RED Semiconductor provides adequate funds and resources for the long haul, in order to not only see through the proposals but also ensure that the associated toolchains, test duites, documentation etc. are properly written and maintained, long-term.  Yet I stress, again, that despite committing the financial resources,  RED Semiconductor will *not* own the Copyright or any patents on LibreSOC work.
 
 My question to you is, therefore: what is the best way forward, here?  What "vehicle" or arrangement would be suitable that takes into account these unique circumstances? Would a conference call perhape be a good idea to discuss a way forward?