(no commit message)

diff --git a/openpower/sv/overview/discussion.mdwn b/openpower/sv/overview/discussion.mdwn
index c6838d30df3149523185ffafc1db0428113ec1ea..843042461c47ee2e6c4c700bfcde35bdd7863c02 100644 (file)
--- a/openpower/sv/overview/discussion.mdwn
+++ b/openpower/sv/overview/discussion.mdwn
@@ -187,9 +187,12 @@ The meaning of "Architecturally" is that the programmer sees one definition,
 where that definition has absolutely no connection or imposition on precisely
 how the implementation is implemented (internally), **except** to comply with
 the definition as far as **external** usage is concerned (programs).
+Mathematics uses the term "Topologically Homeomorphic" to refer to the
+relationship between external (specification, programs) and any given
+(internal) hardware implementation.
 
 This is the *canonical* Architectural definition of the regfile
-asuming a Little-Endian system, in the c programming language:
+assuming a Little-Endian system, in the c programming language:
 
     #pragma pack
     typedef union {
@@ -203,7 +206,8 @@ asuming a Little-Endian system, in the c programming language:
     elreg_t int_regfile[128];
 
 Where things become complicated is how to transliterate the above into
-MSB0 numbering, which significantly harms understanding as to how
+MSB0 numbering, which unfortunately significantly harms understanding
+as to how
 to clearly access elememts within the regfile, and thus requires
 very careful an comprehensive and explanation.
 We start with some definitions: