Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify and fix grammar for Formats docs #867

Merged
merged 73 commits into from
Aug 21, 2016

Conversation

weedySeaDragon
Copy link
Contributor

Like I did with PR #863 , I went through the docs in the Formats section and corrected grammar, fixed typos, and did a little clarifying and strengthening. Like #863, I didn't squash the commits in case someone wanted to review them. (But I can squash.)

…ackage' is confusing and ambiguous to new users)
…Helps to relate to the 'Output' section below)
…umentation hasn't referred to 'mapping key')
…e'. "pattern" makes it clear that the example can be generalized
…efers to a thing (an event/task that happens)
…ow this is different ("....content..." can easily be overlooked at first glance)
…les ("First we...." doesn't make sense when the code is so simple.)
@lightbend-cla-validator

Hi @weedySeaDragon,

Thank you for your contribution! We really value the time you've taken to put this together.

Before we proceed with reviewing this pull request, please sign the Typesafe Contributors License Agreement:

http://www.lightbend.com/contribute/cla

@muuki88 muuki88 added the documentation Documentation should be extended or updated label Aug 19, 2016
@muuki88
Copy link
Contributor

muuki88 commented Aug 19, 2016

😮 Wow. Thanks a lot. How long did it take to fix my english? Did you use a tool or was it plain old reading and fixing?

Squashing is not necessary. Github now supports this in the UI ;)

@weedySeaDragon
Copy link
Contributor Author

Just plain old (slightly compulsive) editing. Writing the comments for the commits is what took a while. ;-) It wasn't that much, really.
Plus I had a chunk of time to work on it.

There's some really great info in there! I'm trying to note some ideas for doing a little re-organizing to highlight some of it. (For example: There's a great explanation of mappings in there. I think it'd be powerful & much more helpful if that explanation was in the Intro: Main Concepts section.) That's for another time.

I'm happy to help. It's a great way for me to learn this!


.. code-block:: scala

libraryDependencies += "org.vafer" % "jdeb" % "1.3" artifacts (Artifact("jdeb", "jar", "jar"))

JDeb is a provided dependency so you have to add it on your own. It brings a lot of dependencies
JDeb is a provided dependency. (It is not a not an AutoPlugin_.) You have to explicitly add it on your own. It brings a lot of dependencies
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"It is not a not an AutoPlugin._" ? I think you can remove that :)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will do. (I think that shows my personal learning curve. :-) )

@muuki88
Copy link
Contributor

muuki88 commented Aug 20, 2016

So a few small notes. Beside that: Amazing work :)

@weedySeaDragon
Copy link
Contributor Author

Will make those changes in a bit. Thanks for reviewing it so quickly!

@muuki88
Copy link
Contributor

muuki88 commented Aug 21, 2016

Awesome :) You made it easy to review ;)

@muuki88 muuki88 merged commit eaae77c into sbt:master Aug 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation should be extended or updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants