summaryrefslogtreecommitdiff
path: root/protocol
diff options
context:
space:
mode:
authorChristopher Michael <cpmichael@osg.samsung.com>2015-07-14 01:21:40 -0700
committerBryce Harrington <bryce@osg.samsung.com>2015-07-14 01:23:28 -0700
commita820b4d635854fb1bf21bc7a25d13a0599ce15ce (patch)
treebd431b4b6c5da8496e016030e3c532fcb12e3ccd /protocol
parent35e7b10d44b6dc389bbc948574b756f53b858807 (diff)
downloadweston-a820b4d635854fb1bf21bc7a25d13a0599ce15ce.tar.gz
Documentation for the prepare_lock_surface event description, is incorrect
Documentation for the prepare_lock_surface event description is incorrect. The summary says "Tell the client..." however the full-text description says "tell the shell..." Signed-off-by: Chris Michael <cp.michael@samsung.com> Reviewed-by: Bryce Harrington <bryce@osg.samsung.com> Acked-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk> [This time include the actual changes.]
Diffstat (limited to 'protocol')
-rw-r--r--protocol/desktop-shell.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/protocol/desktop-shell.xml b/protocol/desktop-shell.xml
index fb0b7481..dd81574a 100644
--- a/protocol/desktop-shell.xml
+++ b/protocol/desktop-shell.xml
@@ -44,9 +44,9 @@
<event name="prepare_lock_surface">
<description summary="tell the client to create, set the lock surface">
- Tell the shell we want it to create and set the lock surface, which is
+ Tell the client we want it to create and set the lock surface, which is
a GUI asking the user to unlock the screen. The lock surface is
- announced with 'set_lock_surface'. Whether or not the shell actually
+ announced with 'set_lock_surface'. Whether or not the client actually
implements locking, it MUST send 'unlock' request to let the normal
desktop resume.
</description>