Commit 8f4ec2fc authored by Alan Coopersmith's avatar Alan Coopersmith 🛫

Fix various typos & spelling errors across the docs

Signed-off-by: Alan Coopersmith's avatarAlan Coopersmith <alan.coopersmith@oracle.com>
parent 36941875
......@@ -239,7 +239,7 @@ The next section describes what is new in the latest version
The XCB libraries have begun adding support for the GLX and XKB
extensions. This work is not yet complete in this release,
and not all of the functionality available through these extensions
is accessibile via the XCB APIs. Some of this effort was funded
is accessible via the XCB APIs. Some of this effort was funded
by past Google Summer of Code projects.
</para>
</listitem>
......
......@@ -292,7 +292,7 @@ setxkbmap -model logicordless -layout "us,cz,de" \
<title>Basic Global Options</title>
<para>
For a list of available options, with a short decription of what they do,
For a list of available options, with a short description of what they do,
see the section starting with <quote><literal>! option</literal></quote> in the
<filename>rules/*.lst</filename> files.
</para>
......
......@@ -92,7 +92,7 @@ main modules:
<para>
Tables that defines translation from keyboard scan codes into reasonable
symbolic names, maximum, minimum legal keycodes, symbolic aliases and
description of physically present LED-indicators. The primary sence of
description of physically present LED-indicators. The primary sense of
this component is to allow definitions of maps of symbols (see below)
to be independent of physical keyboard scancodes. There are two main
naming conventions for symbolic names (always four bytes long):
......@@ -670,7 +670,7 @@ the first case (the Lock itself is included in the list of modifiers but
combinations with this modifier aren't mentioned in the map statements)
the internal capitalization rules will be applied to the symbol from the first
level. But in the second case the capitalization will be applied to the symbol
chosen accordingly to he first modifier - and this can be the symbol from the
chosen accordingly to the first modifier - and this can be the symbol from the
first as well as from the second level.
</para>
......
......@@ -206,7 +206,7 @@ Component Integration Laboratories, Inc.
Draper Laboratory.
Electronic Book Technologies, Inc.
Gallium Software, Inc.
Georgia Institiute of Technology
Georgia Institute of Technology
Human Designed Systems, Inc.
INRIA \- Institut National de Recherche en Informatique et en Automatique
Integrated Computer Solutions, Inc.
......
......@@ -5486,7 +5486,7 @@ The root window of the screen on which the colormap is installed
<row>
<entry>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;data[0]</entry>
<entry>
the timestampe of the event that caused the client to start or stop
the timestamp of the event that caused the client to start or stop
installing colormaps
</entry>
</row>
......@@ -6828,7 +6828,7 @@ Contain the window ID of the client leader window
<para>
A client must withdraw all of its top-level windows on the same display
before modifiying either the WM_CLIENT_LEADER or the SM_CLIENT_ID property
before modifying either the WM_CLIENT_LEADER or the SM_CLIENT_ID property
of its client leader window.
</para>
......@@ -8533,7 +8533,7 @@ request has been added.
<listitem>
<para>
<!-- .bP -->
[P49] A convention on discrimated names has been added.
[P49] A convention on discriminated names has been added.
</para>
</listitem>
<listitem>
......
......@@ -434,7 +434,7 @@ as appropriate.
<!-- .LP -->
The
<function>FontName</function>
is a structured, parsable string (of type STRING8)
is a structured, parseable string (of type STRING8)
whose Backus-Naur Form syntax description is as follows:
</para>
<!-- .IN "FontName Syntax" -->
......
......@@ -576,7 +576,7 @@
</row>
<row>
<entry><literal>DixForceAccess</literal></entry>
<entry>The device cursor is being overriden by a grab.</entry>
<entry>The device cursor is being overridden by a grab.</entry>
<entry>GrabPointer, GrabButton</entry>
</row>
<row>
......@@ -1036,7 +1036,7 @@
<section id="audit_avail_hook">
<title>Auditing Hooks</title>
<para>Two hooks provide basic auditing support. The begin hook is called immediately before an incoming client request is dispatched and before the dispatch hook is called (refer to <xref linkend="core_dispatch_hook"/>). The end hook is called immedately after the processing of the request has finished. The hook argument is a pointer to a structure of type <type>XaceKeyAvailRec</type>. This structure contains a
<para>Two hooks provide basic auditing support. The begin hook is called immediately before an incoming client request is dispatched and before the dispatch hook is called (refer to <xref linkend="core_dispatch_hook"/>). The end hook is called immediately after the processing of the request has finished. The hook argument is a pointer to a structure of type <type>XaceKeyAvailRec</type>. This structure contains a
<structfield>client</structfield> field of type <type>ClientPtr</type>,
and a <structfield>requestResult</structfield> field of type <type>int</type>.</para>
<para>The <structfield>client</structfield> field refers to client making the request.</para>
......
......@@ -164,7 +164,7 @@ the following actions, listed roughly in order of severity:
<listitem>
<para>
Execute the request normally. This is the right choice when we decide that a
particlar threat is not serious enough to worry about.
particular threat is not serious enough to worry about.
</para>
</listitem>
<listitem>
......@@ -212,7 +212,7 @@ the desired functionality.
In some cases we will suggest returning an Access error where the X protocol
does not explicitly allow one. These new Access errors arise when a client
can only perform a (non-empty) subset of the defined operations on a
resource. The disallowed operations cause Access errors. The resiource at
resource. The disallowed operations cause Access errors. The resource at
issue is usually a root window.
</para>
......@@ -1069,7 +1069,7 @@ Defense: send Window error.
<para>
A client can use SendEvent to cause events of any type to be sent to windows
of other clients. Similarly, a client could SendEvent to one of its own
windows with propogate set to True and arrange for the event to be propogated
windows with propagate set to True and arrange for the event to be propogated
up to a window it does not own. Clients can detect events generated by
SendEvent, but we cannot assume that they will.
</para>
......@@ -2177,7 +2177,7 @@ likely to confuse the user. We propose to do nothing about this threat.
<title>Errors</title>
<para>
There appear to be no threats related to procotol errors.
There appear to be no threats related to protocol errors.
</para>
</chapter>
......
......@@ -135,7 +135,7 @@ AppGroup's root window ID, and if it is the same, True is returned.
If neither case is true, then False is returned.
</para>
<para>
XagConnectionInfo returns an abreviated version of the connection
XagConnectionInfo returns an abbreviated version of the connection
setup information. When an embedded AppGroup is created the server
returns only the information about the [UI] screen that the
application is embedded within in the connection setup in order to
......
......@@ -141,7 +141,7 @@ disconnect time for reasons described below.
<para>
Now that we know what needs to be done and why, let's walk through the
sequnce of events.
sequence of events.
</para>
<para>
......@@ -279,7 +279,7 @@ extensions don't exist.
<para>
To prevent untrusted clients from using extensions by guessing their major
opcode, one of two new Proc vectors are used by untusted clients,
opcode, one of two new Proc vectors are used by untrusted clients,
<function>UntrusedProcVector</function> and
<function>SwappedUntrustedProcVector</function>. These have the same contents
as <function>ProcVector</function> and
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment