Fix all the whitespace errors igor reports.

Translators can ignore.

Sponsored by:	Absolight, The FreeBSD Foundation

en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml

@@ -2490,9 +2490,9 @@ USE_GITHUB=	yes</programlisting>
 	  similar to <xref
 	    linkend="porting-master-sites-n"/>.</para>
 
-	<para>When fetching multiple files from GitHub, sometimes the default
+	<para>When fetching multiple files from GitHub, sometimes the
-	  distribution file is not required.  To disable fetching the default
+	  default distribution file is not required.  To disable
-	  distribution, set:</para>
+	  fetching the default distribution, set:</para>
 
 	<programlisting>USE_GITHUB=	nodefault</programlisting>
 
@@ -2500,8 +2500,8 @@ USE_GITHUB=	yes</programlisting>
 	  <varname>GH_ACCOUNT</varname>,
 	  <varname>GH_PROJECT</varname>, and
 	  <varname>GH_TAGNAME</varname>.  Each different value is
-	  assigned a group.  The main value can either have no group, or
+	  assigned a group.  The main value can either have no group,
-	  the <literal>:DEFAULT</literal> group.  A value can be
+	  or the <literal>:DEFAULT</literal> group.  A value can be
 	  omitted if it is the same as the default as listed in
 	  <xref
 	    linkend="makefile-master_sites-github-description"/>.</para>
@@ -2533,9 +2533,9 @@ USE_GITHUB=	yes</programlisting>
 	<note>
 	  <para>As this is only syntastic sugar above
 	    <varname>DISTFILES</varname> and
-	    <varname>MASTER_SITES</varname>, the group names must adhere
+	    <varname>MASTER_SITES</varname>, the group names must
-	    to the restrictions on group names outlined in <xref
+	    adhere to the restrictions on group names outlined in
-	      linkend="porting-master-sites-n"/></para>
+	    <xref linkend="porting-master-sites-n"/></para>
 	</note>
 
 	<example xml:id="makefile-master_sites-github-multi">
@@ -3645,7 +3645,8 @@ PATCHFILES=	patch1:test</programlisting>
 
     <orderedlist>
       <listitem>
-	<para>The COMMENT string should be 70 characters or less.</para>
+	<para>The COMMENT string should be 70 characters or
+	  less.</para>
       </listitem>
 
       <listitem>
@@ -3664,7 +3665,8 @@ PATCHFILES=	patch1:test</programlisting>
       </listitem>
 
       <listitem>
-	<para>Capitalize names such as Apache, JavaScript, or Perl.</para>
+	<para>Capitalize names such as Apache, JavaScript, or
+	  Perl.</para>
       </listitem>
 
       <listitem>
@@ -5940,8 +5942,8 @@ USE_OPENSSL=	yes
 	<sect4 xml:id="options-configure_enable">
 	  <title><varname><replaceable>OPT</replaceable>_CONFIGURE_ENABLE</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    for each <replaceable>entry</replaceable> in
+	    selected, for each <replaceable>entry</replaceable> in
 	    <varname><replaceable>OPT</replaceable>_CONFIGURE_ENABLE</varname>
 	    then
 	    <literal>--enable-<replaceable>entry</replaceable></literal>
@@ -5951,8 +5953,8 @@ USE_OPENSSL=	yes
 	    <literal>--disable-<replaceable>entry</replaceable></literal>
 	    is appended to <varname>CONFIGURE_ARGS</varname>.  An
 	    optional argument can be specified with an
-	    <literal>=</literal> symbol.  This argument is only appended
+	    <literal>=</literal> symbol.  This argument is only
-	    to the
+	    appended to the
 	    <literal>--enable-<replaceable>entry</replaceable></literal>
 	    configure option.  For example:</para>
 
@@ -5982,8 +5984,8 @@ CONFIGURE_ARGS+=	--disable-test2
 	<sect4 xml:id="options-configure_with">
 	  <title><varname><replaceable>OPT</replaceable>_CONFIGURE_WITH</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    for each <replaceable>entry</replaceable> in
+	    selected, for each <replaceable>entry</replaceable> in
 	    <varname><replaceable>OPT</replaceable>_CONFIGURE_WITH</varname>
 	    then
 	    <literal>--with-<replaceable>entry</replaceable></literal>
