# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1471990301 -7200
# Node ID bd140638915fcecc305f77fbc6d304c83dc6fa97
# Parent  60e67a0c8b61a2cbd3b928781ec61fa72d79544b
Semantic versioning

diff -r 60e67a0c8b61 -r bd140638915f ssm-en.xhtml
--- a/ssm-en.xhtml	Wed Aug 24 00:05:10 2016 +0200
+++ b/ssm-en.xhtml	Wed Aug 24 00:11:41 2016 +0200
@@ -37,13 +37,13 @@
 	
 		<h2>Semantic versioning</h2>
 		<ul>
-			<li>strongly recommended</li>
-			<li>required when the package is suposed to be used as dependency by others</li>
-			<li>if there is need of some marketing or cool versioning/codenames like Ultrasonic Umbrella or 2016, they should be used in addition to semantic versioning, not instead it</li>
-			<li>once publicly released, the package must not be changed anymore – if a change (even small fix) is needed, new version number must be assigned</li>
+			<li><a href="http://semver.org/">Semantic versioning</a> is strongly recommended.</li>
+			<li>Especially when the software is suposed to be used as dependency by others.</li>
+			<li>If there is a need of some marketing or cool versioning/codenames like Ultrasonic Umbrella or 2016, they should be used in addition to semantic versioning, not instead of it.</li>
+			<li>Once publicly released, the package must not be changed anymore – if a change (even a small fix) is needed, new version number must be assigned.</li>
 			<li>
 				APIs, file formats and protocols might be semanticly versioned independently from the implementation;
-				in such case, there should be a table documenting which API/format/protocol version matches which implementation version
+				in such case, there should be a table documenting which API/format/protocol version matches which implementation version.
 			</li>
 		</ul>