Fixes #40, adding a statement about the basis of semver. From @icylace.
Fixes #12 with a new PR, updated to reflect pre-release and build metadata.
Merge pull request #91 from jeffhandley/issue-40-basis

Fixes #40, adding a statement about the basis of semver. From @icylace.
Replaces #30. Updated wording as suggested
updated as suggested
added FAQ entry regarding semver version string size. Fixes #79.
Merge pull request #96 from Tieske/master

Replaces #30, pre-release versions are unstable
Reword scenario of accidental breaking changes

Alternate proposal to #93. This fixes #38
Remove the details for pre-release and build metadata from the summary
Merge pull request #99 from mojombo/better-wording-faq

Reword scenario of accidental breaking changes
Cleaned up punctuation and format of summary
Section 9: Clarify pre-release definition

- Remove confusing 'satisfies' usage.
- Specify that pre-release identifiers cannot be empty.
Section 11: A larger set of pre-release is higher

Clarifies the comparison between, eg 1.0.0-a vs 1.0.0-a.b
Attempt to clarify precedence even more.

While this is implied, SemVer never really makes it clear that
1.9.0 < 2.1.1. It only specifies how each identifier is compared.

This commit attempts to clarify how the comparison of each identifier
relates to the comparison of the whole version.
Merge pull request #108 from mojombo/clarify-version-comparisons

Clarify version comparisons
Section 10: Clarify language around build metadata precedence

They're not the 'same version', necessarily, they're the same precedence
Clarify non-empty build metadata

- Build metadata identifiers MUST not be empty.
- Changed "are" to "have" when discussing version precedence. We usually
say a version HAS a precedence not that it IS a precedence.
Be more precise about version precedence
Merge pull request #107 from mojombo/clarify-prerelease

Section 9: Clarify pre-release definition
Merge pull request #109 from mojombo/build-metadata-clarification

Build metadata clarification