@@ -5993,8 +5995,8 @@ CONFIGURE_ARGS+=	--disable-test2
 	    <literal>--without-<replaceable>entry</replaceable></literal>
 	    is appended to <varname>CONFIGURE_ARGS</varname>.  An
 	    optional argument can be specified with an
-	    <literal>=</literal> symbol.  This argument is only appended
+	    <literal>=</literal> symbol.  This argument is only
-	    to the
+	    appended to the
 	    <literal>--with-<replaceable>entry</replaceable></literal>
 	    configure option.  For example:</para>
 
@@ -6026,8 +6028,8 @@ CONFIGURE_ARGS+=	--without-test2
 	    and
 	    <varname><replaceable>OPT</replaceable>_CONFIGURE_OFF</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    the value of
+	    selected, the value of
 	    <varname><replaceable>OPT</replaceable>_CONFIGURE_ON</varname>,
 	    if defined, is appended to
 	    <varname>CONFIGURE_ARGS</varname>.
@@ -6068,8 +6070,8 @@ CONFIGURE_ARGS+=	--no-test
 	    and
 	    <varname><replaceable>OPT</replaceable>_CMAKE_OFF</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    the value of
+	    selected, the value of
 	    <varname><replaceable>OPT</replaceable>_CMAKE_ON</varname>,
 	    if defined, is appended to <varname>CMAKE_ARGS</varname>.
 	    <varname><replaceable>OPT</replaceable>_CMAKE_OFF</varname>
@@ -6093,8 +6095,8 @@ CMAKE_ARGS+=	-DOPTIMIZE:BOOL=true
 .endif</programlisting>
 
 	  <tip>
-	    <para>See <xref linkend="options-cmake_bool"/> for a shorter
+	    <para>See <xref linkend="options-cmake_bool"/> for a
-	      helper when the value is boolean.</para>
+	      shorter helper when the value is boolean.</para>
 	  </tip>
 	</sect4>
 
@@ -6103,8 +6105,8 @@ CMAKE_ARGS+=	-DOPTIMIZE:BOOL=true
 	    and
 	    <varname><replaceable>OPT</replaceable>_CMAKE_BOOL_OFF</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    for each <replaceable>entry</replaceable> in
+	    selected, for each <replaceable>entry</replaceable> in
 	    <varname><replaceable>OPT</replaceable>_CMAKE_BOOL</varname>
 	    then
 	    <literal>-D<replaceable>entry</replaceable>:BOOL=true</literal>
@@ -6116,8 +6118,8 @@ CMAKE_ARGS+=	-DOPTIMIZE:BOOL=true
 	    <varname><replaceable>OPT</replaceable>_CMAKE_BOOL_OFF</varname>
 	    is the oposite,
 	    <literal>-D<replaceable>entry</replaceable>:BOOL=false</literal>
-	    is appended to <varname>CMAKE_ARGS</varname> when the option
+	    is appended to <varname>CMAKE_ARGS</varname> when the
-	    is selected, and
+	    option is selected, and
 	    <literal>-D<replaceable>entry</replaceable>:BOOL=true</literal>
 	    when the option is <emphasis>not</emphasis> selected.  For
 	    example:</para>
@@ -6150,8 +6152,8 @@ CMAKE_ARGS+=	-DTEST:BOOL=false -DDEBUG:BOOL=false \
 	    and
 	    <varname><replaceable>OPT</replaceable>_MESON_OFF</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    the value of
+	    selected, the value of
 	    <varname><replaceable>OPT</replaceable>_MESON_ON</varname>,
 	    if defined, is appended to <varname>MESON_ARGS</varname>.
 	    <varname><replaceable>OPT</replaceable>_MESON_OFF</varname>
@@ -6180,8 +6182,8 @@ MESON_ARGS+=	-Dopt=2
 	    and
 	    <varname><replaceable>OPT</replaceable>_MESON_FALSE</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    for each <replaceable>entry</replaceable> in
+	    selected, for each <replaceable>entry</replaceable> in
 	    <varname><replaceable>OPT</replaceable>_MESON_TRUE</varname>
 	    then
 	    <literal>-D<replaceable>entry</replaceable>=true</literal>
@@ -6193,8 +6195,8 @@ MESON_ARGS+=	-Dopt=2
 	    <varname><replaceable>OPT</replaceable>_MESON_FALSE</varname>
 	    is the oposite,
 	    <literal>-D<replaceable>entry</replaceable>=false</literal>
-	    is appended to <varname>CMAKE_ARGS</varname> when the option
+	    is appended to <varname>CMAKE_ARGS</varname> when the
-	    is selected, and
+	    option is selected, and
 	    <literal>-D<replaceable>entry</replaceable>=true</literal>
 	    when the option is <emphasis>not</emphasis> selected.  For
 	    example:</para>
@@ -6223,8 +6225,8 @@ CMAKE_ARGS+=	-Dtest=false -Ddebug=false \
 	    and
 	    <varname><replaceable>OPT</replaceable>_MESON_NO</varname></title>
 
-	  <para>When option <replaceable>OPT</replaceable> is selected,
+	  <para>When option <replaceable>OPT</replaceable> is
-	    for each <replaceable>entry</replaceable> in
+	    selected, for each <replaceable>entry</replaceable> in
 	    <varname><replaceable>OPT</replaceable>_MESON_YES</varname>
 	    then
 	    <literal>-D<replaceable>entry</replaceable>=yes</literal>
@@ -6236,8 +6238,8 @@ CMAKE_ARGS+=	-Dtest=false -Ddebug=false \
 	    <varname><replaceable>OPT</replaceable>_MESON_NO</varname>
 	    is the oposite,
 	    <literal>-D<replaceable>entry</replaceable>=no</literal>
-	    is appended to <varname>CMAKE_ARGS</varname> when the option
+	    is appended to <varname>CMAKE_ARGS</varname> when the
-	    is selected, and
+	    option is selected, and
 	    <literal>-D<replaceable>entry</replaceable>=yes</literal>
 	    when the option is <emphasis>not</emphasis> selected.  For
 	    example:</para>
@@ -7047,7 +7049,8 @@ DISTVERSION=	1.0</programlisting>
 	adds files to their system.  All the additional commands run
 	in the port <filename>Makefile</filename>'s
 	<buildtarget>*-install</buildtarget> targets should be
-	echoed to the screen.  <emphasis>Do not</emphasis> silence these commands with
+	echoed to the screen.  <emphasis>Do not</emphasis> silence
+	these commands with
 	<literal>@</literal> or <literal>.SILENT</literal>.</para>
     </important>
 

en_US.ISO8859-1/books/porters-handbook/new-port/chapter.xml

@@ -22,8 +22,8 @@
     refer to <filename>/usr/ports/Mk/bsd.port.mk</filename>, which is
     included by all port <filename>Makefile</filename>s.  Even those
     not hacking <filename>Makefile</filename>s daily can gain much
-    knowledge from it.  Additionally, specific questions can be sent to the
+    knowledge from it.  Additionally, specific questions can be sent
-    &a.ports;.</para>
+    to the &a.ports;.</para>
 
   <note>
     <para>Only a fraction of the variables
@@ -40,8 +40,7 @@
       loaded.</para>
   </note>
 
-  <para>
+  <para>Looking for something easy to start with? Take a look at the
-    Looking for something easy to start with? Take a look at the
     <link xlink:href="http://wiki.freebsd.org/WantedPorts">list of
       requested ports</link> and see if you can work on one (or
     more).</para>

en_US.ISO8859-1/books/porters-handbook/pkg-files/chapter.xml

@@ -92,7 +92,8 @@
       <filename>Makefile</filename> if needed.  This is especially
       useful when sharing the same
       <filename>pkg-<replaceable>*</replaceable></filename> files
-      among several ports or when it is necessary to write to one of these files.
+      among several ports or when it is necessary to write to one of
+      these files.
       See <link linkend="porting-wrkdir">writing to places other than
 	<varname>WRKDIR</varname></link> for why it is a bad idea to
       write directly into

en_US.ISO8859-1/books/porters-handbook/quick-porting/chapter.xml

@@ -418,7 +418,8 @@ lib/X11/oneko/mouse.xpm</programlisting>
       <para>Giving a good description in the summary of the problem
 	report makes the work of port committers a lot easier.  We
 	prefer something like <quote>New port:
-	  <replaceable>category</replaceable>/<replaceable>portname</replaceable> <replaceable>short description of
+	  <replaceable>category</replaceable>/<replaceable>portname</replaceable>
+	  <replaceable>short description of
 	    the port</replaceable></quote> for new ports.  Using this
 	scheme makes it easier and faster to begin the work of
 	committing the new port.</para>

en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml

@@ -192,8 +192,8 @@
       FTP or HTTP server (for example, a home
       page).</para>
 
