fdo-mirrors/wayland-protocols
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland-protocols.git synced 2025-12-20 15:10:07 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Use correct indefinite article before "xdg"

Browse source 
Since the abbreviation "XDG" starts with a vowel sound, the correct
article is "an."

Signed-off-by: Vlad Zahorodnii <vlad.zahorodnii@kde.org>
This commit is contained in:
Vlad Zahorodnii 2020-06-19 12:22:28 +03:00
parent 684cd23ae3
commit 6be6e00c02
5 changed files with 13 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
stable/xdg-shell/xdg-shell.xml
View file

@ -389,7 +389,7 @@
<request name="set_parent_configure" since="3">
<description summary="set parent configure this is a response to">
Set the serial of a xdg_surface.configure event this positioner will be
Set the serial of an xdg_surface.configure event this positioner will be
used in response to. The compositor may use this information together
with set_parent_size to determine what future state the popup should be
constrained using.
@ -1213,12 +1213,12 @@
If the popup is repositioned in response to a configure event for its
parent, the client should send an xdg_positioner.set_parent_configure
and possibly a xdg_positioner.set_parent_size request to allow the
and possibly an xdg_positioner.set_parent_size request to allow the
compositor to properly constrain the popup.
If the popup is repositioned together with a parent that is being
resized, but not in response to a configure event, the client should
send a xdg_positioner.set_parent_size request.
send an xdg_positioner.set_parent_size request.
</description>
<arg name="positioner" type="object" interface="xdg_positioner"/>
<arg name="token" type="uint" summary="reposition request token"/>

4
unstable/xdg-decoration/xdg-decoration-unstable-v1.xml
View file

@ -113,7 +113,7 @@
that the client prefers the provided decoration mode.
After requesting a decoration mode, the compositor will respond by
emitting a xdg_surface.configure event. The client should then update
emitting an xdg_surface.configure event. The client should then update
its content, drawing it without decorations if the received mode is
server-side decorations. The client must also acknowledge the configure
when committing the new content (see xdg_surface.ack_configure).
@ -122,7 +122,7 @@
different mode instead.
Clients whose decoration mode depend on the xdg_toplevel state may send
a set_mode request in response to a xdg_surface.configure event and wait
a set_mode request in response to an xdg_surface.configure event and wait
for the next xdg_surface.configure event to prevent unwanted state.
Such clients are responsible for preventing configure loops and must
make sure not to send multiple successive set_mode requests with the

6
unstable/xdg-foreign/xdg-foreign-unstable-v1.xml
View file

@ -77,7 +77,7 @@
corresponding interface and event for details.
A surface may be exported multiple times, and each exported handle may
be used to create a xdg_imported multiple times. Only xdg_surface
be used to create an xdg_imported multiple times. Only xdg_surface
surfaces may be exported.
</description>
<arg name="id" type="new_id" interface="zxdg_exported_v1"
@ -118,7 +118,7 @@
<interface name="zxdg_exported_v1" version="1">
<description summary="an exported surface handle">
A xdg_exported object represents an exported reference to a surface. The
An xdg_exported object represents an exported reference to a surface. The
exported surface may be referenced as long as the xdg_exported object not
destroyed. Destroying the xdg_exported invalidates any relationship the
importer may have established using xdg_imported.
@ -145,7 +145,7 @@
<interface name="zxdg_imported_v1" version="1">
<description summary="an imported surface handle">
A xdg_imported object represents an imported reference to surface exported
An xdg_imported object represents an imported reference to surface exported
by some client. A client can use this interface to manipulate
relationships between its own surfaces and the imported surface.
</description>

8
unstable/xdg-foreign/xdg-foreign-unstable-v2.xml
View file

@ -77,7 +77,7 @@
corresponding interface and event for details.
A surface may be exported multiple times, and each exported handle may
be used to create a xdg_imported multiple times. Only xdg_toplevel
be used to create an xdg_imported multiple times. Only xdg_toplevel
equivalent surfaces may be exported.
</description>
<arg name="id" type="new_id" interface="zxdg_exported_v2"
@ -118,7 +118,7 @@
<interface name="zxdg_exported_v2" version="1">
<description summary="an exported surface handle">
A xdg_exported object represents an exported reference to a surface. The
An xdg_exported object represents an exported reference to a surface. The
exported surface may be referenced as long as the xdg_exported object not
destroyed. Destroying the xdg_exported invalidates any relationship the
importer may have established using xdg_imported.
@ -145,7 +145,7 @@
<interface name="zxdg_imported_v2" version="1">
<description summary="an imported surface handle">
A xdg_imported object represents an imported reference to surface exported
An xdg_imported object represents an imported reference to surface exported
by some client. A client can use this interface to manipulate
relationships between its own surfaces and the imported surface.
</description>
@ -161,7 +161,7 @@
<request name="set_parent_of">
<description summary="set as the parent of some surface">
Set the imported surface as the parent of some surface of the client.
The passed surface must be a xdg_toplevel equivalent. Calling this
The passed surface must be an xdg_toplevel equivalent. Calling this
function sets up a surface to surface relation with the same stacking
and positioning semantics as xdg_toplevel.set_parent.
</description>

2
unstable/xdg-shell/xdg-shell-unstable-v6.xml
View file

@ -389,7 +389,7 @@
also be treated as errors.
For a surface to be mapped by the compositor, the following conditions
must be met: (1) the client has assigned a xdg_surface based role to the
must be met: (1) the client has assigned an xdg_surface based role to the
surface, (2) the client has set and committed the xdg_surface state and
the role dependent state to the surface and (3) the client has committed a
buffer to the surface.