s/machine/system

It was annoying me.

8 files changed, 32 insertions, 32 deletions

diff --git a/docs/install/index.html b/docs/install/index.html
index fa73a37..5d5757a 100644
--- a/docs/install/index.html
+++ b/docs/install/index.html
@@ -310,7 +310,7 @@
 			<p>
 				<b>
 					Warning: this guide will not instruct the user how to backup the original Lenovo BIOS firmware. These backups
-					are tied to each machine, and will not work on any other.
+					are tied to each system, and will not work on any other.
 					For that, please refer to <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>.
 				</b>
 			</p>
diff --git a/docs/install/r400_external.html b/docs/install/r400_external.html
index cec56b4..060b283 100644
--- a/docs/install/r400_external.html
+++ b/docs/install/r400_external.html
@@ -387,7 +387,7 @@ Please specify which chip definition to use with the -c &lt;chipname&gt; option.
 					the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/>
 					Now compare the 3 images:<br/>
 					# <b>sha512sum factory*.rom</b><br/>
-					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another machine, not
+					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not
 					the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware
 					that could be replicated in coreboot and libreboot.
 				</p>
@@ -443,7 +443,7 @@ Verifying flash... VERIFIED.
 			
 			<p>
 				When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth.
-				Then apply new paste. AS5 is also much better than the default paste used on these machines.
+				Then apply new paste. AS5 is also much better than the default paste used on these systems.
 			</p>
 			
 			<p>
diff --git a/docs/install/t400_external.html b/docs/install/t400_external.html
index 045d502..73eb3cc 100644
--- a/docs/install/t400_external.html
+++ b/docs/install/t400_external.html
@@ -364,7 +364,7 @@ Please specify which chip definition to use with the -c &lt;chipname&gt; option.
 					the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/>
 					Now compare the 3 images:<br/>
 					# <b>sha512sum factory*.rom</b><br/>
-					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another machine, not
+					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not
 					the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware
 					that could be replicated in coreboot and libreboot.
 				</p>
@@ -419,7 +419,7 @@ Verifying flash... VERIFIED.
 			
 			<p>
 				When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth.
-				Then apply new paste. AS5 is also much better than the default paste used on these machines.
+				Then apply new paste. AS5 is also much better than the default paste used on these systems.
 			</p>
 			
 			<p>
diff --git a/docs/install/t500_external.html b/docs/install/t500_external.html
index 048980a..54e6718 100644
--- a/docs/install/t500_external.html
+++ b/docs/install/t500_external.html
@@ -246,7 +246,7 @@ POMONA 5250 (correlate with the BBB guide)
 				<p>
 					When you re-assemble, you will be replacing the wifi chip
 					with another. These two screws don't hold anything together,
-					but they are included in your machine because the screw
+					but they are included in your system because the screw
 					holes for half-height cards are a different size, so
 					use these if you will be installing a half-height card:<br/>
 					<img src="images/t500/0027.jpg" alt="" />
@@ -324,7 +324,7 @@ POMONA 5250 (correlate with the BBB guide)
 				</p>
 				<p>
 					The flash chip is next to the memory slots. On this
-					machine, it was a SOIC-8 (4MiB or 32Mb) flash chip:<br/>
+					system, it was a SOIC-8 (4MiB or 32Mb) flash chip:<br/>
 					<img src="images/t500/0060.jpg" alt="" />
 				</p>
 				<p>
@@ -381,7 +381,7 @@ Please specify which chip definition to use with the -c &lt;chipname&gt; option.
 					the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/>
 					Now compare the 3 images:<br/>
 					# <b>sha512sum factory*.rom</b><br/>
-					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another machine, not
+					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not
 					the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware
 					that could be replicated in coreboot and libreboot.
 				</p>
@@ -436,7 +436,7 @@ Verifying flash... VERIFIED.
 			
 			<p>
 				When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth.
-				Then apply new paste. AS5 is also much better than the default paste used on these machines.
+				Then apply new paste. AS5 is also much better than the default paste used on these systems.
 			</p>
 			
 			<p>
diff --git a/docs/install/t60_unbrick.html b/docs/install/t60_unbrick.html
index d05078c..e92298b 100644
--- a/docs/install/t60_unbrick.html
+++ b/docs/install/t60_unbrick.html
@@ -26,7 +26,7 @@
 					Types of brick:
 					<ul>
 						<li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li>
-						<li><a href="#recovery">Brick type 2: bad rom (or user error), machine won't boot</a></li>
+						<li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li>
 					</ul>
 				</li>
 			</ul>
@@ -45,7 +45,7 @@
 				dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/>
 				dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/>
 				dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/>
