mchitre
commented
4 years ago [Was] RF links are used for mid range communication in air. [Should be] mid-range
Fixed.
[Was] We dub such links as Sneakernet links . [Should be] links.
Not a bug in the text. Rendering framework bug for HTML (pdf looks fine). Unfixable.
[Was] The Unet framework provides core services, messages, agents and APIs needed by UnetStack. The Unet basic stack is a collection of agents providing services and functionality required by typical Unets. These agents, together with the Unet framework, are sufficient to build fully functional Unets. [Could be] (better differentiated definitions; currently too much overlap and poor distinction for a reader to make proper sense of the terms, 'framework' and 'stack')
I can't think of a way to differentiate better. @su-nat, if you have suggestions on specific wording, happy to consider.
[Was] The components are packaged into various editions . The community edition is downloadable free of charge [Should be] The components are packaged into various editions. The community edition is downloadable free of charge //remove extra underline after the words 'editions' and 'downloadable'.
Rendering framework bug for HTML (pdf looks fine). Unfixable.
[Was] Figure 2. An overview of UnetStack components. [Should be] Figure 2. An overview of UnetStack components //no full-stop after fragmented sentences
Looks ugly and inconsistent. Sticking with the way it is.
[Was] Unet audio is a sound card based realtime software defined open architecture acoustic modem (SDOAM) [Should be] Unet audio is a sound-card-based realtime software-defined open architecture acoustic modem (SDOAM) //hyphenation //seems clunky, but that's what conveys the meaning most unambiguously, which is, indeed the purpose of hyphens in the first place!
Double hyphens in a single word is ugly. I'm chosen not to hyphenate "soundcard", so it is now "soundcard-based".
General note: underlining of space after a word is to be avoided; this problem exists in several places. Would you like those to be explicitly called out, or can you fix it programmatically?
There is no problem with the source text. This is a rendering framework bug for HTML (pdf looks fine). Unfixable.
[Was] sends a RTS PDU [Should be] sends an RTS PDU
Fixed.
(Fixed = text updated, will be updated online in the next release)
Unet 1.1: [Was] RF links are used for mid range communication in air. [Should be] mid-range
[Was] We dub such links as Sneakernet links . [Should be] links.
[Was] The Unet framework provides core services, messages, agents and APIs needed by UnetStack.
The Unet basic stack is a collection of agents providing services and functionality required by typical Unets. These agents, together with the Unet framework, are sufficient to build fully functional Unets.
[Could be] (better differentiated definitions; currently too much overlap and poor distinction for a reader to make proper sense of the terms, 'framework' and 'stack')
[Was] The components are packaged into various editions . The community edition is downloadable free of charge [Should be] The components are packaged into various editions. The community edition is downloadable free of charge //remove extra underline after the words 'editions' and 'downloadable'.
[Was] Figure 2. An overview of UnetStack components. [Should be] Figure 2. An overview of UnetStack components //no full-stop after fragmented sentences
[Was] Unet audio is a sound card based realtime software defined open architecture acoustic modem (SDOAM) [Should be] Unet audio is a sound-card-based realtime software-defined open architecture acoustic modem (SDOAM) //hyphenation //seems clunky, but that's what conveys the meaning most unambiguously, which is, indeed the purpose of hyphens in the first place!
General note: underlining of space after a word is to be avoided; this problem exists in several places. Would you like those to be explicitly called out, or can you fix it programmatically?
---- Adding to this list below: piggyback! :) ----
[Was] sends a RTS PDU [Should be] sends an RTS PDU