libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Corrected spelling errors found by lintian

Browse Source
This commit is contained in:
Thomas Schmitt
2017-09-17 11:06:12 +02:00
parent 187d79682c
commit 2e560d1257
6 changed files with 63 additions and 63 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
xorriso/xorrisofs.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISOFS 1 "Version 1.4.9, Sep 12, 2017"
.TH XORRISOFS 1 "Version 1.4.9, Sep 16, 2017"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1005,7 +1005,7 @@ from the boot image in the current catalog entry.
Non\-emulating BIOS bootimages usually need a load size of 4.
Nevertheless the default setting of mkisofs is to use the full size of the
boot image rounded up to a multiple of 4 512\-byte blocks. This default
may be explicitely enforced by the word "full" instead of a number.
may be explicitly enforced by the word "full" instead of a number.
.br
EFI boot images usually get set the number of blocks occupied
by the boot image file.
@ -1072,7 +1072,7 @@ boot facilities and partition tables of various hardware architectures.
A \fBMBR\fR (Master Boot Record) contains boot code and a partition table.
It is read by PC\-BIOS when booting from USB stick or hard disk,
and by PowerPC CHRP or PReP when booting.
An MBR partiton with type 0xee indicates the presence of GPT.
An MBR partition with type 0xee indicates the presence of GPT.
.br
A \fBGPT\fR (GUID Partition Table) marks partitions in a more modern way.
It is read by EFI when booting from USB stick or hard disk, and may be used