[PATCH 06/21] docs: Consistency fixes

[Jason Ekstrand]

Looks Good!
--Jason Ekstrand

On Sat, Mar 30, 2013 at 12:11 AM,  <matthias.clasen at gmail.com> wrote:
> From: Matthias Clasen <mclasen at redhat.com>
>
> Say 'object ID' throughout.
> ---
>  doc/Wayland/en_US/Protocol.xml | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/doc/Wayland/en_US/Protocol.xml b/doc/Wayland/en_US/Protocol.xml
> index 9bc8232..58a5962 100644
> --- a/doc/Wayland/en_US/Protocol.xml
> +++ b/doc/Wayland/en_US/Protocol.xml
> @@ -9,15 +9,15 @@
>      <title>Basic Principles</title>
>      <para>
>        The wayland protocol is an asynchronous object oriented protocol.  All
> -      requests are method invocations on some object.  The request include
> -      an object id that uniquely identifies an object on the server.  Each
> +      requests are method invocations on some object.  The requests include
> +      an object ID that uniquely identifies an object on the server.  Each
>        object implements an interface and the requests include an opcode that
>        identifies which method in the interface to invoke.
>      </para>
>      <para>
>        The server sends back events to the client, each event is emitted from
>        an object.  Events can be error conditions.  The event includes the
> -      object id and the event opcode, from which the client can determine
> +      object ID and the event opcode, from which the client can determine
>        the type of event.  Events are generated both in response to requests
>        (in which case the request and the event constitutes a round trip) or
>        spontaneously when the server state changes.
> --
> 1.8.1.4
>
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel