[libc-commits] [libc] 3382aef - [libc] Fixed typo in porting.rst (#134488)

[via libc-commits]

Author: amansharma612
Date: 2025-04-07T21:59:41+01:00
New Revision: 3382aef944ef7a497248ef85df75ec04f6c21642

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

LOG: [libc] Fixed typo in porting.rst (#134488)

Co-authored-by: Aman Sharma <210100011 at iitb.ac.in>

Added: 
    

Modified: 
    libc/docs/porting.rst

Removed: 
    


################################################################################
diff  --git a/libc/docs/porting.rst b/libc/docs/porting.rst
index 5747a8b9b0c73..e890e439f619f 100644
--- a/libc/docs/porting.rst
+++ b/libc/docs/porting.rst
@@ -53,7 +53,7 @@ architectures. Since a large part of the libc makes use of syscalls (or an
 equivalent on non-Linux like platforms), it might be simpler and convenient to
 bring up the libc for one architecture at a time. In such cases, wherein the
 support surface of LLVM's libc 
diff ers for each target architecture, one will
-have to add a subdirectory (within the config directory os the operating
+have to add a subdirectory (within the config directory of the operating
 system) for each target architecture, and list the relevant config information
 separately in those subdirectories. For example, for Linux, the x86_64 and
 aarch64 configs are in separate directories, named