Typo in NotReadableError defintion?

I noticed this yesterday: 
http://dev.w3.org/2006/webapi/FileAPI/#dfn-NotReadableError 

the NotReadableError is defined as: 

If the File or Blob cannot be read, typically due due to permission problems that occur after a reference to a File or Blob has been acquired (e.g. concurrent lock with another application) then for asynchronous read methods the error attribute MUST return a "NotFoundError" DOMError and synchronous read methods MUST throw a NotFoundError exception.

Is this a typo?  Shouldn't the instances here of "NotFoundError" be "NotReadableError"?

- sharon

Received on Friday, 4 May 2012 18:54:48 UTC