-    <para>If a convenient and reliable place to put
+    <para>If a convenient and reliable place to put the distfile
-      the distfile cannot be found, we can <quote>house</quote> it ourselves on
+      cannot be found, we can <quote>house</quote> it ourselves on
       <systemitem>ftp.FreeBSD.org</systemitem>; however, this is the
       least-preferred solution.  The distfile must be placed into
       <filename>~/public_distfiles/</filename> of someone's
@@ -209,8 +209,8 @@
       distfile on a home page and listing it as the first
       <varname>MASTER_SITES</varname>.  Try to talk the
       port author out of doing this; it really does help to establish
-      some kind of source code control.  Hosting a specific version will
+      some kind of source code control.  Hosting a specific version
-      prevent users from getting
+      will prevent users from getting
       <errorname>checksum mismatch</errorname> errors, and also reduce
       the workload of maintainers of our FTP site.  Also, if there is
       only one master site for the port, it is recommended to
@@ -458,9 +458,10 @@ DOS2UNIX_WRKSRC=	${WRKDIR}</programlisting>
     <para>Include any additional customization commands in the
       <filename>configure</filename> script and save it in the
       <filename>scripts</filename> subdirectory.  As mentioned above,
-      it is also possible do this with <filename>Makefile</filename> targets
+      it is also possible do this with <filename>Makefile</filename>
-      and/or scripts with the name <filename>pre-configure</filename>
+      targets and/or scripts with the name
-      or <filename>post-configure</filename>.</para>
+      <filename>pre-configure</filename> or
+      <filename>post-configure</filename>.</para>
   </sect1>
 
   <sect1 xml:id="slow-user-input">

en_US.ISO8859-1/books/porters-handbook/special/chapter.xml

@@ -1459,10 +1459,9 @@ USE_XORG=	x11 xpm</programlisting>
 
       <programlisting>DEVELOPER=yes</programlisting>
 
-      <para>
+      <para>in the environment or in
-	in the environment or in <filename>/etc/make.conf</filename>.
+	<filename>/etc/make.conf</filename>.  This causes the ports
-	This causes the ports framework to enable additional
+	framework to enable additional checks.</para>
-	checks.</para>
     </sect2>
 
     <sect2 xml:id="use-gnome">
@@ -2902,7 +2901,8 @@ USE_QT4=	moc_build qmake_build rcc_build uic_build</programlisting>
     <title>Using LXQt</title>
 
     <para>Applications depending on LXQt should set
-      <literal>USES+= lxqt</literal> and set <varname>USE_LXQT</varname>
+      <literal>USES+= lxqt</literal> and set
+      <varname>USE_LXQT</varname>
       to the list of required components from the table below</para>
 
     <table frame="none" xml:id="using-lxqt-components">
@@ -2973,7 +2973,8 @@ USE_LXQT=       buildtools libfmqt</programlisting>
 	The most current version is
 	<package role="port">java/openjdk8</package>, with
 	<package role="port">java/openjdk6</package> and
-	<package role="port">java/openjdk7</package> also available.</para>
+	<package role="port">java/openjdk7</package> also
+	available.</para>
 
       <table frame="none" xml:id="using-java-variables">
 	<title>Variables Which May be Set by Ports That Use

en_US.ISO8859-1/books/porters-handbook/testing/chapter.xml

@@ -182,7 +182,8 @@
 	<command>poudriere testport</command> or <command>poudriere
 	  bulk -t</command>.  It is highly recommended that every
 	ports contributor install and test their ports with it.  See
-	<xref linkend="testing-poudriere"/> for more information.</para>
+	<xref linkend="testing-poudriere"/> for more
+	information.</para>
     </tip>
   </sect1>
 

en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml

@@ -698,8 +698,8 @@
 
     <para>Possible arguments: (none)</para>
 
-    <para>Uses <package role="port">devel/gmake</package> as a build-time
+    <para>Uses <package role="port">devel/gmake</package> as a
-      dependency and sets up the environment to use
+      build-time dependency and sets up the environment to use
       <command>gmake</command> as the default <command>make</command>
       for the build.</para>
   </sect1>
@@ -1346,8 +1346,9 @@ GSSAPI_NONE_CONFIGURE_ON=	--without-gssapi</programlisting>
 	  <filename>KERN_DEBUGDIR</filename>/<filename>KMODDIR</filename>.
 	  By default, <varname>KERN_DEBUGDIR</varname> is copied from
 	  <varname>DEBUGDIR</varname> and set to
