Skip to content

Commit a2164c9

Browse files
committed
doc: Fix some groff/mandoc linting complaints
1 parent 2fad7d8 commit a2164c9

File tree

1 file changed

+12
-15
lines changed

1 file changed

+12
-15
lines changed

doc/C/parted.8

Lines changed: 12 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -54,16 +54,14 @@ Use optimum alignment as given by the disk topology information. This
5454
aligns to a multiple of the physical block size in a way that guarantees
5555
optimal performance.
5656
.RE
57-
5857
.SH COMMANDS
5958
.TP
6059
.B [device]
6160
The block device to be used. When none is given, \fBparted\fP will use the
6261
first block device it finds.
6362
.TP
6463
.B [command [options]]
65-
Specifies the command to be executed. If no command is given,
66-
.BR parted
64+
Specifies the command to be executed. If no command is given, \fBparted\fP
6765
will present a command prompt. Possible commands are:
6866
.RS
6967
.TP
@@ -119,8 +117,8 @@ or an LVM logical volume if necessary.
119117
.B set \fIpartition\fP \fIflag\fP \fIstate\fP
120118
Change the state of the \fIflag\fP on \fIpartition\fP to \fIstate\fP.
121119
Supported flags are: "boot", "root", "swap", "hidden", "raid", "lvm", "lba",
122-
"legacy_boot", "irst", "msftres", "esp", "chromeos_kernel", "bls_boot", "linux-home",
123-
"no_automount", "bios_grub", and "palo".
120+
"legacy_boot", "irst", "msftres", "esp", "chromeos_kernel", "bls_boot",
121+
"linux-home", "no_automount", "bios_grub", and "palo".
124122
\fIstate\fP should be either "on" or "off".
125123
.TP
126124
.B unit \fIunit\fP
@@ -140,10 +138,10 @@ On MS-DOS set the type aka. partition id of \fIpartition\fP to
140138
the type-uuid of \fIpartition\fP to \fIuuid\fP.
141139
.TP
142140
.B disk_set \fIflag\fP \fIstate\fP
143-
Change a \fIflag\fP on the disk to \fIstate\fP. A flag can be either "on" or "off".
144-
Some or all of these flags will be available, depending on what disk label you
145-
are using. Supported flags are: "pmbr_boot" on GPT to enable the boot flag on the
146-
GPT's protective MBR partition.
141+
Change a \fIflag\fP on the disk to \fIstate\fP. A flag can be either "on" or
142+
"off". Some or all of these flags will be available, depending on what disk
143+
abel you are using. Supported flags are: "pmbr_boot" on GPT to enable the
144+
boot flag on the GPT's protective MBR partition.
147145
.TP
148146
.B disk_toggle \fIflag\fP
149147
Toggle the state of the disk \fIflag\fP.
@@ -155,24 +153,23 @@ Display version information and a copyright message.
155153
\fBparted\fP will compute sensible ranges for the locations you specify when using
156154
units like "GB", "MB", etc. Use the sector unit "s" or IEC binary units like
157155
"GiB", "MiB", to specify exact locations.
158-
159156
When you specify start or end values using IEC binary units like "MiB",
160157
"GiB", "TiB", etc., \fBparted\fP treats those values as exact, and equivalent to
161158
the same number specified in bytes (i.e., with the "B" suffix), in that it
162159
provides no helpful range of sloppiness. Contrast that with a partition
163160
start request of "4GB", which may actually resolve to some sector up to 500MB
164-
before or after that point. Thus, when creating a partition in an exact location
165-
you should use units of bytes ("B"), sectors ("s"), or IEC binary units like
166-
"MiB", "GiB", but not "MB", "GB", etc.
161+
before or after that point. Thus, when creating a partition in an exact
162+
location you should use units of bytes ("B"), sectors ("s"), or IEC binary units
163+
like "MiB", "GiB", but not "MB", "GB", etc.
167164
.SH REPORTING BUGS
168165
Report bugs to <bug-parted@gnu.org>
169166
.SH SEE ALSO
170167
.BR fdisk (8),
171168
.BR mkfs (8),
172169
The \fIparted\fP program is fully documented in the
173-
.BR info(1)
170+
.BR info (1)
174171
format
175-
.IR "GNU partitioning software"
172+
.I "GNU partitioning software"
176173
manual.
177174
.SH AUTHOR
178175
This manual page was written by Timshel Knoll <timshel@debian.org>,

0 commit comments

Comments
 (0)