# HG changeset patch
# User František Kučera <franta-hg@frantovo.cz>
# Date 1569965012 -7200
# Node ID bc2043705ec555ad76c01584b42cca9e4437a5c9
# Parent  07858e00622bf85e648eb8d015392409def4dd5b
small fixes, typos

diff -r 07858e00622b -r bc2043705ec5 text/ssm.en.xml
--- a/text/ssm.en.xml	Tue Oct 01 23:20:39 2019 +0200
+++ b/text/ssm.en.xml	Tue Oct 01 23:23:32 2019 +0200
@@ -59,7 +59,7 @@
 		</item>
 		<item>
 			<id>f39b90ae-0054-467e-a9e2-43379b7c2331</id>
-			<text>If the software is distributed with a hardware, the hardware must support instalation of independently built software without any restrictions or requirements (e.g. digital signature from the original author).</text>
+			<text>If the software is distributed with a hardware, the hardware must support installation of independently built software without any restrictions or requirements (e.g. digital signature from the original author).</text>
 		</item>
 	</chapter>
 	
@@ -113,7 +113,7 @@
 		</item>
 		<item>
 			<id>dd013325-bf22-43d3-9579-0e272e2ac344</id>
-			<text>APIs, file formats and protocols might (and usually should) be semanticly versioned independently from the implementation.</text>
+			<text>APIs, file formats and protocols might (and usually should) be semantically versioned independently from the implementation.</text>
 			<note>In such case, there should be a table documenting which API/format/protocol version matches which implementation version.</note>
 		</item>
 		<item>
@@ -124,7 +124,7 @@
 		</item>
 		<item>
 			<id>ae33d206-4988-44ec-b8e2-3120019fcf2f</id>
-			<text>Do not remove features unless they are really obsolete, unused or unrepairably broken.</text>
+			<text>Do not remove features unless they are really obsolete, unused or irreparably broken.</text>
 		</item>
 		<item>
 			<id>c542336a-fce8-412c-a8dd-1328c1a884ec</id>
@@ -333,7 +333,7 @@
 		</item>
 		<item>
 			<id>a3b0c164-4dde-4e33-b3be-5478d2a187e2</id>
-			<text>if not, it should be documented, why and how build products mihgt differ, and there should be plan/task to make it reproducible</text>
+			<text>if not, it should be documented, why and how build products might differ, and there should be plan/task to make it reproducible</text>
 		</item>
 	</chapter>
 	
@@ -435,7 +435,7 @@
 			</item>
 			<item>
 				<id>c9f4d9f4-f959-48ad-bc68-6720dd4596e3</id>
-				<text>If there is no default, the encoding must be specified in the metadata attached (e.g. protocol headers, extended attributes on filesystem) to the actual data or at least at the begining of the data (like declaration in XML format).</text>
+				<text>If there is no default, the encoding must be specified in the metadata attached (e.g. protocol headers, extended attributes on filesystem) to the actual data or at least at the beginning of the data (like declaration in XML format).</text>
 			</item>
 		</item>
 		<item>