en_US/Installation_notes.xml | 25 +++++++++++++------------
1 file changed, 13 insertions(+), 12 deletions(-)
New commits:
commit 15f92ff4863f39d3bd32968fc3dbf32b5b9f6bd0
Author: Paul W. Frields <paul(a)salma.internal.frields.org>
Date: Sat Nov 1 16:11:35 2008 -0400
Sync with wiki content.
diff --git a/en_US/Installation_notes.xml b/en_US/Installation_notes.xml
index b028611..baabc15 100644
--- a/en_US/Installation_notes.xml
+++ b/en_US/Installation_notes.xml
@@ -100,15 +100,15 @@
-- Anaconda is now using
<application>NetworkManager</application> for configuring
network interfaces during installation. The previous backend
- tool was <systemitem class="library">libdhcp</systemitem>
- (which was a replacement for <systemitem
- class="library">libpump</systemitem>).
+ tool was <systemitem class="library">libdhcp</systemitem>,
+ which was a replacement for <systemitem
+ class="library">libpump</systemitem>.
<application>Anaconda</application> uses
<application>NetworkManager</application> by communicating
with it via D-Bus during installation. The move to
<application>NetworkManager</application> in
- <application>Anaconda</application> is still ongoing and some
- things are not yet 100% functional, but the bulk of existing
+ <application>Anaconda</application> is still ongoing,
+ but the bulk of existing
functionality has been retained.
<application>NetworkManager</application> is enabled by
default on newly installed systems, so moving to
@@ -133,9 +133,9 @@
source></replaceable></literal> or add
<option>askmethod</option> to the installer boot parameters.
The <option>askmethod</option> option causes the selection
- screen to appear as it did in previous releases. Boot
- parameters can be added by pressing the <keycap>Tab</keycap>
- key in the initial boot screen and appending your new
+ screen to appear as it did in previous releases. To add boot
+ parameters, press the <keycap>Tab</keycap>
+ key in the initial boot screen and append any new
parameters to the existing list. For more information, refer
to the <computeroutput>repo=</computeroutput> and
<computeroutput>stage2=</computeroutput> descriptions at
commit dc25d996b635964aaef7c83e964333f05b35f69f
Author: Paul W. Frields <paul(a)salma.internal.frields.org>
Date: Sat Nov 1 16:06:13 2008 -0400
Sync with wiki content.
diff --git a/en_US/Installation_notes.xml b/en_US/Installation_notes.xml
index da24d3f..b028611 100644
--- a/en_US/Installation_notes.xml
+++ b/en_US/Installation_notes.xml
@@ -39,19 +39,20 @@
selected during boot from an installation-only media.</para>
<para>
For Fedora Live media, press any key during the initial boot
- countdown, bringing up a boot option menu. Select
+ countdown, to display a boot option menu. Select
<menuchoice><guimenuitem>Verify and
boot</guimenuitem></menuchoice> to perform the media test. The
pure installation medium can be used to verify a Fedora Live
medium. <application>Anaconda</application> asks during the
mediacheck if you want to check any other disc than the one
<application>Anaconda</application> is running from. To test
- another media, select
+ additional media, select
<menuchoice><guimenuitem>eject</guimenuitem></menuchoice>
to
eject the inserted medium, then replace it with the medium you
want to test instead.</para>
- <para>Perform this test everytime after you create or receive a new
- installation or live medium.</para>
+ <para>
+ Perform this test for any new installation or live medium.
+ </para>
<para>The Fedora Project strongly recommends that you perform this
test before reporting any installation-related bugs. Many of the
bugs reported are actually due to improperly-burned CD or
Show replies by date