[llvm] fcc8802 - [Docs] Fix typo in GetElementPtr.rst (#127393)

[via llvm-commits]

Author: Omar Hossam
Date: 2025-02-27T10:21:56+01:00
New Revision: fcc88021334d7ee904e891a9b7b29b07afd609d0

URL: https://github.com/llvm/llvm-project/commit/fcc88021334d7ee904e891a9b7b29b07afd609d0
DIFF: https://github.com/llvm/llvm-project/commit/fcc88021334d7ee904e891a9b7b29b07afd609d0.diff

LOG: [Docs] Fix typo in GetElementPtr.rst (#127393)

I couldn't find the verb "indices", and it was actually
a bit confusing for me reading this.
I think this should be "indexes" instead.

Added: 
    

Modified: 
    llvm/docs/GetElementPtr.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/GetElementPtr.rst b/llvm/docs/GetElementPtr.rst
index 9ba6218fadfbd..25a24c6403091 100644
--- a/llvm/docs/GetElementPtr.rst
+++ b/llvm/docs/GetElementPtr.rst
@@ -41,7 +41,7 @@ same. For example, when we write, in "C":
 
 it is natural to think that there is only one index, the selection of the field
 ``F``.  However, in this example, ``Foo`` is a pointer. That pointer
-must be indexed explicitly in LLVM. C, on the other hand, indices through it
+must be indexed explicitly in LLVM. C, on the other hand, indexes through it
 transparently.  To arrive at the same address location as the C code, you would
 provide the GEP instruction with two index operands. The first operand indexes
 through the pointer; the second operand indexes the field ``F`` of the