On Thu, Jul 24, 2014 at 5:36 PM, KARR, DAVID <dk0...@att.com> wrote:

>  I finally finished the complete proofreading run through of the user
> guide.  This is a summary of what I fixed:
>
>
>
> ·         Minor typos, wordos, and small display problems in almost every
> chapter.
>
> ·         Too long lines in many code samples.
>
> ·         Some incorrect double quotes (changed from the plain one to the
> left and right quotes).
>
> ·         There were only a few places that I changed real content,
> either adding more explicit statements or rewording phrases.
>
> ·         Because of formatting problems with things like “literal” (not
> respecting display line length) I ended up rephrasing many statements,
> hopefully more clearly, but towards the goal of repositioning the “literal”
> strings so they didn’t wrap off the end of the line. I gave up on many of
> these if I found it would be too much reformatting to get a good result.
>
>
>
> You might have noticed the several questions I posted on the forum, those
> were the real content-related issues.
>
>
>
> The question is, what should I do now?  Normally I would just check all of
> this in and submit a pull request.  I just did a count, and there are 130
> files modified.  Is that going to be a problem?
>

Yes, a pull request is the correct way to provide these changes. Please
ensure that you rebase against the latest version before submitting.

>
>
> *From:* Szczepan Faber [mailto:szczepan.fa...@gradleware.com]
> *Sent:* Thursday, July 03, 2014 3:14 PM
> *To:* dev@gradle.codehaus.org
>
> *Subject:* Re: [gradle-dev] Question about phrase in userguide doc
>
>
>
> I think only 3 words are really important in this sentence: "groovy",
> "productivity" and "fun".
>
>
>
> Hope that helps :)
>
>
>
> Thanks for helping out with the user guide!
>
>
>
> On Thu, Jul 3, 2014 at 11:52 PM, KARR, DAVID <dk0...@att.com> wrote:
>
> I'm planning on reading and proofreading the user guide, and submitting
> the changes in a PR.  I've found a few typos and wordos in just the first
> few pages.  Usually, I find it obvious what the person meant, and can
> suggest a better wording.  However, sometimes I just can't parse what they
> were trying to say.  I found one of those ungrokable statements in the
> "overview" section, which says:
>
>         "Only by that using Groovy is the fun and productivity gain it can
> be."
>
> If I'm reading the history correctly, it looks like Hans wrote this more
> than 4 years ago.  If Hans isn't around, can someone interpret what he was
> trying to say here?
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>
>
>
> --
>
> Szczepan Faber
>
> Principal engineer@gradle; Founder@mockito
>



-- 
Darrell (Daz) DeBoer
http://www.gradleware.com

Reply via email to