Grammar, spelling, and formatting fixes in documentation#743
Merged
Conversation
jhusain
added a commit
that referenced
this pull request
Feb 29, 2016
Grammar, spelling, and formatting fixes in documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Besides standard English changes, I did the following:
“and”) with dumb quotes ("). In places where smart quotes were used in text, they were often wrong (two left-hand quotes or two right-hand quotes). Where they were used in code snippets, they resulted in invalid code. Jekyll converts dumb quotes to smart ones automatically anyway (ignoring code snippets).JSON.stringifywhich is a way to turn a JavaScript Array or Object into a JSON string. "JavaScript's toString algorithm" is just calling.toStringon something, like(4).toString()