[Valgrind-developers] [valgrind] Fix typo: segement -> segment

[Philippe W. <phi...@so...>]

https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=50d1a471cd86ba82f3bc4e79943b43bf9193d8cb

commit 50d1a471cd86ba82f3bc4e79943b43bf9193d8cb
Author: Philippe Waroquiers <phi...@sk...>
Date:   Fri Apr 11 21:37:18 2025 +0200

    Fix typo:  segement -> segment
    
    No impact, typo in a comment.

Diff:
---
 coregrind/m_ume/elf.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/coregrind/m_ume/elf.c b/coregrind/m_ume/elf.c
index 67d3139d29..5f2ac1fedb 100644
--- a/coregrind/m_ume/elf.c
+++ b/coregrind/m_ume/elf.c
@@ -514,7 +514,7 @@ Bool VG_(match_ELF)(const void *hdr, SizeT len)
      the furthest-along mapping it creates.  The executable is mapped
      starting at EBASE, which is usually read from it (eg, 0x8048000
      etc) except if it's a PIE, in which case aspacem is queried for
-     the first adequately sized segement.
+     the first adequately sized segment.
 
      The returned address is recorded in info->brkbase as the start
      point of the brk (data) segment, as it is traditional to place