governance: fix typos

Signed-off-by: Vaxry <vaxry@vaxry.net>
This commit is contained in:
Vaxry 2023-10-12 22:10:11 +01:00
parent 9ffeb975c3
commit d70af2ea1e

View file

@ -58,7 +58,7 @@ standardization.
2. Protocols in a namespace may optionally use the namespace followed by a dash 2. Protocols in a namespace may optionally use the namespace followed by a dash
in the name (e.g. "xdg-shell"). in the name (e.g. "xdg-shell").
3. The "xdg" namespace is established for protocols letting clients 3. The "xdg" namespace is established for protocols letting clients
configure its surfaces as "windows", allowing clients to affect how they configure their surfaces as "windows", allowing clients to affect how they
are managed. are managed.
4. The "wp" namespace is established for protocols generally useful to Wayland 4. The "wp" namespace is established for protocols generally useful to Wayland
implementations (i.e. "plumbing" protocols). implementations (i.e. "plumbing" protocols).
@ -72,7 +72,7 @@ standardization.
2. Protocols in the "xdg" and "wp" namespace are eligible for inclusion only if 2. Protocols in the "xdg" and "wp" namespace are eligible for inclusion only if
ACKed by at least 3 members. ACKed by at least 3 members.
3. Protocols in the "xdg" and "wp" namespace are ineligible for inclusion if 3. Protocols in the "xdg" and "wp" namespace are ineligible for inclusion if
if NACKed by any member. NACKed by any member.
4. Protocols in the "xdg" and "wp" namespaces must have at least 3 open-source 4. Protocols in the "xdg" and "wp" namespaces must have at least 3 open-source
implementations (either 1 client + 2 servers, or 2 clients + 1 server) to be implementations (either 1 client + 2 servers, or 2 clients + 1 server) to be
eligible for inclusion. eligible for inclusion.
@ -95,7 +95,7 @@ standardization.
use this time to acquire them. use this time to acquire them.
4. When the proposed protocol meets all requirements for inclusion per section 4. When the proposed protocol meets all requirements for inclusion per section
2.2, and the minimum discussion period has elapsed, the sponsoring member may 2.2, and the minimum discussion period has elapsed, the sponsoring member may
merge their changes in the wayland-protocol repository. merge their changes into the wayland-protocol repository.
5. Amendments to existing protocols may be proposed by the same process, with 5. Amendments to existing protocols may be proposed by the same process, with
no minimum discussion period. no minimum discussion period.
6. Declaring a protocol stable may be proposed by the same process, with the 6. Declaring a protocol stable may be proposed by the same process, with the