The correct names for these are RRCrtcChangeNotifyMask and
RROutputChangeNotifyMask, respectively.

Signed-off-by: Aaron Plattner <[email protected]>
---
 randrproto.txt | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/randrproto.txt b/randrproto.txt
index 2123e7e..afd6921 100644
--- a/randrproto.txt
+++ b/randrproto.txt
@@ -406,19 +406,19 @@ The name of this extension is "RANDR".
 
        New for version 1.2:
 
-       If 'enable' contains RRCrtcChangeMask, RRCrtcChangeNotify events
+       If 'enable' contains RRCrtcChangeNotifyMask, RRCrtcChangeNotify events
        will be sent when a the configuration for a CRTC associated with the
        screen changes, either through this protocol extension or due to
        detected external changes. RRCrtcChangeNotify may also be sent when
        this request executes if the CRTC configuration has changed since
        the client connected, to avoid race conditions.
 
-       If 'enable' contains RROutputChangeMask, RROutputChangeNotify events
-       will be sent when a the configuration for an output associated with
-       the screen changes, either through this protocol extension or due to
-       detected external changes. RROutputChangeNotify may also be sent
-       when this request executes if the output configuration has changed
-       since the client connected, to avoid race conditions.
+       If 'enable' contains RROutputChangeNotifyMask, RROutputChangeNotify
+       events will be sent when a the configuration for an output associated
+       with the screen changes, either through this protocol extension or due
+       to detected external changes. RROutputChangeNotify may also be sent when
+       this request executes if the output configuration has changed since the
+       client connected, to avoid race conditions.
 
        If 'enable' contains RROutputPropertyNotifyMask,
        RROutputPropertyNotify events will be sent when properties change on
-- 
1.8.5.2

_______________________________________________
[email protected]: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

Reply via email to