There are several spell issues in the protocol xml files.
Modify to correct them.
Bug-AGL: SPEC-4174
Signed-off-by: ZhouMingying <zhoumy@cn.fujitsu.com>
Change-Id: I052a1cb4b1a0054305899a1d83e4be0fd9d03c2b
<event name="done">
<description summary="sent when 'take_shot' finished">
- Even sent back to nofify client 'take_shot' request has completed.
+ Even sent back to notify client 'take_shot' request has completed.
</description>
<arg name="status" type="uint" enum="done_status" />
</event>
<description summary="Private extension to allow applications activate other apps">
This extension can be used by regular application to instruct to compositor
to activate or switch to other running (regular) applications. The client
- is responsbile for filtering their own app_id when receiving application id.
+ is responsible for filtering their own app_id when receiving application id.
The compositor will allow clients to bind to this interface only if the
policy engine allows it.
Ask the compositor to hide the toplevel window for window
management purposes. Depending on the window role, this request
will either display the previously active window (or the background
- in case there's no previously activate surface) or temporarly (or
+ in case there's no previously active surface) or temporarily (or
until a 'activate_app' is called upon) hide the surface. All
the surfaces are identifiable by using the app_id, and no actions are
taken in case the app_id is not/was not present.
Tell the server that this client is ready to be shown. The server
will delay presentation during start-up until all shell clients are
ready to be shown, and will display a black screen instead.
- This gives the client an oppurtunity to set up and configure several
+ This gives the client an opportunity to set up and configure several
surfaces into a coherent interface.
The client that binds to this interface must send this request, otherwise
Set the surface to act as a panel of an output. The 'edge' argument
says what edge of the output the surface will be anchored to.
After this request, the server will send a configure event with the
- correponding width/height that the client should use, and 0 for the
+ corresponding width/height that the client should use, and 0 for the
other dimension. E.g. if the edge is 'top', the width will be the
output's width, and the height will be 0.