From dc328a6b88ab8bb49818cf85c73df8ccbb52b2cb Mon Sep 17 00:00:00 2001 From: Jim Mock Date: Fri, 7 Apr 2000 21:26:56 +0000 Subject: [PATCH] Fix up the grammar in a few places. Submitted by: Josh Bello --- .../books/handbook/boot/chapter.sgml | 24 +++++++++---------- .../books/handbook/boot/chapter.sgml | 24 +++++++++---------- 2 files changed, 24 insertions(+), 24 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/boot/chapter.sgml b/en_US.ISO8859-1/books/handbook/boot/chapter.sgml index 321cef9bff..d21c5427ab 100644 --- a/en_US.ISO8859-1/books/handbook/boot/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/boot/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,14 +12,14 @@ FreeBSD uses a three-stage bootstrap by default, which basically entails three programs which call each - other in order (the two boot + other in order (two boot blocks, and the loader). Each of these three build on the previous program's understanding and provide increasing amounts of sophistication. - The kernel is then started, at which time devices are - probed for and initialized for use. Once the kernel boot + The kernel is then started, which will then probe for devices + and initialize them for use. Once the kernel boot process is finished, the kernel passes control to the user process &man.init.8;, which then makes sure the disks are in a usable state. &man.init.8; then starts the user-level resource configuration which @@ -42,14 +42,14 @@ programs to determine what configuration details were determined. - In standard personal computers, this involves the BIOS, - which oversees the bootstrap, and CMOS, which stores - configuration; and these understand disks, and they also + In standard personal computers, this involves the BIOS + (which oversees the bootstrap), and CMOS (which stores + configuration). BIOS and CMOS understand disks, and also understand where on the disk to find a program that will know how to load up an operating system. This chapter will not deal with this first part of the - bootstrap process, and focuses on what happens after control + bootstrap process. Instead it will focus on what happens after control is passed to the program on the disk. The boot blocks are responsible for finding (usually) the @@ -67,7 +67,7 @@ list of possible slices to boot from. boot0 is very simple, since the program in the - MBR can only be 512 bytes large. + MBR can only be 512 bytes in size. It displays something like this: @@ -94,7 +94,7 @@ Default: F2 find the program to run to continue the boot process. boot1 is very simple, since it too can only be 512 bytes - large, and knows just enough about the FreeBSD + in size, and knows just enough about the FreeBSD disklabel, which stores information about the slice, to find and execute boot2. @@ -116,7 +116,7 @@ Default: F2 boot2 screenshot - >> FreeBSD/i386 BOOT + >> FreeBSD/i386 BOOT Default: 0:wd(0,a)/kernel boot: @@ -367,7 +367,7 @@ boot: Once the kernel is loaded by either loader (as usual) or boot2 (bypassing the loader), it - examines its boot flags, if any, and adjusts its behaviour as + examines its boot flags, if any, and adjusts its behavior as necessary. diff --git a/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml b/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml index 321cef9bff..d21c5427ab 100644 --- a/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml +++ b/en_US.ISO_8859-1/books/handbook/boot/chapter.sgml @@ -1,7 +1,7 @@ @@ -12,14 +12,14 @@ FreeBSD uses a three-stage bootstrap by default, which basically entails three programs which call each - other in order (the two boot + other in order (two boot blocks, and the loader). Each of these three build on the previous program's understanding and provide increasing amounts of sophistication. - The kernel is then started, at which time devices are - probed for and initialized for use. Once the kernel boot + The kernel is then started, which will then probe for devices + and initialize them for use. Once the kernel boot process is finished, the kernel passes control to the user process &man.init.8;, which then makes sure the disks are in a usable state. &man.init.8; then starts the user-level resource configuration which @@ -42,14 +42,14 @@ programs to determine what configuration details were determined. - In standard personal computers, this involves the BIOS, - which oversees the bootstrap, and CMOS, which stores - configuration; and these understand disks, and they also + In standard personal computers, this involves the BIOS + (which oversees the bootstrap), and CMOS (which stores + configuration). BIOS and CMOS understand disks, and also understand where on the disk to find a program that will know how to load up an operating system. This chapter will not deal with this first part of the - bootstrap process, and focuses on what happens after control + bootstrap process. Instead it will focus on what happens after control is passed to the program on the disk. The boot blocks are responsible for finding (usually) the @@ -67,7 +67,7 @@ list of possible slices to boot from. boot0 is very simple, since the program in the - MBR can only be 512 bytes large. + MBR can only be 512 bytes in size. It displays something like this: @@ -94,7 +94,7 @@ Default: F2 find the program to run to continue the boot process. boot1 is very simple, since it too can only be 512 bytes - large, and knows just enough about the FreeBSD + in size, and knows just enough about the FreeBSD disklabel, which stores information about the slice, to find and execute boot2. @@ -116,7 +116,7 @@ Default: F2 boot2 screenshot - >> FreeBSD/i386 BOOT + >> FreeBSD/i386 BOOT Default: 0:wd(0,a)/kernel boot: @@ -367,7 +367,7 @@ boot: Once the kernel is loaded by either loader (as usual) or boot2 (bypassing the loader), it - examines its boot flags, if any, and adjusts its behaviour as + examines its boot flags, if any, and adjusts its behavior as necessary.