[clang] [clang][www] Fix typos in OpenProjects page (PR #228822)
Ivy Xu via cfe-commits
cfe-commits at lists.llvm.org
Sun Oct 4 00:30:50 PDT 2026
https://github.com/IvyXu420 updated https://github.com/llvm/llvm-project/pull/228822
>From 9f32da20486024b71bc3d96789a4566e27d62d89 Mon Sep 17 00:00:00 2001
From: Ivy Xu <fakeshadow1337 at gmail.com>
Date: Sun, 4 Oct 2026 12:57:09 +0800
Subject: [PATCH 1/2] Add the missing space after `issue tracker`
---
clang/www/OpenProjects.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/clang/www/OpenProjects.html b/clang/www/OpenProjects.html
index 71ce7ecf416d8..ef090610149b0 100755
--- a/clang/www/OpenProjects.html
+++ b/clang/www/OpenProjects.html
@@ -77,7 +77,7 @@ <h1>Open Clang Projects</h1>
defect reports and updating the documentation accordingly.</li>
<li><b>Bug triage</b>: Clang's <a href="https://github.com/llvm/llvm-project/issues">
-issue tracker</a>currently has over 20,000 open issues, many of which are not
+issue tracker</a> currently has over 20,000 open issues, many of which are not
appropriately tagged, are no longer reproducible, could use a reduced test case,
or otherwise needs some manual interaction. We can always use help with
<a href="https://llvm.org/docs/BugLifeCycle.html#triaging-bugs">bug triage and
>From 03440190f195651bb88a0d7f0ddac494a9e74509 Mon Sep 17 00:00:00 2001
From: Ivy Xu <fakeshadow1337 at gmail.com>
Date: Sun, 4 Oct 2026 15:30:13 +0800
Subject: [PATCH 2/2] More typos
---
clang/www/OpenProjects.html | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/clang/www/OpenProjects.html b/clang/www/OpenProjects.html
index ef090610149b0..05425d6964ea1 100755
--- a/clang/www/OpenProjects.html
+++ b/clang/www/OpenProjects.html
@@ -37,15 +37,15 @@ <h1>Open Clang Projects</h1>
undocumented attributes</a>,</li>
<li>documenting <a href="https://github.com/llvm/llvm-project/blob/main/clang/include/clang/Basic/DiagnosticDocs.td">
diagnostic group flags</a> (adding code examples of what is diagnosed, or
- other relevant information), or</li>
+ other relevant information),</li>
<li>documenting <a href="https://github.com/llvm/llvm-project/blob/main/clang/include/clang/Options/Options.td">
- command line options</a>, or</li>
+ command-line options</a>,</li>
<li>help with completing other missing documentation.</li>
</ul>
These projects are independent of each other.</li>
<li><b>Complete the investigation into Clang's C conformance</b>: Clang's
-<a href="c_status.html">C status page</a> contain a number of entries marked as
+<a href="c_status.html">C status page</a> contains a number of entries marked as
<code>Unknown</code>. Completing the investigation involves adding
<a href="https://github.com/llvm/llvm-project/tree/main/clang/test/C">test
coverage</a> for the various standards papers and updating the documentation
@@ -97,7 +97,7 @@ <h1>Open Clang Projects</h1>
from source code. The tool is in early stages of development and could use more
dedicated effort to complete the implementation.</li>
-<li><b>Self-testing using clang</b>: There are several neat ways to
+<li><b>Self-testing using Clang</b>: There are several neat ways to
improve the quality of clang by self-testing. Some examples:
<ul>
<li>Improve the reliability of AST printing and serialization by
@@ -142,7 +142,7 @@ <h1>Open Clang Projects</h1>
<p>The second stage would be to produce a configuration file (that can be used
independently of the Host) so that Clang can read it and not need a gazillion
-of command-line options. Such file should be simple JSON / INI or anything that
+of command-line options. Such a file should be simple JSON / INI or anything that
a text editor could change.</p></li>
</ul>
More information about the cfe-commits
mailing list