(v0.8) Ch3 typos and grammar
Missing chapter number in top-level heading.
(All section numbers below refer to what the numbers *should* be, e.g. instead of just "2.", I use 3.2.)
[Margin errors] 3.2, 3.5.1
The terminal text extends off into the right margin on the PDF. Maybe you should cut back the left-side whitespace from the split-line mvn commands. (I only point this out because of the risk that it might look wrong when it goes to print in book format, depending on your page size and margins.)
3.3, First paragraph
I'm just nitpicking, but is that parenthesized callout to the previous section really necessary? It doesn't exactly clarify anything that needed clarification.
3.4, Example 3
Title is uncapitalized. Does it obey your convention?
3.4, Paragraph "This pom.xml..."
* First sentence is a comma-spliced. Just make it two sentences.
* Last sentence is comma-spliced. I suggest to use a semi-colon instead.
* Last sentence: The two commas before and after "all you need to know" are unnecessary and should be removed.
3.5.1, Second paragraph
Sentence that begins "Other," - it looks like this was written to be a list, but there's only two items. Replace the comma after "Hibernate" with the word "or".
3.5.1, Figure title
This figure title has all words capitalized. What is your convention? (Should probably be the same as that for Examples)
3.5.1, Third para
Your typesetting program has put a line break after the dash in "-Dgroupid". I bet there's away to prevent it from doing that.
3.5.1, Last para
(nitpick) Last sentence: That comma after "And" bugs me. I think it's unnecessary.
3.5.2 Figure 3 and the "install phase"
If "install" is a lifecycle phase, why isn't it in this figure? You mention it right below the figure. This is honestly impeding my understanding of the material. Does install come before or after package? (Later added: I now see that "install" is described in 3.5.4; perhaps a note here about this would be prudent.)
3.5.3 First paragraph
This paragraph, while grammatically fine, is a chore to read. It's fine at first, but seems to digress when it starts talking about goals. Why is it talking about goals here? Take out both sentences that start with "Goals" and the paragraph instantly improves, and I don't think any crucial info is lost (goals were defined in earlier sections).
3.5.3 Third para
Missing a space after the "2" footnote.
3.5.3 Figure 5
* Title: "Maven Space"... is Space a term that's supposed to be capitalized?
* In the diagram: You used singular "coordinate". Probably should be 'Every "artifact" has a unique set of coordinates.'
3.5.5 Fourth para
Typo: second-to-last sentence - change "dependencies" to "dependency's"
3.5.5 Fifth para
This paragraph's info should have come earlier! Why define "transitive dependency" here when you've been using it for the past 4 paragraphs? Maybe move this to be the third paragraph.
3.5.5 Last para
Combine the last two sentences, since the latter one's content is only relevant to the former one. I suggest linking the sentences like so: "application, where you'll need to"
(All section numbers below refer to what the numbers *should* be, e.g. instead of just "2.", I use 3.2.)
[Margin errors] 3.2, 3.5.1
The terminal text extends off into the right margin on the PDF. Maybe you should cut back the left-side whitespace from the split-line mvn commands. (I only point this out because of the risk that it might look wrong when it goes to print in book format, depending on your page size and margins.)
3.3, First paragraph
I'm just nitpicking, but is that parenthesized callout to the previous section really necessary? It doesn't exactly clarify anything that needed clarification.
3.4, Example 3
Title is uncapitalized. Does it obey your convention?
3.4, Paragraph "This pom.xml..."
* First sentence is a comma-spliced. Just make it two sentences.
* Last sentence is comma-spliced. I suggest to use a semi-colon instead.
* Last sentence: The two commas before and after "all you need to know" are unnecessary and should be removed.
3.5.1, Second paragraph
Sentence that begins "Other," - it looks like this was written to be a list, but there's only two items. Replace the comma after "Hibernate" with the word "or".
3.5.1, Figure title
This figure title has all words capitalized. What is your convention? (Should probably be the same as that for Examples)
3.5.1, Third para
Your typesetting program has put a line break after the dash in "-Dgroupid". I bet there's away to prevent it from doing that.
3.5.1, Last para
(nitpick) Last sentence: That comma after "And" bugs me. I think it's unnecessary.
3.5.2 Figure 3 and the "install phase"
If "install" is a lifecycle phase, why isn't it in this figure? You mention it right below the figure. This is honestly impeding my understanding of the material. Does install come before or after package? (Later added: I now see that "install" is described in 3.5.4; perhaps a note here about this would be prudent.)
3.5.3 First paragraph
This paragraph, while grammatically fine, is a chore to read. It's fine at first, but seems to digress when it starts talking about goals. Why is it talking about goals here? Take out both sentences that start with "Goals" and the paragraph instantly improves, and I don't think any crucial info is lost (goals were defined in earlier sections).
3.5.3 Third para
Missing a space after the "2" footnote.
3.5.3 Figure 5
* Title: "Maven Space"... is Space a term that's supposed to be capitalized?
* In the diagram: You used singular "coordinate". Probably should be 'Every "artifact" has a unique set of coordinates.'
3.5.5 Fourth para
Typo: second-to-last sentence - change "dependencies" to "dependency's"
3.5.5 Fifth para
This paragraph's info should have come earlier! Why define "transitive dependency" here when you've been using it for the past 4 paragraphs? Maybe move this to be the third paragraph.
3.5.5 Last para
Combine the last two sentences, since the latter one's content is only relevant to the former one. I suggest linking the sentences like so: "application, where you'll need to"
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
-
Inappropriate?Alright Grant, you win the prize. I've created another JIRA to track this progress:
https://issues.sonatype.org/browse/MV...
I’m thankful
Loading Profile...


EMPLOYEE