summaryrefslogtreecommitdiff
path: root/specs
diff options
context:
space:
mode:
Diffstat (limited to 'specs')
-rw-r--r--specs/XI2proto.txt28
-rw-r--r--specs/XIproto.txt10
-rw-r--r--specs/kbproto/appD.xml6
-rw-r--r--specs/recordproto/record.xml2
-rw-r--r--specs/scrnsaverproto/saver.xml10
-rw-r--r--specs/xextproto/appgrp.xml6
-rw-r--r--specs/xextproto/dbe.xml2
-rw-r--r--specs/xextproto/dpms.xml4
-rw-r--r--specs/xextproto/evi.xml2
-rw-r--r--specs/xextproto/security.xml8
-rw-r--r--specs/xextproto/shm.xml2
-rw-r--r--specs/xextproto/tog-cup.xml6
-rw-r--r--specs/xproto/glossary.xml2
-rw-r--r--specs/xproto/keysyms.xml2
-rw-r--r--specs/xproto/sect1-9.xml2
15 files changed, 46 insertions, 46 deletions
diff --git a/specs/XI2proto.txt b/specs/XI2proto.txt
index 440b0d0..9ba0201 100644
--- a/specs/XI2proto.txt
+++ b/specs/XI2proto.txt
@@ -198,7 +198,7 @@ the screen. A master keyboard is represented by a keyboard focus.
Each master pointer is paired with the respective master keyboard and vice
versa, and this pairing is constant for the lifetime of both input devices.
Clients can use this pairing behaviour to implement input paradigms that
-require pointer and keyboard interation (e.g. SHIFT + Click).
+require pointer and keyboard integration (e.g. SHIFT + Click).
[[hierarchy-slave]]
Slave devices
@@ -265,7 +265,7 @@ is chosen to provide the data for this request.
This ClientPointer may be explicitly assigned to a client with the
SetClientPointer call. If no ClientPointer is set when a client issues an
ambiguous request, the server choses one device as the ClientPointer. The
-method of chosing a ClientPointer from the available master pointers is
+method of choosing a ClientPointer from the available master pointers is
implementation-specific.
If the master pointer currently set as ClientPointer for one or more clients is
@@ -391,7 +391,7 @@ touch events as they occur on the device. If and when the client
becomes the owner of a touch sequence, a TouchOwnership event is sent to the
client. If the client is the initial owner of the sequence, the TouchBegin is
immediately followed by the TouchOwnership event. Otherwise, TouchUpdate events
-may preceed a TouchOwnership event. A client is not guaranteed to become the
+may precede a TouchOwnership event. A client is not guaranteed to become the
owner of any given touch sequence.
The server delivers touch events to all clients that have selected for
@@ -1399,7 +1399,7 @@ XIGrabDevice
This request actively grabs control of the specified input device. Further
input events from this device are reported only to the grabbing client.
-This request overides any previous active grab by this client for this
+This request overrides any previous active grab by this client for this
device. This request does not affect the processing of XI 2.2
touch events.
@@ -1802,7 +1802,7 @@ with mode XIPassiveGrabNotify are generated as if the pointer or focus
were to suddenly warp from its current position to some position in
the grab window. These events are sent to the grabbing client only
and only if the grab event mask has selected for it. If such a passive
-grab deactivates, addional LeaveNotify events with mode
+grab deactivates, additional LeaveNotify events with mode
XIPassiveUngrabNotify are generated and sent to the grabbing client
before the grab deactivates.
@@ -1902,7 +1902,7 @@ The type is uninterpreted by the server. The format specifies whether
the data should be viewed as a list of 8-bit, 16-bit, or 32-bit
quantities so that the server can correctly byte-swap as necessary.
-If the mode is Replace, the previous propert y value is discarded. If
+If the mode is Replace, the previous property value is discarded. If
the mode is Prepend or Append, then the type and format must match the
existing property value (or a Match error results). If the property is
undefined, it is treated as defined with the correct type and format
@@ -2149,20 +2149,20 @@ HierarchyEvent
flags: SETofHIERARCHYMASK}
flags
- Set of the changes that have occured, causing this event.
+ Set of the changes that have occurred, causing this event.
num_info
The number of device info structs following the request.
info:
The current hierarchy information.
An XIHierarchyEvent is sent whenever the device hierarchy been
-changed. The flags specify all types of hierarchy modifiations that have
-occured.
+changed. The flags specify all types of hierarchy modifications that have
+occurred.
For all devices, info details the hierarchy information after the
-modification of the hierarchy has occured. For each device specified with
+modification of the hierarchy has occurred. For each device specified with
deviceid:
-- if type is MasterPointer or MasterKeyboard, attachment decribes the
+- if type is MasterPointer or MasterKeyboard, attachment describes the
pairing of this device.
- if type is SlavePointer or SlaveKeyboard, attachment describes the
master device this device is attached to.
@@ -2285,7 +2285,7 @@ XI 2.2: The event type may also be TouchBegin, TouchUpdate, or TouchEnd.
sourceid
The source device that originally generated the event.
mods
- XKB modifier state before the event occured.
+ XKB modifier state before the event occurred.
group
XKB group state before the event.
buttons
@@ -2393,7 +2393,7 @@ when the device is grabbed by another client.
eventtype
- The type of event that occured on the device.
+ The type of event that occurred on the device.
detail
The button number, keycode or touch ID¹.
sourceid
@@ -2491,7 +2491,7 @@ zero if the device is a floating slave device.
window, then focus is True. Otherwise, focus is False. This field is
unspecified for focus in/out events.
mods
- XKB modifier state before the event occured.
+ XKB modifier state before the event occurred.
group
XKB group state before the event.
buttons_len
diff --git a/specs/XIproto.txt b/specs/XIproto.txt
index 1095a26..61ef41b 100644
--- a/specs/XIproto.txt
+++ b/specs/XIproto.txt
@@ -474,7 +474,7 @@ VALUATORCLASS is as follows:
axes
The axes field contains a pointer to an AXISINFO
- struture.
+ structure.
The information returned for each axis reported by the
device is:
@@ -630,7 +630,7 @@ by first_valuator and num_valuators are set. If the number of
valuators supported by the device is less than the expression
first_valuator + num_valuators, a Value error will result.
-If the request succeeds, Success is returned. If the specifed
+If the request succeeds, Success is returned. If the specified
device is grabbed by some other client, the request will fail
and a status of AlreadyGrabbed will be returned.
@@ -698,7 +698,7 @@ where
Errors: Length, Device, Match, Value
-ChangeDeviceControl changes the specifed device control
+ChangeDeviceControl changes the specified device control
according to the values specified in the DeviceControl
structure. The device control must be supported by the target
server and device or an error will result.
@@ -969,7 +969,7 @@ keycodes. Client programs may be running that depend on those
characteristics. For example, a client program could allocate
an array based on the number of buttons on the pointer device,
and then use the button numbers received in button events as
-indicies into that array. Changing the core devices could cause
+indices into that array. Changing the core devices could cause
such client programs to behave improperly or abnormally
terminate.
@@ -2546,7 +2546,7 @@ DeviceEnabled, the device is enabled and will generate events.
If the field is DeviceDisabled or DeviceRemoved, the given
device is disabled and stops sending events or was removed from
the server, respectively. If the field is DeviceUnrecoverable,
-an IO-error has occured on the device and the device is
+an IO-error has occurred on the device and the device is
forcibly disabled and removed by the server. If devchange is
DeviceControlChanged, control specifies the type of control
that has been changed.
diff --git a/specs/kbproto/appD.xml b/specs/kbproto/appD.xml
index 23aed05..147373b 100644
--- a/specs/kbproto/appD.xml
+++ b/specs/kbproto/appD.xml
@@ -26,7 +26,7 @@ v LISTofITEMs NAME
<para>
The MASK-EXPRESSION is an expression using C-style boolean operators and fields
of the request which specifies the bitmask used to determine whether or not a
-mem ber of the LISTofITEMs is present. If present, TYPE specifies the
+member of the LISTofITEMs is present. If present, TYPE specifies the
interpretation of the resulting bitmask and the values are listed using the
symbolic names of the members of the set. If TYPE is blank, the values are
numeric constants.
@@ -692,10 +692,10 @@ class, or feedback
1 KEYCODE new key
1 SETofKEYMASK mask
1 SETofKEYMASK real modifiers
-1 SETofKB_VMODSHIGH virtual modfiiers mask high
+1 SETofKB_VMODSHIGH virtual modifiers mask high
1 SETofKB_VMODSLOW virtual modifiers mask low
1 SETofKB_VMODSHIGH virtual modifiers high
-1 SETofKB_VMODSLOW virtual modfiers low
+1 SETofKB_VMODSLOW virtual modifiers low
</literallayout>
<literallayout class='monospaced'>1 18 type
diff --git a/specs/recordproto/record.xml b/specs/recordproto/record.xml
index 842a5d6..6b15895 100644
--- a/specs/recordproto/record.xml
+++ b/specs/recordproto/record.xml
@@ -177,7 +177,7 @@ experiments done under the auspices of the X Consortium xtest working
group. Although this was a group effort, the author remains
responsible for any errors or omissions.
Two years ago, Robert Chesler of Absol-puter, Kieron Drake of UniSoft
-Ltd., Marc Evans of Synergytics and Ken Miller of Digitial shared the
+Ltd., Marc Evans of Synergytics and Ken Miller of Digital shared the
vision of a standard extension for recording and were all instrumental
in the early protocol development. During the last two years, Bob
Scheifler of the X Consortium and Jim Fulton of NCD continuously
diff --git a/specs/scrnsaverproto/saver.xml b/specs/scrnsaverproto/saver.xml
index 2374218..b19f0f9 100644
--- a/specs/scrnsaverproto/saver.xml
+++ b/specs/scrnsaverproto/saver.xml
@@ -103,7 +103,7 @@ deactivates. At this time, the window is unmapped and is not accessible to any
client requests.
</para>
<para>
-The server's default mechanism is refered to as the <emphasis remap='I'>internal</emphasis> screen
+The server's default mechanism is referred to as the <emphasis remap='I'>internal</emphasis> screen
saver. An <emphasis remap='I'>external</emphasis>
screen saver client requires a means of determining the window
id for the screen saver window and setting the attributes (e.g. size,
@@ -126,7 +126,7 @@ Second, a screen saver program must control the actual RGB values sent to the
display tube to ensure that the values change periodically to avoid phosphor
burn in. Thus, the client must have a known colormap installed whenever the
screen saver window is displayed. To prevent screen flashing, the visual type
-of the screen saver window should also be controlable.
+of the screen saver window should also be controllable.
</para>
<para>
Third, some implementations may wish to destroy the screen saver window when
@@ -145,7 +145,7 @@ The Screen Saver extension is as follows:
<sect1 id="Types">
<title>Types</title>
<para>
-In adition to the comon types described in the core protocol, the following
+In addition to the common types described in the core protocol, the following
type is used in the request and event definitions in subsequent sections.
</para>
@@ -233,7 +233,7 @@ any of its siblings in the stacking order. XXX - TranslateCoords?
</para>
<para>
The <emphasis remap='I'>state</emphasis> field specifies whether or not the screen saver is currently
-active and how the <emphasis remap='I'>til-or-since</emphasis> value should be interpretted:
+active and how the <emphasis remap='I'>til-or-since</emphasis> value should be interpreted:
</para>
<informaltable frame="none">
@@ -826,7 +826,7 @@ The format of the events generated is:
typedef struct {
int type; /* of event */
unsigned long serial; /* # of last request processed by server */
- Bool send_event; /* true if this came frome a SendEvent request */
+ Bool send_event; /* true if this came from a SendEvent request */
Display *display; /* Display the event was read from */
Window window; /* screen saver window */
Window root; /* root window of event screen */
diff --git a/specs/xextproto/appgrp.xml b/specs/xextproto/appgrp.xml
index 0f91e16..5e27a63 100644
--- a/specs/xextproto/appgrp.xml
+++ b/specs/xextproto/appgrp.xml
@@ -233,7 +233,7 @@ If single_screen is set to True default_root specifies which screen will be retu
<para>
-If single_screen is set to True the root_visual and default_colormap attributes may be used to over-ride the default values that are returned in the connection setup information returned to new programs in the Application Group. If None is specified for root_visual or default_colormap then the normal default values for the screen (possibly spedified by default_root) are used, otherwise the specified values are used. If root_visual and/or default_colormap are specified they must be valid, i.e. root_visual must be a visual type available on the screen, and the colormap, if specified, must be a valid colormap for the visual that is used.
+If single_screen is set to True the root_visual and default_colormap attributes may be used to over-ride the default values that are returned in the connection setup information returned to new programs in the Application Group. If None is specified for root_visual or default_colormap then the normal default values for the screen (possibly specified by default_root) are used, otherwise the specified values are used. If root_visual and/or default_colormap are specified they must be valid, i.e. root_visual must be a visual type available on the screen, and the colormap, if specified, must be a valid colormap for the visual that is used.
</para>
<para>
@@ -409,7 +409,7 @@ The Application Group Leader must not select SubstructuRedirect events on a root
<title>MapRequest</title>
<para>
-When a MapWindow request is received for a window whose override-redirect attribut is set to False and whose parent is the root window and the window belongs to an application that is in an application group and there is an application group leader for the group, then this event is delivered to the Application Group Leader with the parent field in the event set to the AppGroup ID. Otherwise the core protocol semantics apply.
+When a MapWindow request is received for a window whose override-redirect attribute is set to False and whose parent is the root window and the window belongs to an application that is in an application group and there is an application group leader for the group, then this event is delivered to the Application Group Leader with the parent field in the event set to the AppGroup ID. Otherwise the core protocol semantics apply.
</para>
</sect2>
@@ -417,7 +417,7 @@ When a MapWindow request is received for a window whose override-redirect attrib
<title>ConfigureRequest</title>
<para>
-When a ConfigureWindow request is received for a window whose override-redirect attribut is set to False and whose parent is the root window and the window belongs to an application that is in an application group and there is an application group leader for the group, then this event is delivered to the Application Group Leader with the parent field in the event set to the AppGroup ID. Otherwise the core protocol semantics apply.
+When a ConfigureWindow request is received for a window whose override-redirect attribute is set to False and whose parent is the root window and the window belongs to an application that is in an application group and there is an application group leader for the group, then this event is delivered to the Application Group Leader with the parent field in the event set to the AppGroup ID. Otherwise the core protocol semantics apply.
</para>
</sect2>
diff --git a/specs/xextproto/dbe.xml b/specs/xextproto/dbe.xml
index 5af90a6..7b09f5a 100644
--- a/specs/xextproto/dbe.xml
+++ b/specs/xextproto/dbe.xml
@@ -236,7 +236,7 @@ is cleared.
</itemizedlist>
<para>
The effect of passing a window to a request that accepts a DRAWABLE is
-unchanged by this extension. The window and front buffer are synonomous with
+unchanged by this extension. The window and front buffer are synonymous with
each other. This includes obeying the <function>GetImage</function> semantics
and the subwindow-mode semantics if a core graphics context is involved.
Regardless of whether the window was explicitly passed in a
diff --git a/specs/xextproto/dpms.xml b/specs/xextproto/dpms.xml
index 823344d..7edfe5c 100644
--- a/specs/xextproto/dpms.xml
+++ b/specs/xextproto/dpms.xml
@@ -108,7 +108,7 @@ to enforce this rule.
</para>
<para>
-Note however that a concious decision is made to decouple the timeouts
+Note however that a conscious decision is made to decouple the timeouts
associated with screen saver from the DPMS timeouts. While it might be
considered logical to require that the first non-zero DPMS timeout be
greater than or equal to the screen saver timeout, this is intentionally
@@ -273,7 +273,7 @@ final level of power savings is invoked. Off mode's physical and electrical
characteristics are implementation defined, but in DPMS compliant hardware,
is implemented by shutting off both horizontal and vertical sync signals,
resulting in the power-down of the monitor. Recovery time is implementation
-dependant, but frequently is similar to the power-up time of the monitor. A
+dependent, but frequently is similar to the power-up time of the monitor. A
value of zero indicates that this mode is disabled.
</para>
diff --git a/specs/xextproto/evi.xml b/specs/xextproto/evi.xml
index 7b661f6..e47feb1 100644
--- a/specs/xextproto/evi.xml
+++ b/specs/xextproto/evi.xml
@@ -46,7 +46,7 @@ OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER USEABILITIY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF, OR IN
-CONNNECTION WITH THE SOFTWARE OR THE USE OF OTHER DEALINGS IN
+CONNECTION WITH THE SOFTWARE OR THE USE OF OTHER DEALINGS IN
THE SOFTWARE.
</para>
diff --git a/specs/xextproto/security.xml b/specs/xextproto/security.xml
index 93073c5..35f3395 100644
--- a/specs/xextproto/security.xml
+++ b/specs/xextproto/security.xml
@@ -530,7 +530,7 @@ a root window destination.)
</para>
<orderedlist>
<listitem>
- <para>The propogate field of SendEvent is False.</para>
+ <para>The propagate field of SendEvent is False.</para>
</listitem>
<listitem>
<para>
@@ -838,7 +838,7 @@ forward client connections to servers that do not meet the criteria.
To use this authorization method, the client (or proxy) sends
"XC-QUERY-SECURITY-1" as the authorization-protocol-name in the initial
connection setup message. The authorization-protocol-data may be empty or
-may contain additional security criteria desribed below. If the success
+may contain additional security criteria described below. If the success
field of the server's reply is Authenticate, the server supports the
security extension, and the server meets all specified additional security
criteria. In this case, the client should resend the initial connection
@@ -1289,7 +1289,7 @@ name and name_length fields of auth_in should be initialized to the
authorization protocol name and its length in characters respectively.
If there is authorization data, the data and data_length fields of
auth_in should be initialized to the data and its length in characters
-respectivley. The library does not assume that name and data are
+respectively. The library does not assume that name and data are
null-terminated strings. The auth_in argument must be freed with
<xref linkend='XSecurityFreeXauth' xrefstyle='select: title'/>.
</para>
@@ -1380,7 +1380,7 @@ name that was passed in, and the data and data_length fields will be set to
the authorization data returned by the server. The caller should not assume
that name and data are null-terminated strings. If no authorization data was
returned by the server, the data and data_length fields will be set to NULL
-and zero repectively. The returned Xauth structure must be freed with
+and zero respectively. The returned Xauth structure must be freed with
<xref linkend='XSecurityFreeXauth' xrefstyle='select: title'/>; the caller should not use any other
means free the structure or any of its components. The auth_id_return
argument will be filled in with the non-zero authorization id of the created
diff --git a/specs/xextproto/shm.xml b/specs/xextproto/shm.xml
index f6ad347..8e04e7d 100644
--- a/specs/xextproto/shm.xml
+++ b/specs/xextproto/shm.xml
@@ -81,7 +81,7 @@ be able to use this extension, your system must provide the SYSV shared
memory primitives. There is not an mmap-based version of this extension.
To use shared memory on Sun systems, you must have built your kernel with
SYSV shared memory enabled -- which is not the default configuration.
-Additionally, the shared memeory maximum size will need to be increased on
+Additionally, the shared memory maximum size will need to be increased on
both Sun and Digital systems; the defaults are far too small for any useful
work.
</para>
diff --git a/specs/xextproto/tog-cup.xml b/specs/xextproto/tog-cup.xml
index a35ff8c..c59e768 100644
--- a/specs/xextproto/tog-cup.xml
+++ b/specs/xextproto/tog-cup.xml
@@ -49,7 +49,7 @@ OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-
INFRINGEMENT. IN NO EVENT SHALL THE OPEN GROUP BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF
CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF, OR IN
-CONNNECTION WITH THE SOFTWARE OR THE USE OF OTHER DEALINGS IN
+CONNECTION WITH THE SOFTWARE OR THE USE OF OTHER DEALINGS IN
THE SOFTWARE.
</para>
<para>
@@ -80,7 +80,7 @@ colormap flashing.
</para>
<para>
-To encourage colormap sharing and accomodate special colormap requirements
+To encourage colormap sharing and accommodate special colormap requirements
two new protocols are defined: the first provides a way to query the
server for a list of reserved colormap entries, and the second is a way
to initialize read-only (shareable) colormap entries at specific locations
@@ -555,7 +555,7 @@ proper location) in its private colormap using XCupStoreColors.
<para>
Applications which allocate many colors in a screen's default colormap, e.g.
a color-cube or a gray-ramp, should allocate them with XCupStoreColors. By
-using XCupStoreColors the colors will be allocated sharable (read-only) and
+using XCupStoreColors the colors will be allocated shareable (read-only) and
any other application which allocates the same color will share that color
cell.
</para>
diff --git a/specs/xproto/glossary.xml b/specs/xproto/glossary.xml
index 61233e3..eefd327 100644
--- a/specs/xproto/glossary.xml
+++ b/specs/xproto/glossary.xml
@@ -350,7 +350,7 @@ These events can be generated either asynchronously from devices
or as side effects of client requests.
Events are grouped into types.
The server never sends events to a client unless the
-client has specificially asked to be informed of that type of event.
+client has specifically asked to be informed of that type of event.
However, other clients can force events to be sent to other clients.
Events are typically reported relative to a window.
<!-- .KE -->
diff --git a/specs/xproto/keysyms.xml b/specs/xproto/keysyms.xml
index e2fa0d0..9999f8d 100644
--- a/specs/xproto/keysyms.xml
+++ b/specs/xproto/keysyms.xml
@@ -1181,7 +1181,7 @@ terminals.
<para>
The KEYSYM number range #x10000000 to #x1FFFFFFF is available for
-vendor-specific extentions. Among these, the range #x11000000 to
+vendor-specific extensions. Among these, the range #x11000000 to
#x1100FFFF is designated for keypad KEYSYMs.
</para>
</sect1>
diff --git a/specs/xproto/sect1-9.xml b/specs/xproto/sect1-9.xml
index f8e8b7c..c59def1 100644
--- a/specs/xproto/sect1-9.xml
+++ b/specs/xproto/sect1-9.xml
@@ -2,7 +2,7 @@
<preface id="acknowledgements">
<title>Acknowledgements</title>
<para>
-The primary contributers to the X11 protocol are:
+The primary contributors to the X11 protocol are:
</para>
<itemizedlist>
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-22 06:31:06 +0000