Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.
Sign upUpdate README.md #15
+1
−1
Conversation
machawk1
requested a review
from
shawnmjones
Jul 11, 2019
This comment has been minimized.
This comment has been minimized.
|
You are correct. I am inconsistent. I wonder about the rest of the documentation now. I need to settle on a capitalization. |
shawnmjones
merged commit d51d3b3
into
master
Jul 12, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
machawk1 commentedJul 11, 2019
This PR remedies a triviality in the README, but makes it slightly more consistent.
Regarding capitalization, the project's name appears to be un-capitalized, though it happens to occur at the beginning of the sentence a few times. This is fine, albeit syntactically ambiguous (should all lowercase brands always be lowercase?), but the final header capitalizes Raintale in
The future of Raintale(cf.Building raintale). The preceding header is all lowercase.This PR simply makes the final header consistent with the instances of the name throughout the README.