1 files changed, 12 insertions, 12 deletions
diff --git a/fi/post-install/kernel-baking.xml b/fi/post-install/kernel-baking.xml
index 35a4b92c5..1c8f06300 100644
--- a/fi/post-install/kernel-baking.xml
+++ b/fi/post-install/kernel-baking.xml
@@ -1,37 +1,37 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 31881 untranslated -->
+<!-- original version: 31905 untranslated -->
 
  <sect1 id="kernel-baking"><title>Compiling a New Kernel</title>
 <para>
 
 Why would someone want to compile a new kernel? It is often not
 necessary since the default kernel shipped with Debian handles most
-configurations. However, it is useful to compile a new kernel in order
-to:
+configurations. Also, Debian often offers several alternative kernels.
+So you may want to check first if there is an alternative kernel image
+package that better corresponds to your hardware. However, it can be
+useful to compile a new kernel in order to:
 
 <itemizedlist>
 <listitem><para>
 
-handle special hardware needs, or hardware conflicts with the pre-supplied
-kernels
+handle special hardware needs, or hardware conflicts with the
+pre-supplied kernels
 
 </para></listitem>
 <listitem><para>
 
-handle hardware or options not included in the stock kernel, such as
-APM or SMP
+use options of the kernel which are not supported in the pre-supplied
+kernels (such as high memory support)
 
 </para></listitem>
 <listitem><para>
 
-optimize the kernel by removing useless drivers to speed up boot
-time
+optimize the kernel by removing useless drivers to speed up boot time
 
 </para></listitem>
 <listitem><para>
 
-use options of the kernel which are not supported by the default
-kernel (such as high memory support)
+create a monolithic instead of a modularized kernel
 
 </para></listitem>
 <listitem><para>
@@ -41,7 +41,7 @@ run an updated or development kernel
 </para></listitem>
 <listitem><para>
 
-impress your friends, try new things
+learn more about linux kernels
 
 </para></listitem>
 </itemizedlist>