From 70971f92c9888250f03b61f749ffb7fcf013ae7d Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Wed, 13 Mar 2024 23:12:07 +0900 Subject: [PATCH 01/12] Clarify what a registry is made of (#818) The specs that use the registry are necessarily for a registry to be useful, but they're not part of it. Co-authored-by: Ted Thibodeau Jr --- index.bs | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/index.bs b/index.bs index 0a398db7..ce481350 100644 --- a/index.bs +++ b/index.bs @@ -4566,14 +4566,13 @@ Revising W3C Statements The Registry Track A registry documents a data set - consisting of one or more associated registry tables, + consisting of one or more registry tables, each table representing an updatable collection of logically independent, consistently-structured registry entries. - A registry has three associated components: + A registry consists of: The purposes of maintaining a [=registry=] can include: From 020ae90bdd644108f9b596aee8b8b926462b1cdb Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Thu, 14 Mar 2024 17:39:13 +0900 Subject: [PATCH 02/12] Add anchor for convenient linking --- index.bs | 1 + 1 file changed, 1 insertion(+) diff --git a/index.bs b/index.bs index ce481350..9c1744c6 100644 --- a/index.bs +++ b/index.bs @@ -2539,6 +2539,7 @@ Council Deliberations The deliberations of a [=W3C Council=] are confidential to that [=W3C Council=] and its [=Council Team Contact=]. +

If a [=W3C Council=] is unable to come to a conclusion within 45 days of being convened, the [=W3C Council Chair=] must inform the [=AC=] of this delay and of the status of the discussions. From c92eacf3ee525ba7cf9f1375410f6f90b9590705 Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Mon, 18 Mar 2024 23:57:12 +0900 Subject: [PATCH 03/12] Update the CEPC to its new Name (COC) --- index.bs | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/index.bs b/index.bs index 9c1744c6..5db021ff 100644 --- a/index.bs +++ b/index.bs @@ -118,9 +118,9 @@ Relation of Process Document to Patent Policy and Other Policies incorporated by normative reference as a part of the Process Document are equally binding. - The Patent Policy and CEPC place additional obligations on Members, Team, and other participants in W3C. + The Patent Policy and Code of Conduct place additional obligations on Members, Team, and other participants in W3C. The Process Document does not restate those requirements but includes references to them. - The Process Document, Patent Policy, and CEPC have been designed to allow each to evolve independently. + The Process Document, Patent Policy, and Code of Conduct have been designed to allow each to evolve independently. In the Process Document, the term “participant” refers to an individual, not an organization. @@ -437,7 +437,7 @@ Expectations and Discipline are responsible for assessing and attesting to the qualities of those nominees.

Participants in any W3C activity must abide - by the terms and spirit of the W3C Code of Ethics and Professional Conduct [[!CEPC]] + by the terms and spirit of the W3C Code of Conduct [[!COC]] and the participation requirements described in “Disclosure” in the W3C Patent Policy [[!PATENT-POLICY]]. @@ -448,7 +448,7 @@ Expectations and Discipline if serious and/or repeated violations, such as failure to meet the requirements on individual behavior of (a) this process - and in particular the CEPC, or + and in particular the Code of Conduct, or (b) the membership agreement, or (c) applicable laws, occur. @@ -2408,7 +2408,7 @@ Council Participation, Dismissal, and Renunciation The [=Team=] may report comments verbatim or may paraphrase them while preserving their intent; they may also elide inappropriate comments, - such as any that violate applicable laws or the [[CEPC]]. + such as any that violate applicable laws or the [[COC]]. Before a Council forms, the [=Team=] presents the entire list of potential members @@ -5483,7 +5483,7 @@ Process Evolution The documents covered by this section are: * the W3C Process (this document) * the W3C Patent Policy [[!PATENT-POLICY]] - * the W3C Code of Ethics and Professional Conduct [[!CEPC]] + * the W3C Code of Conduct [[!COC]] * The W3C Document License [[!DOC-LICENSE]] The [=Advisory Board=] initiates review as follows: @@ -5508,7 +5508,7 @@ Process Evolution Note: As of June 2020, the [[PATENT-POLICY|Patent Policy]] is developed in the Patents and Standards Interest Group, - the [[CEPC|Code of Ethics and Professional Conduct]] in the Positive Work Environment Community Group, + the [[COC|Code of Conduct]] in the Positive Work Environment Community Group, and the Process in the W3C Process Community Group.

@@ -5841,9 +5841,9 @@ Changes since earlier versions

"title": "The Art of Consensus, a guidebook for W3C Working Group Chairs and other collaborators", "publisher": "W3C" }, - "CEPC": { - "href": "https://www.w3.org/Consortium/cepc/", - "title": "W3C Code of Ethics and Professional Conduct", + "COC": { + "href": "https://www.w3.org/policies/code-of-conduct/", + "title": "W3C Code of Conduct", "publisher": "W3C" }, "OBS-RESC": { From 45b10f03d6d916c50a0a3d5fc874c7b7cf43e275 Mon Sep 17 00:00:00 2001 From: Florian Rivoal Date: Fri, 22 Mar 2024 12:39:25 +0900 Subject: [PATCH 04/12] Update links See #824 --- index.bs | 58 ++++++++++++++++++++++++++++---------------------------- 1 file changed, 29 insertions(+), 29 deletions(-) diff --git a/index.bs b/index.bs index 5db021ff..2bdef76a 100644 --- a/index.bs +++ b/index.bs @@ -33,7 +33,7 @@ Previous Version: https://www.w3.org/2023/Process-20231103/ Editor: Elika J. Etemad / fantasai, Apple, https://fantasai.inkedblade.net/contact Editor: Florian Rivoal, Invited Expert, https://florian.rivoal.net/ Former Editor: Natasha Rooney, Invited Expert -Former Editor: Charles McCathie Nevile, Yandex, http://yandex.com +Former Editor: Charles McCathie Nevile, Yandex, https://yandex.com Former Editor: Ian Jacobs, W3C, https://www.w3.org/ Level: none Repository: w3c/w3process @@ -46,7 +46,7 @@ Abstract: This document does not describe the internal workings of the Team. For more information about the W3C mission and the history of W3C, - please refer to About W3C. + please refer to About W3C. Status Text: This document, which is based on the 3 November 2023 Process, @@ -180,7 +180,7 @@ Introduction of its chartered [=Working Groups=] and [=Interest Groups=], see [[#Policies]] and [[#GAGeneral]]. W3C also operates Community and Business Groups, - which are separately described in their own process document [[BG-CG]]. + which are separately described in their own process document [[BG-CG]]. In addition, several groups are formally established by the Consortium: the W3C Advisory Committee, which has a representative from each Member, @@ -245,8 +245,8 @@ Members

W3C membership is open to all entities, - as described in “How to Join W3C” [[JOIN]]; - (refer to the public list of current W3C Members [[MEMBER-LIST]]). + as described in “How to Join W3C” [[JOIN]]; + (refer to the public list of current W3C Members [[MEMBER-LIST]]). The Team must ensure that Member participation agreements remain Team-only and that no Member receives preferential treatment within W3C. @@ -378,7 +378,7 @@ The W3C Team unpaid interns, and W3C Fellows. W3C Fellows are Member employees working as part of the Team; - see the W3C Fellows Program [[FELLOWS]]. + see the W3C Fellows Program [[FELLOWS]]. The Team provides technical leadership about Web technologies, organizes and manages W3C activities to reach goals within practical constraints (such as resources available), @@ -452,7 +452,7 @@ Expectations and Discipline (b) the membership agreement, or (c) applicable laws, occur. - Refer to the Guidelines to suspend or remove participants from groups. + Refer to the Guidelines to suspend or remove participants from groups.

Conflict of Interest Policy
@@ -745,7 +745,7 @@ Participation in the Advisory Committee of current Advisory Committee representatives. [[CURRENT-AC]]) When an organization joins W3C - (see “How to Join W3C” [[JOIN]]), + (see “How to Join W3C” [[JOIN]]), it must name its Advisory Committee representative as part of the Membership Agreement. The New Member Orientation [[INTRO]] explains how to subscribe or unsubscribe to Advisory Committee mailing lists, @@ -833,7 +833,7 @@ Advisory Committee Meetings The Team must announce the region of each Advisory Committee meeting at least one year in advance. - More information about Advisory Committee meetings [[AC-MEETING]] + More information about Advisory Committee meetings [[AC-MEETING]] is available at the Member website.

@@ -1606,7 +1606,7 @@ Invited Expert in a Working Group

  • agree to the terms of the - invited expert and collaborators agreement [[!COLLABORATORS-AGREEMENT]], + invited expert and collaborators agreement [[!COLLABORATORS-AGREEMENT]],
  • accept the participation terms set forth in the charter, @@ -2970,7 +2970,7 @@ Wide Review the record of requests to and responses from reviewers, especially W3C Horizontal Groups [[CHARTER]] and groups identified as dependencies in the charter - or identified as liaisons [[LIAISON]], + or identified as liaisons [[LIAISON]], and seek evidence of clear communication to the general public about appropriate times and which content to review and whether such reviews actually occurred. @@ -4424,7 +4424,7 @@ Process for Rescinding, Obsoleting, Superseding, Restoring a Recommendation with up to date status. The updated version may remove the main body of the document. The Status of this Document section should link - to the explanation of Obsoleting and Rescinding W3C Specifications [[OBS-RESC]] as appropriate. + to the explanation of Obsoleting and Rescinding W3C Specifications [[OBS-RESC]] as appropriate. Once W3C has published a Rescinded Recommendation, future W3C technical reports must not include normative references @@ -4902,7 +4902,7 @@ Switching Tracks

    Further reading

    - Refer to "How to Organize a Recommendation Track Transition" [[TRANSITION]] + Refer to "How to Organize a Recommendation Track Transition" [[TRANSITION]] in the Art of Consensus [[GUIDE]] for practical information about preparing for the reviews and announcements of the various steps, @@ -4930,7 +4930,7 @@ Public Communication W3C technical reports (and software) are available free of charge to the general public.
  • - A mission statement [[MISSION]] + A mission statement [[MISSION]] that explains the purpose and mission of W3C, the key benefits for Members, and the organizational structure of W3C. @@ -4951,7 +4951,7 @@ Public Communication [=Workshops=], and review deadlines, the Team provides them with a regular (e.g., weekly) news service - and maintains a calendar [[CALENDAR]] + and maintains a calendar [[CALENDAR]] of official W3C events. Members are encouraged to send schedule and event information to the Team for inclusion on this calendar. @@ -5157,7 +5157,7 @@ Liaisons unless directed to do so by the [=Board=]. A signed [=agreement=] should be made public. - Information about W3C liaisons with other organizations [[LIAISON]] + Information about W3C liaisons with other organizations [[LIAISON]] and the guidelines W3C follows when creating a liaison is available on the Web.

    @@ -5307,7 +5307,7 @@ Scope of Member Submissions

    to build consensus around concrete proposals for new work. Members should not submit materials - covering topics well outside the scope of W3C's mission [[MISSION]]. + covering topics well outside the scope of W3C's mission [[MISSION]].

    Information Required in a Submission Request

    @@ -5316,7 +5316,7 @@ Information Required in a Submission Request and any other authors of the submitted material must agree that, if the request is acknowledged, - the documents in the Member Submission will be subject to the W3C Document License [[!DOC-LICENSE]] + the documents in the Member Submission will be subject to the W3C Document License [[!DOC-LICENSE]] and will include a reference to it. The [=Submitter=](s) may hold the copyright for the documents in a Member Submission. @@ -5448,7 +5448,7 @@ Rejection of a Submission Request, and Submission Appeals
  • The ideas expressed in the request are poor, might harm the Web, - or run counter to W3C's mission [[MISSION]]. + or run counter to W3C's mission [[MISSION]].
  • The ideas expressed in the request lie well outside the scope of W3C's mission. @@ -5727,7 +5727,7 @@ Changes since earlier versions 
     {
 	"JOIN": {
-		"href": "https://www.w3.org/Consortium/join",
+		"href": "https://www.w3.org/Consortium/join/",
 		"title": "How to Join W3C",
 		"publisher": "W3C"
 		},
@@ -5757,12 +5757,12 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"MISSION": {
-		"href": "https://www.w3.org/Consortium/mission",
+		"href": "https://www.w3.org/mission/",
 		"title": "The W3C Mission statement",
 		"publisher": "W3C"
 	},
 	"COLLABORATORS-AGREEMENT": {
-		"href": "https://www.w3.org/Consortium/Legal/collaborators-agreement",
+		"href": "https://www.w3.org/invited-experts/agreement-2023/",
 		"title": "Invited expert and collaborators agreement",
 		"publisher": "W3C"
 	},
@@ -5792,7 +5792,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"LIAISON": {
-		"href": "https://www.w3.org/2001/11/StdLiaison",
+		"href": "https://www.w3.org/liaisons/",
 		"title": "W3C liaisons with other organizations",
 		"publisher": "W3C"
 	},
@@ -5807,7 +5807,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"FELLOWS": {
-		"href": "https://www.w3.org/Consortium/Recruitment/Fellows",
+		"href": "https://www.w3.org/careers/fellows/",
 		"title": "W3C Fellows Program",
 		"publisher": "W3C"
 	},
@@ -5832,7 +5832,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"CALENDAR": {
-		"href": "https://www.w3.org/participate/eventscal",
+		"href": "https://www.w3.org/events/",
 		"title": "Calendar of all scheduled official W3C events",
 		"publisher": "W3C"
 	},
@@ -5847,7 +5847,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"OBS-RESC": {
-		"href": "https://www.w3.org/2016/11/obsoleting-rescinding/",
+		"href": "https://www.w3.org/Guide/process/obsolete-rescinded-supserseded",
 		"title": "Obsoleting and Rescinding W3C Specifications",
 		"publisher": "W3C"
 	},
@@ -5872,7 +5872,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"AC-MEETING": {
-		"href": "https://www.w3.org/Member/Meeting/",
+		"href": "https://www.w3.org/event/ac/",
 		"title": "Advisory Committee meetings (Member-only access)",
 		"publisher": "W3C"
 	},
@@ -5908,7 +5908,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"TRANSITION": {
-		"href": "https://www.w3.org/Guide/transitions",
+		"href": "https://www.w3.org/Guide/transitions/",
 		"title": "Organize a Technical Report Transition",
 		"publisher": "W3C"
 	},
@@ -5922,7 +5922,7 @@ Changes since earlier versions
 		"title": "Amended and Restated Bylaws of World Wide Web Consortium, Inc."
 	},
 	"W3C-IPR": {
-		"href": "https://www.w3.org/Consortium/Legal/2002/ipr-notice-20021231",
+		"href": "https://www.w3.org/policies/",
 		"title": "W3C IPR Policies"
 	},
 	"COUNCIL-REPORT-INDEX": {

From 2aaddbb554c9f51a72ac2234e714a4d035347842 Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Fri, 22 Mar 2024 12:45:45 +0900
Subject: [PATCH 05/12] Fix typos in links

Part of #824
---
 index.bs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index 2bdef76a..dd7a2a8e 100644
--- a/index.bs
+++ b/index.bs
@@ -245,7 +245,7 @@ Members
 	
 
 	
    W3C membership is open to all entities,
-	as described in “How to Join W3C” [[JOIN]];
+	as described in “How to Join W3C” [[JOIN]];
 	(refer to the public list of current W3C Members [[MEMBER-LIST]]).
 	The Team must ensure
 	that Member participation agreements remain Team-only
@@ -745,7 +745,7 @@ Participation in the Advisory Committee
 	of current Advisory Committee representatives. [[CURRENT-AC]])
 
 	When an organization joins W3C
-	(see “How to Join W3C” [[JOIN]]),
+	(see “How to Join W3C” [[JOIN]]),
 	it must name its Advisory Committee representative as part of the Membership Agreement.
 	The New Member Orientation [[INTRO]]
 	explains how to subscribe or unsubscribe to Advisory Committee mailing lists,
@@ -5727,7 +5727,7 @@ Changes since earlier versions
 
     {
 	"JOIN": {
-		"href": "https://www.w3.org/Consortium/join/",
+		"href": "https://www.w3.org/membership/join/",
 		"title": "How to Join W3C",
 		"publisher": "W3C"
 		},
@@ -5872,7 +5872,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"AC-MEETING": {
-		"href": "https://www.w3.org/event/ac/",
+		"href": "https://www.w3.org/events/ac/",
 		"title": "Advisory Committee meetings (Member-only access)",
 		"publisher": "W3C"
 	},

From 6ebd14690beef62870eaaf14dbdc397c5b65ec5c Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Fri, 22 Mar 2024 12:48:13 +0900
Subject: [PATCH 06/12] Update links

Part of #824
---
 index.bs | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/index.bs b/index.bs
index dd7a2a8e..1ccaa652 100644
--- a/index.bs
+++ b/index.bs
@@ -5346,7 +5346,7 @@ Information Required in a Submission Request
 			[=Submitters=] may hold the copyright for the material contained in these documents,
 			but when made available by W3C,
 			these documents must be subject to the provisions
-			of the W3C Document License [[!DOC-LICENSE]].
+			of the W3C Document License [[!DOC-LICENSE]].
 	
 
 	The request must also answer the following questions.
@@ -5442,7 +5442,7 @@ Rejection of a Submission Request, and Submission Appeals
 			The IPR statement made by the [=Submitter=](s) is inconsistent with W3C's
 			Patent Policy [[!PATENT-POLICY]]
 			and in particular the “Licensing Commitments in W3C Submissions”,
-			Document License [[!DOC-LICENSE]],
+			Document License [[!DOC-LICENSE]],
 			or other IPR policies.
 
 		
  • 
@@ -5737,7 +5737,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"MEMBER-LIST": {
-		"href": "https://www.w3.org/Consortium/Member/List",
+		"href": "https://www.w3.org/Consortium/membership/list/",
 		"title": "The list of current W3C Members",
 		"publisher": "W3C"
 	},
@@ -5767,7 +5767,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"DOC-LICENSE": {
-		"href": "https://www.w3.org/Consortium/Legal/copyright-documents",
+		"href": "https://www.w3.org/copyright/document-license-2023/",
 		"title": "W3C Document License",
 		"publisher": "W3C"
 	},

From 77ccd122e9c75db620a3236f4fd05ddfb0f3d18a Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Fri, 22 Mar 2024 12:53:18 +0900
Subject: [PATCH 07/12] Fix typos in links

Part of #824
---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 1ccaa652..327d22cd 100644
--- a/index.bs
+++ b/index.bs
@@ -5737,7 +5737,7 @@ Changes since earlier versions
 		"publisher": "W3C"
 	},
 	"MEMBER-LIST": {
-		"href": "https://www.w3.org/Consortium/membership/list/",
+		"href": "https://www.w3.org/membership/list/",
 		"title": "The list of current W3C Members",
 		"publisher": "W3C"
 	},

From 59df8e6fb7e4bfd8033a404fe7f79a3956ebbf06 Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Thu, 28 Mar 2024 00:04:26 +0900
Subject: [PATCH 08/12] Clarify definition of the REC-track document

This makes it clear that a document that uses the various publication
types and transitions of the REC-track is indeed a REC-track document, even
if it isn't planning to go all the way to the end.

Some groups for instance have a declared intention of only going as far
as CR. That doesn't make the documents on the "CR track", as there's no
such thing.

See https://github.com/w3c/strategy/issues/438#issuecomment-1997685426
---
 index.bs | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/index.bs b/index.bs
index 327d22cd..3cd5ae5b 100644
--- a/index.bs
+++ b/index.bs
@@ -3196,6 +3196,9 @@ The W3C Recommendation Track
 		
  • Publication as a [=W3C Recommendation=].
 	
 
+	A W3C Recommendation Track document
+	is any document whose current status is one of the five in the numbered list above.
+
 	
    
 		
     			path: basic-rec-track.svg

From 4a4d433ba42d7a5dc58f2813fb933fe7113eb593 Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Thu, 28 Mar 2024 00:07:12 +0900
Subject: [PATCH 09/12] Clarify confidentiality requirements (#835)

This is an attempt to clarify the confidentiality requirements by
separating concerns.

* the second bullet in the list is about using reasonable effort. It's
  not specifically the different levels of confidentiality, nor about any
  particular action that must be taken. It's only about defining the
  standard of care that is applicable to maintaining confidentiality.
* The third bullet is specifically about "must not disclose".

But the phrasing of the second bullet could be read as if there was some
particular task or activity ("effort") to be performed when dealing with
different levels, suggesting that maybe changing levels was OK, as long
as you do it the right way (maybe by redacting something).

This rephrasing clarifies that "reasonable effort" is a general
requirement about confidentiality, and that disclosing beyond the proper
level is not appropriate.
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index 3cd5ae5b..ff6a77a9 100644
--- a/index.bs
+++ b/index.bs
@@ -4989,10 +4989,11 @@ Confidentiality Levels
 			must treat the information as confidential within W3C,
 
 		
  • 
-			must use reasonable efforts to maintain the proper level of confidentiality, and
+			must use reasonable efforts to preserve that confidentiality, and
 
 		
  • 
-			must not release this information to the general public or press.
+			must not release this information to the general public or press,
+			nor beyond the proper level of access.
 	
 
 	The [=Team=] must provide mechanisms

From 76ab28c830e7f7c1857f03957ac712ea98489b49 Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Mon, 1 Apr 2024 10:24:20 +0900
Subject: [PATCH 10/12] Eliminate potential ambiguity in AB chair ratification

See this resolves part 1 of https://github.com/w3c/w3process/issues/838
---
 index.bs | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/index.bs b/index.bs
index ff6a77a9..f6ff596e 100644
--- a/index.bs
+++ b/index.bs
@@ -885,8 +885,9 @@ Composition of the Advisory Board
 	With the input of the [=AB=],
 	the [=Team=] appoints the Chair,
 	who should choose a co-chair among the elected participants.
-	The Chair(s) are subject to ratification by secret ballot
-	by two thirds of the AB upon appointment.
+	Upon appointment,
+	the Chair(s) are subject to ratification by secret ballot,
+	requiring approval by two thirds of the elected participants.
 	Chair selection must be run
 	at least at the start of each regular term,
 	as well as when a majority of the participants request it;

From 30b55e7a42f974f7c70bb6c47668cba6ff14c70f Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Mon, 1 Apr 2024 11:20:59 +0900
Subject: [PATCH 11/12] Update changes section

---
 index.bs | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/index.bs b/index.bs
index f6ff596e..2f07efe3 100644
--- a/index.bs
+++ b/index.bs
@@ -5682,12 +5682,6 @@ Changes since the 3 November
 	a detailed log of all changes since then
 	are available.
 
-	
-
 	In addition to a number of editorial adjustments and minor teaks, the following is a summary of the main differences:
 
 	
 
 

From bb1c8c1f40b9d9e78d759757d6cb8efd8a45cdac Mon Sep 17 00:00:00 2001
From: Florian Rivoal 
Date: Mon, 15 Apr 2024 12:14:56 +0900
Subject: [PATCH 12/12] Export term

---
 index.bs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.bs b/index.bs
index 2f07efe3..479090ff 100644
--- a/index.bs
+++ b/index.bs
@@ -3197,7 +3197,7 @@ The W3C Recommendation Track
 		
  • Publication as a [=W3C Recommendation=].
 	
 
-	A W3C Recommendation Track document
+	A W3C Recommendation Track document
 	is any document whose current status is one of the five in the numbered list above.