Clean up em dashes and semicolons in the docs - #79
Merged
Conversation
Replace em dashes with plain dashes and reword prose that used semicolons. Semicolons inside code blocks stay as they are since they are required there.
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
1 participant
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.
Closes #78
Our readme and docs had collected a lot of em dashes and semicolons and it made the prose read a little stiff.
This swaps every em dash for a plain dash and rewords the sentences that used semicolons so they flow on their own. The semicolons still sitting in code blocks stay as they are because the bash loops, the nginx config, and the SQL all need them.
Docs only, no behavior change.