docs: installation reference - reorganized callouts and footnotes, edited lists and a few other lines for pacing, clarity and flow#67
Open
ink7047 wants to merge 1 commit into
Conversation
…ited lists and a few other lines for pacing, clarity and flow -In the "practical implications" section, I wanted to use wording that made the section feel more important/compelling. If there are more accurate terms than "performance and supportability" feel free to substitute them. -In the manual installation section, I rewrote a sentence in a way that allowed it and the following sentence flow more smoothly. But I realize the language of dependencies may be more familiar and actually easier to read for developers. If that's the case, feel free to disregard the edit. -
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.
-In the "practical implications" section, I wanted to use wording that made the section feel more important/compelling. If there are more accurate terms than "performance and supportability" feel free to substitute them.
-In the manual installation section, I rewrote a sentence in a way that allowed it and the following sentence flow more smoothly. But I realize the language of dependencies may be more familiar and actually easier to read for developers. If that's the case, feel free to disregard the edit.