Correct murky grammar.
This commit is contained in:
parent
285ed71840
commit
b1036d3d1c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=33354
1 changed files with 3 additions and 3 deletions
|
@ -119,7 +119,7 @@
|
|||
done from within the old system, up to the point where you can
|
||||
chroot to the new system. In other words, we go through three
|
||||
stages, where each stage consists of either running a shell
|
||||
script or invoke <command>make</command>:</para>
|
||||
script or invoking <command>make</command>:</para>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
|
@ -524,9 +524,9 @@ news inn-stable CONFIGURE_ARGS="--enable-uucp-rnews --enable-setgid-inews"
|
|||
appropriate answers to the installation command (e.g. <command>yes |
|
||||
make install</command>. For other ports you need to investigate
|
||||
where exactly the interactive command is located and deal with it
|
||||
appropriately. The examples above for
|
||||
appropriately. See the examples above for
|
||||
<filename role="package">print/acroread8</filename> and
|
||||
<filename role="package">java/jdk16</filename> are examples.</para>
|
||||
<filename role="package">java/jdk16</filename>.
|
||||
|
||||
<para>You should also be aware of upgrade issues for config files.
|
||||
In general you do not know when and if the format or contents of a
|
||||
|
|
Loading…
Reference in a new issue