From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com
[IPv6:2607:f8b0:4864:20::d2c])
by sourceware.org (Postfix) with ESMTPS id CFC95394843A
for ; Tue, 22 Mar 2022 19:55:42 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org CFC95394843A
Received: by mail-io1-xd2c.google.com with SMTP id p22so1374513iod.2
for ; Tue, 22 Mar 2022 12:55:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20210112;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=7ykDhd+4hYJbtdNehHFQNTsmh7x6+w+DDPguq7WiKBE=;
b=nRdJa5iyAUWcs2K1EXC4BGAMbp6HUsmQs9ijpfubmilC8Gs6P7OA6nFw/ArdUdG7uk
LEPY64vh4WfqjpzfGIT9Mkq6st1Td4my7lBkT8ugJmWu+cEg4STGLRISxQG/5RFYe5Oz
zUQ5JpPf0UkTvtRxxTZsM1btfBWDixCEeSOwuiYQuvaIde0DL6xx3NxjSnTO2kFDfjZq
+pD3V1LYL1Z9Ynv2OFxdPUQi5ehx6ohzkgpBPkYSbGPy6/wvBL9nldzfXyILaEUOtqkV
87HCpSTCa1NhRQaCxcBFbbwgkcFSQ/+hptQt49Cw5A/gqiiPZK2wzFwl1NuXiEH29aCS
KxbQ==
X-Gm-Message-State: AOAM531x4f3mzlWJonIXaH7ZV45dRhL5kTSb+h8z5XuX9yGZ/HNvW+Zx
G/FQK9FpKbYEEJK9FUQmH+QFOCUPLc/ltd2A45dVi5RumxA=
X-Google-Smtp-Source: ABdhPJyqfgo6Nn9HRAV0PNifdas7ZaZ6anaEeAWjrGzpP6/p2icPcfSnOfX7meeMCDc0CPgOqmcOiTqPq/VN99WRDhc=
X-Received: by 2002:a02:ab89:0:b0:321:2f3f:ae96 with SMTP id
t9-20020a02ab89000000b003212f3fae96mr8135885jan.253.1647978941896; Tue, 22
Mar 2022 12:55:41 -0700 (PDT)
MIME-Version: 1.0
References:
In-Reply-To:
From: Pokechu22
Date: Tue, 22 Mar 2022 12:55:15 -0700
Message-ID:
Subject: [wwwdocs] [PATCH 4/4] contribute: Fix various typos
To: gcc-patches@gcc.gnu.org
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-8.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT,
FREEMAIL_FROM, GIT_PATCH_0, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP,
T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
server2.sourceware.org
X-BeenThere: gcc-patches@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-patches mailing list
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Tue, 22 Mar 2022 19:55:44 -0000
---
htdocs/contribute.html | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c0223738..2d04b1f0 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -267,7 +267,7 @@ characters.
The classifier identifies the type of contribution, for example a
patch, an RFC (request for comments) or a committed patch (where
-approval is not necessary. The classifier should be written in upper
+approval is not necessary). The classifier should be written in upper
case and surrounded with square brackets. This is the only component
of the e-mail subject line that will not appear in the commit itself.
The classifier may optionally contain a version number (vN) and
@@ -297,7 +297,7 @@ followed by a colon. For example,
Some large components may be subdivided into sub-components. If
-the subcomponent name is not disctinct in its own right, you can use the
+the subcomponent name is not distinct in its own right, you can use the
form component/sub-component:.
Series identifier
@@ -327,7 +327,7 @@ the commit message so that Bugzilla will correctly
notice the
commit. If your patch relates to two bugs, then write
[PRnnnnn, PRmmmmm]
. For multiple
bugs, just cite the most relevant one in the summary and use an
-elipsis instead of the second, or subsequent PR numbers; list all the
+ellipsis instead of the second, or subsequent PR numbers; list all the
related PRs in the body of the commit message in the normal way.
It is not necessary to cite bugs that are closed as duplicates of
@@ -352,7 +352,7 @@ together.
If you submit a new version of a patch series, then you should
start a new email thread (don't reply to the original patch series).
This avoids email threads becoming confused between discussions of the
-first and subsequent revisions of the patch set. Your cover leter
+first and subsequent revisions of the patch set. Your cover letter
(0/nnn) should explain clearly what has been changed between
the two patch series. Also state if some of the patches are unchanged
between revisions; this saves maintainers having to re-review the
--
2.25.1