[wayland-protocols v2] linux-dmabuf: clarify format event description

[Varad Gautam]

From: Varad Gautam <varad.gautam at collabora.com>

clearly state the request name in format event to avoid abmiguous
interpretation between 'zwp_linux_buffer_params_v1::create' and
'zwp_linux_dmabuf_v1::create_params' requests.

v2: grammar fixup (Yong Bakos)

Suggested-by: Yong Bakos <ybakos at humanoriented.com>
Signed-off-by: Varad Gautam <varad.gautam at collabora.com>
Reviewed-by: Yong Bakos <ybakos at humanoriented.com>
---
 unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml b/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
index cc5d604..0b22721 100644
--- a/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
+++ b/unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
@@ -105,7 +105,8 @@
         binds to this interface. A roundtrip after binding guarantees
         that the client has received all supported formats.
 
-        For the definition of the format codes, see create request.
+        For the definition of the format codes, see the
+        zwp_linux_buffer_params_v1::create request.
 
         XXX: Can a compositor ever enumerate them?
       </description>
-- 
2.6.2