Fix inconsistencies in CHROMIUM_sync_point.txt.

gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt

Index: gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt
diff --git a/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt b/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt
index 0a0a808f19ea5edcf4bb7c17893074c5f9b58e14..3c1f0e71ffec16a7b2b47b0230683f7a0f6bc4b7 100644
--- a/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt
+++ b/gpu/GLES2/extensions/CHROMIUM/CHROMIUM_sync_point.txt
@@ -8,7 +8,7 @@ Name Strings
 
 Version
 
-    Last Modifed Date: September 8, 2015
+    Last Modifed Date: November 20, 2015
 
 Dependencies
 
@@ -63,7 +63,7 @@ New Procedures and Functions
     InsertFenceSyncCHROMIUM was called. The <sync_token> can be passed and
     used by any context on the same server, including other context groups.
 
-    <sync_token> returns a GL_SYNC_POINT_SIZE_CHROMIUM byte sized name.
+    <sync_token> returns a GL_SYNC_TOKEN_SIZE_CHROMIUM byte sized name.
 
     The command
 
@@ -86,11 +86,11 @@ New Procedures and Functions
 
     causes the current context to stop submitting commands until the specified
     fence sync becomes signaled. This is implemented as a server-side wait.
-    <sync_token> is a sync token generated by GenSyncPointCHROMIUM. If
+    <sync_token> is a sync token generated by GenSyncTokenCHROMIUM. If
     <sync_token> was generated by GenUnverifiedSyncTokenCHROMIUM and the
     corresponding fence sync context required more than just flush ordering
     to guarantee synchronization, a INVALID_OPERATION error is generated. If
-    <sync_token> isn't a valid sync token returned by GenSyncPointCHROMIUM or
+    <sync_token> isn't a valid sync token returned by GenSyncTokenCHROMIUM or
     GenUnverifiedSyncTokenCHROMIUM, the result is undefined.
 
 New Tokens
@@ -102,10 +102,10 @@ New Tokens
 Errors
 
     INVALID_VALUE is generated if the <fence_sync> parameter of
-    GenSyncPointCHROMIUM is not a valid local fence sync name.
+    GenSyncTokenCHROMIUM is not a valid local fence sync name.
 
     INVALID_OPERATION is generated if the <fence_sync> parameter of
-    GenSyncPointCHROMIUM has not been flushed to the server.
+    GenSyncTokenCHROMIUM has not been flushed to the server.
 
     INVALID_OPERATION is generated if the <sync_token> parameter of
     WaitSyncTokenCHROMIUM was generated using GenUnverifiedSyncTokenCHROMIUM,