-				(doing this makes the ROM suitable for use when flashing a machine that still has Lenovo BIOS running,
+				(doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running,
 				using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>.
 				(it says x60, but instructions for t60 are identical)
 			</p>
@@ -53,14 +53,14 @@
 	
 	<div class="section">
 
-		<h1 id="recovery">bad rom (or user error), machine won't boot</h1>
+		<h1 id="recovery">bad rom (or user error), system won't boot</h1>
 
 			<p>
-				In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your machine from
-				booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your machine is bricked and will not boot at all.
+				In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from
+				booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all.
 			</p>
 			<p>
-				&quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the machine, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
+				&quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
 			</p>
 
 			<p>
@@ -156,7 +156,7 @@
 			<p>
 				Remove the shielding containing the motherboard, then flip it over. Remove these screws, placing them on a steady
 				surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the
-				screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the machine:<br/>
+				screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the system:<br/>
 				<img src="../images/t60_dev/0027.JPG" alt="" /> <img src="../images/t60_dev/0028.JPG" alt="" /> <img src="../images/t60_dev/0029.JPG" alt="" />
 				<img src="../images/t60_dev/0031.JPG" alt="" /> <img src="../images/t60_dev/0032.JPG" alt="" /> <img src="../images/t60_dev/0033.JPG" alt="" />
 			</p>
diff --git a/docs/install/x200_external.html b/docs/install/x200_external.html
index dc93582..8a24761 100644
--- a/docs/install/x200_external.html
+++ b/docs/install/x200_external.html
@@ -156,7 +156,7 @@ chip on those pins?
 			</h2>
 				<p>
 					This section is for the X200. This does not apply to the X200S or X200 Tablet
-					(for those machines, you have to remove the motherboard completely, since
+					(for those systems, you have to remove the motherboard completely, since
 					the flash chip is on the other side of the board).
 				</p>
 				<p>
@@ -240,7 +240,7 @@ Please specify which chip definition to use with the -c &lt;chipname&gt; option.
 					the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/>
 					Now compare the 3 images:<br/>
 					# <b>sha512sum factory*.rom</b><br/>
-					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another machine, not
+					If the hashes match, then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not
 					the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware
 					that could be replicated in coreboot and libreboot.
 				</p>
diff --git a/docs/install/x60_unbrick.html b/docs/install/x60_unbrick.html
index 0822a71..d420cb6 100644
--- a/docs/install/x60_unbrick.html
+++ b/docs/install/x60_unbrick.html
@@ -26,7 +26,7 @@
 					Types of brick:
 					<ul>
 						<li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li>
-						<li><a href="#recovery">Brick type 2: bad rom (or user error), machine won't boot</a></li>
+						<li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li>
 					</ul>
 				</li>
 			</ul>
@@ -45,20 +45,20 @@
 				dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/>
 				dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/>
 				dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/>
-				(doing this makes the ROM suitable for use when flashing a machine that still has Lenovo BIOS running,
+				(doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running,
 				using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>.
 			</p>
 	</div>
 	
 	<div class="section">
 
-		<h1 id="recovery">bad rom (or user error), machine won't boot</h1>
+		<h1 id="recovery">bad rom (or user error), system won't boot</h1>
 			<p>
-				In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your machine from
-				booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your machine is bricked and will not boot at all.
+				In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from
+				booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all.
 			</p>
 			<p>
-				&quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the machine, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
+				&quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
 			</p>
 			<p>
 				Remove those screws:<br/>
@@ -223,7 +223,7 @@ POMONA 5250:
 				<img src="../images/x60_unbrick/0039.jpg" alt="" />
 			</p>
 			<p>
-				Connect the wifi antenna cables. At the start of the tutorial, this machine had an Intel wifi chip. Here you see I've replaced it with an 
+				Connect the wifi antenna cables. At the start of the tutorial, this system had an Intel wifi chip. Here you see I've replaced it with an 
 				Atheros AR5B95 (supports 802.11n and can be used without blobs):<br/>
 				<img src="../images/x60_unbrick/0040.jpg" alt="" />
 			</p>
diff --git a/docs/install/x60tablet_unbrick.html b/docs/install/x60tablet_unbrick.html
index 8d93f82..c64f90c 100644
--- a/docs/install/x60tablet_unbrick.html
+++ b/docs/install/x60tablet_unbrick.html
@@ -26,7 +26,7 @@
 					Types of brick:
 					<ul>
 						<li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li>
-						<li><a href="#recovery">Brick type 2: bad rom (or user error), machine won't boot</a></li>
+						<li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li>
 					</ul>
 				</li>
 			</ul>
@@ -45,20 +45,20 @@
 				dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/>
 				dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/>
 				dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/>
-				(doing this makes the ROM suitable for use when flashing a machine that still has Lenovo BIOS running,
+				(doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running,
 				using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>.
 			</p>
 	</div>
 
 	<div class="section">
 
-		<h1 id="recovery">bad rom (or user error), machine won't boot</h1>
+		<h1 id="recovery">bad rom (or user error), system won't boot</h1>
 			<p>
-				In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your machine from
-				booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your machine is bricked and will not boot at all.
+				In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from
+				booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all.
 			</p>
 			<p>
-				&quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the machine, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
+				&quot;Unbricking&quot; means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides).
 			</p>
 
 			<p>
@@ -158,7 +158,7 @@ POMONA 5250:
 			</p>
 
 			<p>
-				Reverse the steps to re-assemble your machine.
+				Reverse the steps to re-assemble your system.
 			</p>
 			
 	</div>