diff --git a/specification/app_glossary.xml b/specification/app_glossary.xml
index 2c4ac47..32dc97a 100644
--- a/specification/app_glossary.xml
+++ b/specification/app_glossary.xml
@@ -197,7 +197,7 @@ xml:id="dbdoclet.50655246_33489">
GNU Compiler Collection
-
+
GEP
@@ -293,7 +293,7 @@ xml:id="dbdoclet.50655246_33489">
Little-endian
-
+
LEP
diff --git a/specification/ch_2.xml b/specification/ch_2.xml
index f9c389c..716434e 100644
--- a/specification/ch_2.xml
+++ b/specification/ch_2.xml
@@ -6935,12 +6935,13 @@ lvx v1, 0, r10
a TOC pointer, and not all functions must preserve the existing value
of r2. See for more
information.
- All functions have a global entry point (GEP) available to any
+ All functions have a global entry point (GEP) available to any
caller and pointing to the beginning of the prologue. Some functions
may have a secondary entry point to optimize the cost of TOC pointer
management. In particular, functions within a common module sharing the
same TOC base value in r2 may be entered using a secondary entry point
- (the local entry point or LEP) that may bypass the code that loads a
+ (the local entry point or
+ LEP) that may bypass the code that loads a
suitable TOC pointer value into the r2 register. When a dynamic or
global linker transfers control from a function to another function in
the same module, it
@@ -6955,7 +6956,9 @@ lvx v1, 0, r10
entry-point address. Code at the global entry point of a function that also has a local entry
point can assume that
- register r12 points to the GEP.
+ register r12 points to the GEPglobal
+ entry point.
However, code at the global entry point of a function that does not
have a separate local entry point cannot make any assumptions about
the values of either r2 or 12.