* add subsections to "submit a PR" section
this allows the reader to visually separate the instructions and makes the longer git-command section less prone to trigger a TLDR (heh) when reading this part.
also, line wrapping tweaks, split a paragraph into two, and reword a couple passages for clarity
* compact the list of git commands
* CONTRIBUTING: greatly simplify the PR instructions
plus some wording tweaks here and there
* improve instructions to use tldrl
* brace expansion is not as common in the wild
removing it keeps the examples of unix features to a manageable/readable 3
* use actual commands in the git section
* use only one-liners on the git section
* add subsection header for commit message
* slight reword of licensing note
* Applying the snake_case convention throughout the repo
- Also removing the file extension where not needed
- Adding {{ }} on a few old pages
* Addressing concerns
- Added {{ }} where they were missed out
- Removed spaces inside {{ }}
- Reverting "file" to "filename" to make it clearer
* Fixing the comments on nc page
Numbered field references have been used in the first two examples,
so it's quite reasonable to take the opportunity to introduce a new (and quite useful!) concept.
In addition, this commit makes a few tweaks to the example descriptions, to make them clearer.
This involves another command, but it's such a natural extension of uniq's `-c` functionality that I feel it's warranted to show here.
We should probably add a sort to the -c example too, because uniq only deals with *sequential* line repetitions.
- Added basic command usage without any flags.
- Removed the '-h' flag as it seems to be added implicitly by the cmd.
- Added the interval parameter.
- Added the '-m' flag.
By default, grep already uses regular expressions when searching.
The example `grep -e {{^regex$}} {{path/to/file}}` is the same as `grep {{^regex$}} {{path/to/file}}`.
However, because of the comment about extended regular expressions, I mistakenly assumed `-e` was the option to enable it.
I believe most people would refer to `tldr` in this use case looking for the `-E` extended regular expressions.
With this in mind, I believe that example would be better rephrased as this pull request makes it.