diff --git a/semver.md b/semver.md
index e84a0f3..194e0dc 100644
--- a/semver.md
+++ b/semver.md
@@ -101,17 +101,17 @@ intended compatibility requirements as denoted by its associated
 normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7,
 1.0.0-x.7.z.92.
 
-1. Build metadata MAY be denoted by appending a plus sign and a series of dot 
-separated identifiers immediately following the patch or pre-release version. 
-Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. 
+1. Build metadata MAY be denoted by appending a plus sign and a series of dot
+separated identifiers immediately following the patch or pre-release version.
+Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-].
 Identifiers MUST NOT be empty. Build metadata SHOULD be ignored when determining
-version precedence. Thus two versions that differ only in the build metadata, 
-have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700, 
+version precedence. Thus two versions that differ only in the build metadata,
+have the same precedence. Examples: 1.0.0-alpha+001, 1.0.0+20130313144700,
 1.0.0-beta+exp.sha.5114f85.
 
 1. Precedence refers to how versions are compared to each other when ordered.
 Precedence MUST be calculated by separating the version into major, minor, patch
-and pre-release identifiers in that order (Build metadata does not figure 
+and pre-release identifiers in that order (Build metadata does not figure
 into precedence). Precedence is determined by the first difference when
 comparing each of these identifiers from left to right as follows: Major, minor,
 and patch versions are always compared numerically. Example: 1.0.0 < 2.0.0 <
@@ -204,7 +204,7 @@ API can keep everyone and everything running smoothly.
 
 As soon as you realize that you've broken the Semantic Versioning spec, fix
 the problem and release a new minor version that corrects the problem and
-restores backwards compatibility. Even under this circumstance, it is 
+restores backwards compatibility. Even under this circumstance, it is
 unacceptable to modify versioned releases. If it's appropriate,
 document the offending version and inform your users of the problem so that
 they are aware of the offending version.
@@ -240,8 +240,8 @@ that users can smoothly transition to the new API.
 
 ### Does semver have a size limit on the version string?
 
-No, but use good judgment. A 255 character version string is probably overkill, 
-for example. Also, specific systems may impose their own limits on the size of 
+No, but use good judgment. A 255 character version string is probably overkill,
+for example. Also, specific systems may impose their own limits on the size of
 the string.
 
 About