[install-guide: 5/18] we might mention there are alternative bootloaders when we explain what bootloaders do, but we're on

[Pete Travis]

commit 7e978da0690f1e8adde104231df56338c22ab59b
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Sat Jul 28 19:39:07 2012 -0600

    we might mention there are alternative bootloaders when we explain what bootloaders do,
    but we're only going to support the one we ship.

 en-US/Boot_Init_Shutdown.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/Boot_Init_Shutdown.xml b/en-US/Boot_Init_Shutdown.xml
index a66323b..e30bced 100644
--- a/en-US/Boot_Init_Shutdown.xml
+++ b/en-US/Boot_Init_Shutdown.xml
@@ -217,7 +217,7 @@
 					Once the kernel loads and hands off the boot process to the <command>init</command> command, the same sequence of events occurs on every architecture. So the main difference between each architecture's boot process is in the application used to find and load the kernel.
 				</para>
 				<para>
-					For example, the IBM eServer pSeries architecture uses <application>yaboot</application>, and the IBM System&nbsp;z systems use the z/IPL boot loader.
+					For example, the IBM eServer pSeries architecture uses <application>yaboot</application>, and the IBM System&nbsp;z systems use the z/IPL boot loader. Configuration of alternative bootloaders is outside of the scope of this document.
 				</para>
 			</section>
 		</section>