fixes to README formatting #1
Merged
Conversation
This file contains 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
|
FWIW - this looks like a nice clarifying cleanup of the README |
|
@jere-mie Thanks so much for the changes. We'll definitely take a look at |
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.
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.
I've made some fixes to the README markdown formatting (as well as adding a link for the lynx browser and php downloads).
Most of the changes revolve around appending two spaces to force a line break. Alternatively, a line break can be forced by adding another new line in between lines.
Also, I would suggest checking out the Links browser (different from Lynx). It's been very nice to use in my experience, and even has really good mouse support. You can check it out here: http://links.twibright.com/. You can install on debian-based systems with a simple
sudo apt install links.