[COMMITTED] doc: fix typo

[Mohammad-Reza Nabipoor]

2023-04-13  Mohammad-Reza Nabipoor  <mnabipoor@gnu.org>

        * doc/poke.texi (Integral Structs): s/little-endian/big-endian/
        when talking about how gcc encodes bit fields.
---
 ChangeLog     | 5 +++++
 doc/poke.texi | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/ChangeLog b/ChangeLog
index 164ec496..e0baa200 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2023-04-13  Mohammad-Reza Nabipoor  <mnabipoor@gnu.org>
+
+       * doc/poke.texi (Integral Structs): s/little-endian/big-endian/
+       when talking about how gcc encodes bit fields.
+
 2023-03-28  Jose E. Marchesi  <jemarch@gnu.org>
 
        * etc/poke.rec: Remove priority fields.
diff --git a/doc/poke.texi b/doc/poke.texi
index b6fcc90c..ef7f8d77 100644
--- a/doc/poke.texi
+++ b/doc/poke.texi
@@ -11776,7 +11776,7 @@ defined, and ultimately what order to use is up to the 
compiler,
 @code{src_reg} in the most significant nibble of the byte and
 @code{dst_reg} in the least significant nibble of the byte when
 compiling for a little-endian target, and the other way around when
-compiling for a little-endian target. (I may have had that wrong, this
+compiling for a big-endian target. (I may have had that wrong, this
 always confuses me.)
 
 How could we encode the C struct regs in Poke?  Let's see.
-- 
2.40.0