separate section for meeting

diff --git a/updates/022_2020feb14_openpower_eula_released.mdwn b/updates/022_2020feb14_openpower_eula_released.mdwn
index b70cc9698e2e2d149e9c11f3710898442fe4cd12..eb57168bf8c6b1feed312c34c23e9231015c1ee4 100644 (file)
--- a/updates/022_2020feb14_openpower_eula_released.mdwn
+++ b/updates/022_2020feb14_openpower_eula_released.mdwn
@@ -109,7 +109,8 @@ funding quite a lot of RISC-V projects, and none of them had any issues.
 I asked him a very simple question: "how many of those projects are
 simply *implementing* existing RISC-V Standards?", and he replied, "all
 of them".  I then asked, "how many of those projects are *innovating*,
-developing alternative extensions to RISC-V?" That was the point at which
+developing alternative extensions to what is dictated by the RISC-V
+Foundation?" With the answer being "none", *that* was the point at which
 he understood the extent of the problem, and how the RISC-V Foundation -
 and its members - are at risk of violating EU anti-trust legislation.