page 7
"error support" -> exaption handling
application level error recovery strategies

page 16
the language binding specifications MUST, however, strive...
"however" seems redundand, and reduces the sentance clarity 

page 17
are guaranteed to not to share -> MUST NOT
(recommendation)

page 22
the parameters is always as follows >
use MUST.

these method do not cause -> MUST NOT...?

page 22: the description of resource deaalocation policies...
page 20: de-allocation (last line)
-> use one notation.

page 25:
the saga core wg spent....
?how is this relevant to the specs? -> 
less personal?

page 29:
paragraph SAGA implementations should...

the sentance: The NotImplemented exception is 
listed....
-> the sentance is unclear, what is the message?

page 32:
(A)the specific.. (B)... -> before you used (a), (b)

(e.g. the error 'file does not exist'...) 
comment: formulation of the sentance is not the best.
The application could have different program flows
depending on the fact if the file exists or not,
but if app tries to open the file, usually because
it needs the info.

page 33:
"most specific exeptions" -> from the text it is clear
what is supposed to be doing, but the description is
not descriptive enough.

page 38:
in the examples for NoSuccess you have also "invalid input parameter",
which is also handled by InvalidParameter exception -> could lead
to different implementations...

page 38:
the saga::exception CONSTRUCTOR could throw "OutOfMemmory" 
or is this handled by some other exception?

page 39:
In the notes you mention "IncorrectState" exc. -> not  mentioned
in the "Throws",

page 43:
clone: if the method is not calling backend why "NoSuccess"?

page 47:
kept alive until the last of that sessions objects gets ...
suggestion: session's objects gets...
-> check with a native speaker

page 48:
dafault saga::context instances on a session can be removed
-> CAN.

page 51:
a context MUST issue an error -> reise exception.

for application level AAA -> what AAA stands for?

page 54:
constructor throws BadParameter or NotImplemented as described in Notes

page 55:
in the definition saga:file CONSTRUCTOR(session, URL).
-> example reversed order of parameters,

page 56:
this interface IS-A attribute. why "IS-A"??

in the want of a better name -> bad formulation

page 60:
If the default value is given...
?? sentance is not clear.

page 61:
InvalidState should be added in the Throws.
(mentioned so in the text - when the attribute 'goes away')

page 64: in what case you throw PermissionDenied in
"find_attributes" method?

page 65: "attribute_exists"
when "DoesNotExist" should be thrown?

page 70:
Instances of these classes can passed to monitorable SAGA object,
-> missing "be" before passed.

page 103/104:
what is the purpose of adding a task to task_container more than once?

page 105:
wait method:
a wait_mode could support more advanced task selection (not just all/any)

page 106:
remove double "Throws" on cancel and get_tasks methods.

page 107: 
definition of the state class? ?reference?

get_states
-> does the return array provide state, which links task cookie with task state? if not how do you link task with state?


page 112:
Does BES defines StagingIn or Stage-In state?

page 113:
"job ID" and "job id" are both used.

page 118: 
WallclockSoftLimit
"This attribute is..." missing end of the sentance.

page 119:
"back end" -> backend (back end is found 4 times in document).

page 121:
wait(2) -> the wait_mode enum is not jet defined

page 124:
there should be much overlap between -> bad sentance formulation.

page 127:
this is a convenience routine build on the create_job
-> on top of create_job.

page 110:
"job server" is this job_service


page 217:
get_url -> Has double Throws definition.