Fix typos in documentation

llvm · Sep 2, 2023 · 5dd9568 · 5dd9568
1 parent 83e6931
commit 5dd9568
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/clang/docs/analyzer/checkers.rst b/clang/docs/analyzer/checkers.rst
@@ -2481,13 +2481,13 @@ input refers to a valid file and removing any invalid user input.
     if (!filename[0])
       return -1;
     strcat(cmd, filename);
-    system(cmd); // Superflous Warning: Untrusted data is passed to a system call
+    system(cmd); // Superfluous Warning: Untrusted data is passed to a system call
   }
 
 Unfortunately, the checker cannot discover automatically that the programmer
 have performed data sanitation, so it still emits the warning.
 
-One can get rid of this superflous warning by telling by specifying the
+One can get rid of this superfluous warning by telling by specifying the
 sanitation functions in the taint configuration file (see
 :doc:`user-docs/TaintAnalysisConfiguration`).
 

diff --git a/libc/docs/dev/code_style.rst b/libc/docs/dev/code_style.rst
@@ -39,7 +39,7 @@ We define two kinds of macros:
 
    * ``src/__support/macros/properties/`` - Build related properties like
      target architecture or enabled CPU features defined by introspecting
-     compiler defined preprocessor defininitions.
+     compiler defined preprocessor definitions.
 
      * ``architectures.h`` - Target architecture properties.
        e.g., ``LIBC_TARGET_ARCH_IS_ARM``.

diff --git a/lldb/docs/use/tutorial.rst b/lldb/docs/use/tutorial.rst
@@ -360,7 +360,7 @@ That is better, but suffers from the problem that when new breakpoints get
 added, they don't pick up these modifications, and the options only exist in
 the context of actual breakpoints, so they are hard to store & reuse.
 
-A even better solution is to make a fully configured breakpoint name:
+An even better solution is to make a fully configured breakpoint name:
 
 ::
 

diff --git a/llvm/docs/LangRef.rst b/llvm/docs/LangRef.rst
@@ -7159,7 +7159,7 @@ It is illegal for the list node to be empty since it might be confused
 with an access group.
 
 The access group metadata node must be 'distinct' to avoid collapsing
-multiple access groups by content. A access group metadata node must
+multiple access groups by content. An access group metadata node must
 always be empty which can be used to distinguish an access group
 metadata node from a list of access groups. Being empty avoids the
 situation that the content must be updated which, because metadata is