diff --git a/semver.md b/semver.md
index 306aeb3..257e329 100644
--- a/semver.md
+++ b/semver.md
@@ -79,18 +79,12 @@ MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]. Pre-release
 versions satisfy but have a lower precedence than the 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. Unique build metadata MAY be denoted by appending a plus `+` and a series of
-dot separated identifiers immediately following the patch or pre-release
-version. While identifiers MUST be comprised of only ASCII alphanumerics and
-hyphens [0-9A-Za-z\-], their values only define uniqueness. The Semantic
-Versioning specation intentionally omits precedence rule definitions for
-comparing two versions where only build metadata is different. Furthermore,
-this specification does not define precedence rules for comparing a version
-with build metadata to a version without build metadata. Specific
-implementations of Semantic Versioning MAY define their own precedence rules
-for those scenarios, but due to the lack of precedence defined within the
-specification, consumers SHOULD NOT rely on build metadata when taking
-dependencies on packages.
+1. Build metadata MAY be denoted by appending a plus + and a series of dot 
+separated identifiers immediately following the patch or pre-release version. 
+Identifiers MUST be comprised of only ASCII alphanumerics and hyphen 
+[0-9A-Za-z-]. Build metadata SHOULD be ignored when determining version 
+precedence. Thus two packages with the same version, but different build 
+metadata are considered to be the same version.
 
 1. Precedence MUST be calculated by separating the version into major, minor,
 patch, pre-release, and build identifiers in that order. Major, minor, and