From 3382aef944ef7a497248ef85df75ec04f6c21642 Mon Sep 17 00:00:00 2001 From: amansharma612 Date: Tue, 8 Apr 2025 02:29:41 +0530 Subject: [PATCH] [libc] Fixed typo in porting.rst (#134488) Co-authored-by: Aman Sharma <210100011@iitb.ac.in> --- libc/docs/porting.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libc/docs/porting.rst b/libc/docs/porting.rst index 5747a8b9b0c7..e890e439f619 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 differs 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