summaryrefslogtreecommitdiff
path: root/en/boot-installer
diff options
context:
space:
mode:
Diffstat (limited to 'en/boot-installer')
-rw-r--r--en/boot-installer/ia64.xml2
-rw-r--r--en/boot-installer/sparc.xml2
2 files changed, 2 insertions, 2 deletions
diff --git a/en/boot-installer/ia64.xml b/en/boot-installer/ia64.xml
index 8b4a7e9cb..68ba99888 100644
--- a/en/boot-installer/ia64.xml
+++ b/en/boot-installer/ia64.xml
@@ -342,7 +342,7 @@ The only difference is how the installation kernel is loaded.
The EFI Boot Manager can load and start programs from a server on
the network.
Once the installation kernel is loaded and starts, the system install
-will proceed thru the same steps as the CD install with the exception
+will proceed through the same steps as the CD install with the exception
that the packages of the base install will be loaded from the network
rather than the CD drive.
diff --git a/en/boot-installer/sparc.xml b/en/boot-installer/sparc.xml
index cea9db730..4a82c9647 100644
--- a/en/boot-installer/sparc.xml
+++ b/en/boot-installer/sparc.xml
@@ -37,7 +37,7 @@ command which is simply an alias to boot from the SCSI device on ID 6
<title>Booting from Floppies</title>
<para>
-Floppy images are currently only available for sparc32, but, for techinical
+Floppy images are currently only available for sparc32, but, for technical
reasons, not for official releases. (The reason is that they can only be
built as root, which is not supported by our build daemons.)
Look under <quote>daily built images</quote> on the