s/u-boot/U-Boot/g across all files

1 files changed, 16 insertions, 16 deletions

diff --git a/po/fr/boot-installer.po b/po/fr/boot-installer.po
index 0abe27953..166009a51 100644
--- a/po/fr/boot-installer.po
+++ b/po/fr/boot-installer.po
@@ -81,10 +81,10 @@ msgstr ""
 #: boot-installer.xml:47
 #, no-c-format
 #| msgid ""
-#| "uImage/uInitrd are image formats designed for the u-boot firmware that is "
-#| "used on many ARM-based systems. Older u-boot versions can only boot files "
+#| "uImage/uInitrd are image formats designed for the U-Boot firmware that is "
+#| "used on many ARM-based systems. Older U-Boot versions can only boot files "
 #| "in uImage/uInitrd format, so these are often used on older armel systems. "
-#| "Newer u-boot versions can - besides booting uImages/uInitrds - also boot "
+#| "Newer U-Boot versions can - besides booting uImages/uInitrds - also boot "
 #| "standard Linux kernels and ramdisk images, but the command syntax to do "
 #| "that is slightly different from that for booting uImages."
 msgid ""
@@ -199,7 +199,7 @@ msgstr ""
 #. Tag: title
 #: boot-installer.xml:108
 #, no-c-format
-#| msgid "TFTP-booting in u-boot"
+#| msgid "TFTP-booting in U-Boot"
 msgid "TFTP-booting in U-Boot"
 msgstr "Amorcer à partir de TFTP avec U-Boot"
 
@@ -207,7 +207,7 @@ msgstr "Amorcer à partir de TFTP avec U-Boot"
 #: boot-installer.xml:109
 #, no-c-format
 #| msgid ""
-#| "Network booting on systems using the u-boot firmware consists of three "
+#| "Network booting on systems using the U-Boot firmware consists of three "
 #| "steps: a) configuring the network, b) loading the images (kernel/initial "
 #| "ramdisk/dtb) into memory and c) actually executing the previosly loaded "
 #| "code."
@@ -278,7 +278,7 @@ msgstr ""
 #: boot-installer.xml:132
 #, no-c-format
 #| msgid ""
-#| "On some systems, u-boot predefines a set of environment variables with "
+#| "On some systems, U-Boot predefines a set of environment variables with "
 #| "suitable load addresses: kernel_addr_r, ramdisk_addr_r and fdt_addr_r. "
 #| "You can check whether they are defined by running "
 #| "<informalexample><screen>\n"
@@ -402,7 +402,7 @@ msgstr "bootz ${kernel_addr_r} ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}"
 #, no-c-format
 #| msgid ""
 #| "Note: When booting standard linux images, it is important to load the "
-#| "initial ramdisk image after the kernel and the dtb as u-boot sets the "
+#| "initial ramdisk image after the kernel and the dtb as U-Boot sets the "
 #| "filesize variable to the size of the last file loaded and the bootz "
 #| "command requires the size of the ramdisk image to work correctly. In case "
 #| "of booting a platform-specific kernel, i.e. a kernel without device-tree, "
@@ -495,7 +495,7 @@ msgstr ""
 #. Tag: title
 #: boot-installer.xml:206
 #, no-c-format
-#| msgid "Booting from a USB stick in u-boot"
+#| msgid "Booting from a USB stick in U-Boot"
 msgid "Booting from a USB stick in U-Boot"
 msgstr "Amorcer sur une clé USB avec U-Boot"
 
@@ -503,7 +503,7 @@ msgstr "Amorcer sur une clé USB avec U-Boot"
 #: boot-installer.xml:207
 #, no-c-format
 #| msgid ""
-#| "Many modern u-boot versions have USB support and allow booting from USB "
+#| "Many modern U-Boot versions have USB support and allow booting from USB "
 #| "mass storage devices such as USB sticks. Unfortunately the exact steps "
 #| "required to do that can vary quite a bit from device to device."
 msgid ""
@@ -539,8 +539,8 @@ msgstr ""
 #| msgid ""
 #| "To build a bootable USB stick for installing &debian;, unpack the hd-"
 #| "media tarball (see <xref linkend=\"where-files\"/>) onto a USB stick "
-#| "formatted with a filesystem supported by the u-boot version on your "
-#| "device. For modern u-boot versions, any of FAT16 / FAT32 / ext2 / ext3 / "
+#| "formatted with a filesystem supported by the U-Boot version on your "
+#| "device. For modern U-Boot versions, any of FAT16 / FAT32 / ext2 / ext3 / "
 #| "ext4 usually works. Then copy the ISO image file of the first &debian; "
 #| "installation CD or DVD onto the stick."
 msgid ""
@@ -562,12 +562,12 @@ msgstr ""
 #: boot-installer.xml:233
 #, no-c-format
 #| msgid ""
-#| "The autoboot framework in modern u-boot versions works similar to the "
+#| "The autoboot framework in modern U-Boot versions works similar to the "
 #| "boot ordering options in a PC BIOS, i.e. it checks a list of possible "
 #| "boot devices for a valid boot image and starts the first one it finds. If "
 #| "there is no operating system installed, plugging in the USB stick and "
 #| "powering up the system should result in starting the installer. You can "
-#| "also initiate the USB-boot process any time from the u-boot prompt by "
+#| "also initiate the USB-boot process any time from the U-Boot prompt by "
 #| "entering the <quote>run bootcmd_usb0</quote> command."
 msgid ""
 "The autoboot framework in modern U-Boot versions works similar to the boot "
@@ -593,15 +593,15 @@ msgstr ""
 #| msgid ""
 #| "One problem that can come up when booting from a USB stick while using a "
 #| "serial console can be a console baudrate mismatch. If a console variable "
-#| "is defined in u-boot, the &d-i; boot script automatically passes it to "
+#| "is defined in U-Boot, the &d-i; boot script automatically passes it to "
 #| "the kernel to set the primary console device and, if applicable, the "
 #| "console baudrate. Unfortunately the handling of the console variable "
 #| "varies from platform to platform - on some platforms, the console "
 #| "variable includes the baudrate (as in <quote>console=ttyS0,115200</"
 #| "quote>), while on other platforms the console variable contains only the "
 #| "device (as in <quote>console=ttyS0</quote>). The latter case leads to a "
-#| "garbled console output when the default baudrate differs between u-boot "
-#| "and the kernel. Modern u-boot versions often use 115200 baud while the "
+#| "garbled console output when the default baudrate differs between U-Boot "
+#| "and the kernel. Modern U-Boot versions often use 115200 baud while the "
 #| "kernel still defaults to the traditional 9600 baud. If this happens, you "
 #| "should manually set the console variable to contain the correct baudrate "
 #| "for your system and then start the installer with the <quote>run "