-	  <filename>/usr/lib/debug</filename>. The framework will take
+	  <filename>/usr/lib/debug</filename>.  The framework will
-	  care of creating and removing any required directories.</para>
+	  take care of creating and removing any required
+	  directories.</para>
       </listitem>
     </itemizedlist>
   </sect1>
@@ -1710,7 +1711,8 @@ GSSAPI_NONE_CONFIGURE_ON=	--without-gssapi</programlisting>
   <sect1 xml:id="uses-localbase">
     <title><literal>localbase</literal></title>
 
-    <para>Possible arguments: (none), <literal>ldflags</literal></para>
+    <para>Possible arguments: (none),
+      <literal>ldflags</literal></para>
 
     <para>Ensures that libraries from dependencies in
       <varname>LOCALBASE</varname> are used instead of the ones from
@@ -2856,7 +2858,8 @@ SHEBANG_FILES=	scripts/foobar.pl scripts/*.sh</programlisting>
 	<term><varname>OPENSSLLIB</varname></term>
 
 	<listitem>
-	  <para>Path to the <application>OpenSSL</application> libraries.</para>
+	  <para>Path to the <application>OpenSSL</application>
+	    libraries.</para>
 	</listitem>
       </varlistentry>
 
@@ -2864,7 +2867,8 @@ SHEBANG_FILES=	scripts/foobar.pl scripts/*.sh</programlisting>
 	<term><varname>OPENSSLINC</varname></term>
 
 	<listitem>
-	  <para>Path to the <application>OpenSSL</application> includes.</para>
+	  <para>Path to the <application>OpenSSL</application>
+	    includes.</para>
 	</listitem>
       </varlistentry>
 

en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml

@@ -90,8 +90,8 @@
 	    <entry>1200006</entry>
 	    <entry><revnumber>305256</revnumber></entry>
 	    <entry>September  1, 2016</entry>
-	    <entry>12.0-CURRENT after &man.crunchgen.1; META_MODE fix in
+	    <entry>12.0-CURRENT after &man.crunchgen.1; META_MODE fix
-	      <revnumber>305254</revnumber>.</entry>
+	      in <revnumber>305254</revnumber>.</entry>
 	  </row>
 
 	  <row>
@@ -198,8 +198,8 @@
 	    <entry>12.0-CURRENT after adding the
 	      <literal>ki_moretdname</literal> member to
 	      <literal>struct kinfo_proc</literal> and
-              <literal>struct kinfo_proc32</literal> to export the whole
+	      <literal>struct kinfo_proc32</literal> to export the
-              thread name to user-space utilities.</entry>
+	      whole thread name to user-space utilities.</entry>
 	  </row>
 
 	  <row>
@@ -223,7 +223,8 @@
 	    <entry>1200021</entry>
 	    <entry><revnumber>313858</revnumber></entry>
 	    <entry>February 16, 2017</entry>
-	    <entry>12.0-CURRENT after removing MCA and EISA support.</entry>
+	    <entry>12.0-CURRENT after removing MCA and EISA
+	      support.</entry>
 	  </row>
 
 	  <row>
@@ -247,7 +248,8 @@
 	    <entry><revnumber>314564</revnumber></entry>
 	    <entry>March 2, 2017</entry>
 	    <entry>12.0-CURRENT after upgrading our copies of clang,
-	      llvm, lld, lldb, compiler-rt and libc++ to 4.0.0.</entry>
+	      llvm, lld, lldb, compiler-rt and libc++ to
+	      4.0.0.</entry>
 	  </row>
 
 	  <row>
@@ -263,7 +265,8 @@
 	    <entry><revnumber>315430</revnumber></entry>
 	    <entry>March 16, 2017</entry>
 	    <entry>12.0-CURRENT after addition of the
-	      <filename>&lt;dev/mmc/mmc_ioctl.h&gt;</filename> header.</entry>
+	      <filename>&lt;dev/mmc/mmc_ioctl.h&gt;</filename>
+	      header.</entry>
 	  </row>
 
 	  <row>
@@ -271,15 +274,16 @@
 	    <entry><revnumber>315662</revnumber></entry>
 	    <entry>March 16, 2017</entry>
 	    <entry>12.0-CURRENT after hiding
-	      <literal>struct inpcb</literal> and <literal>struct tcpcb</literal>
+	      <literal>struct inpcb</literal> and <literal>struct
-	      from userland.</entry>
+		tcpcb</literal> from userland.</entry>
 	  </row>
 
 	  <row>
 	    <entry>1200027</entry>
 	    <entry><revnumber>315673</revnumber></entry>
 	    <entry>March 21, 2017</entry>
-	    <entry>12.0-CURRENT after making CAM SIM lock optional.</entry>
+	    <entry>12.0-CURRENT after making CAM SIM lock
+	      optional.</entry>
 	  </row>
 
 	  <row>
@@ -296,7 +300,8 @@
 	    <entry>1200029</entry>
 	    <entry><revnumber>317176</revnumber></entry>
 	    <entry>April 19, 2017</entry>
-	    <entry>12.0-CURRENT after the removal of struct vmmeter from
+	    <entry>12.0-CURRENT after the removal of struct vmmeter
+	      from
 	      struct pcpu from <revnumber>317061</revnumber>.</entry>
 	  </row>
 
@@ -307,15 +312,18 @@
 	    <entry>12.0-CURRENT after removing NATM support including
 	      en(4), fatm(4), hatm(4), and patm(4).</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200031</entry>
 	    <entry><revnumber>318736</revnumber></entry>
 	    <entry>May 23, 2017</entry>
 	    <entry>12.0-CURRENT after types <literal>ino_t</literal>,
 	      <literal>dev_t</literal>, <literal>nlink_t</literal>
-	      were extended to 64bit and <literal>struct dirent</literal>
+	      were extended to 64bit and <literal>struct
+		dirent</literal>
 	      changed layout (also known as ino64).</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200032</entry>
 	    <entry><revnumber>319664</revnumber></entry>
@@ -323,21 +331,26 @@
 	    <entry>12.0-CURRENT after removal of
 	      <literal>groff</literal>.</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200033</entry>
 	    <entry><revnumber>320043</revnumber></entry>
 	    <entry>June 17, 2017</entry>
-	    <entry>12.0-CURRENT after the type of the
+	    <entry>12.0-CURRENT after the type of the <literal>struct
-	      <literal>struct event</literal> member <literal>data</literal>
+		event</literal> member <literal>data</literal> was
-	      was increased to 64bit, and ext structure members added.</entry>
+	      increased to 64bit, and ext structure members
+	      added.</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200034</entry>
 	    <entry><revnumber>320085</revnumber></entry>
 	    <entry>June 19, 2017</entry>
-	    <entry>12.0-CURRENT after the NFS client and server were changed
+	    <entry>12.0-CURRENT after the NFS client and server were
-	      so that they actually use the 64bit ino_t.</entry>
+	      changed so that they actually use the 64bit
+	      ino_t.</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200035</entry>
 	    <entry><revnumber>320317</revnumber></entry>
@@ -345,13 +358,16 @@
 	    <entry>12.0-CURRENT after the <literal>MAP_GUARD</literal>
 	      <literal>mmap(2)</literal> flag was added.</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200036</entry>
 	    <entry><revnumber>320347</revnumber></entry>
 	    <entry>June 26, 2017</entry>
-	    <entry>12.0-CURRENT after changing <literal>time_t</literal>
+	    <entry>12.0-CURRENT after changing
+	      <literal>time_t</literal>
 	      to 64 bits on powerpc (32-bit version).</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200037</entry>
 	    <entry><revnumber>320545</revnumber></entry>
@@ -360,6 +376,7 @@
 	      <literal>bus_dmamap*</literal> functions
 	      (<revnumber>320528</revnumber>).</entry>
 	  </row>
+
 	  <row>
 	    <entry>1200038</entry>
 	    <entry><revnumber>320879</revnumber></entry>
@@ -1505,8 +1522,8 @@
 	    <entry>11.0-STABLE after adding the
 	      <literal>ki_moretdname</literal> member to
 	      <literal>struct kinfo_proc</literal> and
-              <literal>struct kinfo_proc32</literal> to export the whole
+	      <literal>struct kinfo_proc32</literal> to export the
-              thread name to user-space utilities.</entry>
+	      whole thread name to user-space utilities.</entry>
 	  </row>
 
 	  <row>
@@ -1589,6 +1606,7 @@
 	    <entry>11-STABLE after <literal>releng/11.1</literal>
 	      branched.</entry>
 	  </row>
+
 	  <row>
 	    <entry>1101501</entry>
 	    <entry><revnumber>320666</revnumber></entry>