[llvm] [llvm] Fix a typo in documentation (PR #147129)

Kazu Hirata via llvm-commits llvm-commits at lists.llvm.org
Fri Jul 4 23:02:17 PDT 2025


https://github.com/kazutakahirata created https://github.com/llvm/llvm-project/pull/147129

None

>From 30dc786c42732093fad1ac08c47fcd9384282fd2 Mon Sep 17 00:00:00 2001
From: Kazu Hirata <kazu at google.com>
Date: Fri, 4 Jul 2025 21:45:50 -0700
Subject: [PATCH] [llvm] Fix a typo in documentation

---
 llvm/docs/DeveloperPolicy.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/llvm/docs/DeveloperPolicy.rst b/llvm/docs/DeveloperPolicy.rst
index 87b4d6d0469eb..c1cfa55e77eff 100644
--- a/llvm/docs/DeveloperPolicy.rst
+++ b/llvm/docs/DeveloperPolicy.rst
@@ -623,7 +623,7 @@ After posting a major proposal, it is common to receive lots of conflicting
 feedback from different parties, or no feedback at all, leaving authors without
 clear next steps. As a community, we are aiming for `"rough consensus"
 <https://en.wikipedia.org/wiki/Rough_consensus>`_, similar in spirit to what is
-desribed in `IETF RFC7282 <https://datatracker.ietf.org/doc/html/rfc7282>`_.
+described in `IETF RFC7282 <https://datatracker.ietf.org/doc/html/rfc7282>`_.
 This requires considering and addressing all of the objections to the RFC, and
 confirming that we can all live with the tradeoffs embodied in the proposal.
 



More information about the llvm-commits mailing list