* Replace Linuxish bits with per-port entities in partition sizing.

1 files changed, 2 insertions, 2 deletions

diff --git a/po/pot/partitioning.pot b/po/pot/partitioning.pot
index 2ca1c97e6..837b4fa42 100644
--- a/po/pot/partitioning.pot
+++ b/po/pot/partitioning.pot
@@ -29,13 +29,13 @@ msgstr ""
 #. Tag: para
 #: partitioning.xml:14
 #, no-c-format
-msgid "At a bare minimum, GNU/Linux needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, Linux can make much more efficient use of it. It is possible to force Linux to use a regular file as swap, but it is not recommended."
+msgid "At a bare minimum, GNU/&arch-kernel; needs one partition for itself. You can have a single partition containing the entire operating system, applications, and your personal files. Most people feel that a separate swap partition is also a necessity, although it's not strictly true. <quote>Swap</quote> is scratch space for an operating system, which allows the system to use disk storage as <quote>virtual memory</quote>. By putting swap on a separate partition, &arch-kernel; can make much more efficient use of it. It is possible to force &arch-kernel; to use a regular file as swap, but it is not recommended."
 msgstr ""
 
 #. Tag: para
 #: partitioning.xml:26
 #, no-c-format
-msgid "Most people choose to give GNU/Linux more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/Linux to fix the system. This can save you the trouble of having to reinstall the system from scratch."
+msgid "Most people choose to give GNU/&arch-kernel; more than the minimum number of partitions, however. There are two reasons you might want to break up the file system into a number of smaller partitions. The first is for safety. If something happens to corrupt the file system, generally only one partition is affected. Thus, you only have to replace (from the backups you've been carefully keeping) a portion of your system. At a bare minimum, you should consider creating what is commonly called a <quote>root partition</quote>. This contains the most essential components of the system. If any other partitions get corrupted, you can still boot into GNU/&arch-kernel; to fix the system. This can save you the trouble of having to reinstall the system from scratch."
 msgstr ""
 
 #. Tag: para