* Add newline at end of file.
* Create a uniformat in the code syntax highlighting by using the main syntax `shell` instead of the alias `bash`/`sh`.
* Added (of corrected) the missing code syntax highlighting.
* Split the shell commands from the text outputs.
* Fix JSON samples formatting.
* Checked the commands and updated the text output.
They only serve to make anyone reading the docs who doesn't find
something as simple or easy as stated feel bad about themselves, they
don't add anything valuable to the docs in these cases.
I'm aware this just an example, but it [leads readers to see it a best practise](40642df5ec (r29802440)).
Having code with `"php": ">=5.4.0"` is pretty dangerous and will probably break with next major version.
```json
{
"require": {
"php": "^5.4"
}
}
```
```json
{
"require": {
"php": "^7.1"
}
}
```
is much more safer. Promoting best and proven practise should from *Basic usage* helps people to use composer the best way they can.
What do you think?
* docs-improve:
Docs: cleanup version branches section
Docs: those/these composer/Composer
Docs: notice => note
Docs: Fix shell sample output
Docs: Add back a second clear note about hardcoded versions in VCS
Docs: HHVM is not called HipHop
Docs: versions plural, and update == rm lock&install
Docs: don't use short forms, it => composer
Docs: composer.lock lists versions, not constraints
Docs: superfluous comma & it => Composer
The confusing part is probably rather constraints and how versions work, not what they are
Docs: Clarify what "It" stands for
Finished reworking docs to clarify points about versioning (fixes#6088)
Updated basic usage and versions pages to clarify how versioning and package resolution works (refs #6088)
Added some useful overview information about repositories in the Basic Usage documentation.
Jeffrey Cafferata