Description: - Section 2.
--General: It would be helpful if the terms were alphabetized.
--Node: "We use the term "Node" to refer to …" -> "Refers to …"
Section 5.3.1.1 [6.3.1.1]: First two sentences can be reworded more succinctly - you're not really providing definitions here, put rather describing the syntax for and providing examples illustrative of the presentation language.
OLD: The following definitions are used throughout RELOAD and so are defined here. They also provide a convenient introduction to how to read the presentation language.
NEW: This section provides an introduction to the presentation language used throughout RELOAD.
Section 5.5.1.6 [6.5.1.6]: Add references for SCTP and DCCP.
Section 9.7.4.3 [10.7.4.3], 3rd para:
-- Remove "Note to implementers". Text already highlights that the text isspecific to implementations.
Section 9.8 [10.8]: "For this topology plugin" -> "For Chord-RELOAD"
Section 11 [12]:
General: there are no labels for any of the call flows, so it's not always clear what the text is referring to. In general, I think the text precedes the flow.
Section 6.1.1, last bullet: "later" -> "latter"
Section 6.1.3: Shouldn't this be "For example," rather than "I.e.,"? If "I.e.," is appropriate in that those are the only routing algorithms which might be used, then I would suggest adjusting the sentence structure by using words rather than the abbreviation (it's debatable whether the latter is grammatically correct) to something like. "This means that a node…".
Notes: Note that this contains to all the nits that are not yet fixed.
deanwillis
commented
11 years ago
From: Mary Barnes
Description: - Section 2.
--General: It would be helpful if the terms were alphabetized. --Node: "We use the term "Node" to refer to …" -> "Refers to …"
Notes: Note that this contains to all the nits that are not yet fixed.