[multiboot-guide] master: minor corrections to some stuff (2d873ce)

immanetize at fedoraproject.org immanetize at fedoraproject.org
Mon Jan 26 18:19:04 UTC 2015


Repository : http://git.fedorahosted.org/cgit/docs/multiboot-guide.git

On branch  : master

>---------------------------------------------------------------

commit 2d873ce60c5894ab8d14ea5b92adc8866729f91f
Author: Pete Travis <immanetize at fedoraproject.org>
Date:   Mon Jan 26 11:18:59 2015 -0700

    minor corrections to some stuff


>---------------------------------------------------------------

 en-US/FAQ.xml        |    4 ++--
 en-US/Free_Space.xml |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/en-US/FAQ.xml b/en-US/FAQ.xml
index 67bb89c..40c0e78 100644
--- a/en-US/FAQ.xml
+++ b/en-US/FAQ.xml
@@ -109,7 +109,7 @@
           To fully answer that, you have to understand what these tools do.  In times past, Linux distributions produced ISO images in a format that made them work when burned to an optical disc.  The same format doesn't work when the image is directly written to a USB drives, so tools were created to modify the images for use on USB sticks.  Typically, this involved transferring the contents of the image to the USB drive, then installing a <application>syslinux</application> bootloader to the drive and configuring it to boot the drive's new contents.
         </para>
         <para>
-          Today, Fedora images are created in a <literal>hybrid</literal> format that's directly usable as an optical disk or USB disk, for both legacy and UEFI systems.  A <application>syslinux</application> alone isn't compatible with UEFI booting.  When the universal installation tools replace the hybrid booting configuration with <application>syslinux</application>, the image can't be used on UEFI systems.  You end up with a USB drive that's only bootable in legacy mode, which conflicts with dual booting of other operating systems installed in UEFI mode, such as any laptop preinstalled with Windows 8.
+          Today, Fedora images are created in a <literal>hybrid</literal> format that's directly usable as an optical disk or USB disk, for both legacy and UEFI systems.  A <application>syslinux</application> bootloader alone isn't compatible with UEFI booting.  When the universal installation tools replace the hybrid booting configuration with <application>syslinux</application>, the image can't be used on UEFI systems.  You end up with a USB drive that's only bootable in legacy mode, which conflicts with dual booting of other operating systems installed in UEFI mode, such as any laptop preinstalled with Windows 8.
         </para>
         <para>
           For best results, follow the instructions in the <ulink url="https://docs.fedoraproject.org/install-guide">Fedora Installation Guide</ulink> for a <literal>direct write</literal> method of creating USB media.
@@ -124,7 +124,7 @@
       </question>
       <answer>
         <para>
-          Fedora needs it's own space, it cannot use free space on<filename class="partition" >C:</filename>.  You can use the installer to resize existing partitions and make room for Fedora.
+          Fedora needs it's own space, it cannot use free space on <filename class="partition" >C:</filename>.  You can use the installer to resize existing partitions and make room for Fedora.
         </para>
       </answer>
     </qandaentry>
diff --git a/en-US/Free_Space.xml b/en-US/Free_Space.xml
index 54f56da..1da78c0 100644
--- a/en-US/Free_Space.xml
+++ b/en-US/Free_Space.xml
@@ -169,7 +169,7 @@ Number  Start       End         Size        File system  Name
             </screen>
           </para>
           <para>
-            The partition starts on sector <literal>232384512</literal>, and the sector size is <literal>512&nbsp;bytles</literal>
+            The partition starts on sector <literal>232384512</literal>, and the sector size is <literal>512&nbsp;bytes</literal>
           </para>
         </step>
         <step>



More information about the docs-commits mailing list