Fix "partitioning" part for non-Linux ports.

2 files changed, 6 insertions, 6 deletions

diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml
index d77cefe85..dcb0009c0 100644
--- a/en/partitioning/partition-programs.xml
+++ b/en/partitioning/partition-programs.xml
@@ -20,7 +20,7 @@ your architecture.
 
 Recommended partitioning tool in Debian. This Swiss army knife can
 also resize partitions, create filesystems
-<phrase arch="x86"> (<quote>format</quote> in Windows speak)</phrase>
+<phrase arch="any-x86"> (<quote>format</quote> in Windows speak)</phrase>
 and assign them to the mountpoints.
 
 </para></listitem>
@@ -114,7 +114,7 @@ One of these programs will be run by default when you select
 to use a different partitioning tool from the command line on VT2, but this
 is not recommended.
 
-</para><para arch="x86">Remember to mark your boot partition as
+</para><para arch="any-x86">Remember to mark your boot partition as
 <quote>Bootable</quote>.
 
 </para><para condition="mac-fdisk.txt">
diff --git a/en/partitioning/partition/x86.xml b/en/partitioning/partition/x86.xml
index a0b5366f2..01979f2e7 100644
--- a/en/partitioning/partition/x86.xml
+++ b/en/partitioning/partition/x86.xml
@@ -35,7 +35,7 @@ partitions.  You can create up to 60 logical partitions per extended
 partition; however, you can only have one extended partition per
 drive.
 
-</para><para>
+</para><para arch="linux-any">
 
 Linux limits the partitions per drive to 15 partitions for SCSI disks
 (3 usable primary partitions, 12 logical partitions), and 63
@@ -63,8 +63,8 @@ kernel from the disk into RAM.  If the BIOS int 0x13 large disk access
 extensions are found to be present, they will be utilized. Otherwise,
 the legacy disk access interface is used as a fall-back, and it cannot
 be used to address any location on the disk higher than the 1023rd
-cylinder.  Once Linux is booted, no matter what BIOS your computer
-has, these restrictions no longer apply, since Linux does not use the
+cylinder.  Once &arch-kernel; is booted, no matter what BIOS your computer
+has, these restrictions no longer apply, since &arch-kernel; does not use the
 BIOS for disk access.
 
 </para><para>
@@ -86,7 +86,7 @@ should suffice) partition at the beginning of the disk to be used as
 the boot partition, and then create whatever other partitions you wish
 to have, in the remaining area.  This boot partition
 <emphasis>must</emphasis> be mounted on <filename>/boot</filename>,
-since that is the directory where the Linux kernel(s) will be stored.
+since that is the directory where the &arch-kernel; kernel(s) will be stored.
 This configuration will work on any system, regardless of whether LBA
 or large disk CHS translation is used, and regardless of whether your
 BIOS supports the large disk access extensions.