From: lkcl <lkcl@web>
Date: Mon, 27 Mar 2023 23:51:34 +0000 (+0100)
Subject: (no commit message)
X-Git-Tag: opf_rfc_ls001_v3~21
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=f3f626201ec68f0520e2bb9565969b2f3eca5a79;p=libreriscv.git

---

diff --git a/openpower/sv/rfc/ls009.mdwn b/openpower/sv/rfc/ls009.mdwn
index 022193bf0..fe84451a2 100644
--- a/openpower/sv/rfc/ls009.mdwn
+++ b/openpower/sv/rfc/ls009.mdwn
@@ -133,7 +133,7 @@ implementations may introduce
 latency, so should realistically be used only where it is worthwhile.
 Given that even with latency the fact that up to 127 operations
 can be requested to be issued (from a single instruction) it should
-be clear that REMAP should not be dismissed for *potential* latency alone.
+be clear that REMAP should not be dismissed for *possible* latency alone.
 Commonly-used patterns such as Matrix Multiply, DCT and FFT have
 helper instruction options which make REMAP easier to use.