Fix spelling/wording issues

Found by using:
  codespell --builtin clear,rare,usage,informal,code,names

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

7 files changed, 15 insertions, 15 deletions

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>