Fix section order issues (#1262)

This commit is contained in:
Sergey Panteleev 2021-12-28 08:00:18 +03:00 committed by GitHub
parent 291d60430d
commit 181e9c5572
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 47 additions and 62 deletions

View file

@ -91,6 +91,14 @@ Remove me once you perform substitutions
</row>
</thead>
<tbody>
<row>
<entry>8.0.0</entry>
<entry>
<classname>DOMNodeList</classname> implements
<interfacename>IteratorAggregate</interfacename> now.
Previously, <interfacename>Traversable</interfacename> was implemented instead.
</entry>
</row>
<row>
<entry>7.2.0</entry>
<entry>
@ -102,7 +110,8 @@ Remove me once you perform substitutions
</tgroup>
</informaltable>
</para>
</section><!-- }}} -->
</section><!-- }}} -->
<!-- {{{ See also -->
<section role="seealso">
&reftitle.seealso;
@ -112,30 +121,7 @@ Remove me once you perform substitutions
</simplelist>
</para>
</section>
<section role="changelog">
&reftitle.changelog;
<informaltable>
<tgroup cols="2">
<thead>
<row>
<entry>&Version;</entry>
<entry>&Description;</entry>
</row>
</thead>
<tbody>
<row>
<entry>8.0.0</entry>
<entry>
<classname>DOMNodeList</classname> implements
<interfacename>IteratorAggregate</interfacename> now.
Previously, <interfacename>Traversable</interfacename> was implemented instead.
</entry>
</row>
</tbody>
</tgroup>
</informaltable>
</section>
<!-- }}} -->
</partintro>

View file

@ -44,6 +44,14 @@
</para>
</refsect1>
<refsect1 role="errors">
&reftitle.errors;
<simpara>
Emits an <constant>E_WARNING</constant> level error if the directory
already exists or the relevant permissions prevent creating the directory.
</simpara>
</refsect1>
<refsect1 role="changelog">
&reftitle.changelog;
<informaltable>
@ -61,14 +69,6 @@
</informaltable>
</refsect1>
<refsect1 role="errors">
&reftitle.errors;
<simpara>
Emits an <constant>E_WARNING</constant> level error if the directory
already exists or the relevant permissions prevent creating the directory.
</simpara>
</refsect1>
<refsect1 role="examples">
&reftitle.examples;
<para>

View file

@ -92,6 +92,17 @@ Result set has 239 rows.
</example>
</refsect1>
<refsect1 role="notes">
&reftitle.notes;
<note>
<para>
In contrast to the <function>mysqli_stmt_num_rows</function> function,
this function doesn't have object-oriented method variant.
In the object-oriented style, use the getter property.
</para>
</note>
</refsect1>
<refsect1 role="seealso">
&reftitle.seealso;
<para>
@ -105,17 +116,6 @@ Result set has 239 rows.
</para>
</refsect1>
<refsect1 role="notes">
&reftitle.notes;
<note>
<para>
In contrast to the <function>mysqli_stmt_num_rows</function> function,
this function doesn't have object-oriented method variant.
In the object-oriented style, use the getter property.
</para>
</note>
</refsect1>
</refentry>
<!-- Keep this comment at the end of the file
Local variables:

View file

@ -124,6 +124,23 @@
</para>
</refsect1><!-- }}} -->
<refsect1 role="errors"><!-- {{{ -->
&reftitle.errors;
<para>
On failure the <parameter>error_code</parameter> and
<parameter>error_message</parameter> arguments will be populated with the actual
system level error that occurred in the system-level
<literal>connect()</literal> call. If the value returned in
<parameter>error_code</parameter> is <literal>0</literal> and the
function returned &false;, it is an indication that the error
occurred before the <literal>connect()</literal> call. This is
most likely due to a problem initializing the socket. Note that
the <parameter>error_code</parameter> and
<parameter>error_message</parameter> arguments will always be passed by
reference.
</para>
</refsect1><!-- }}} -->
<refsect1 role="changelog">
&reftitle.changelog;
<informaltable>
@ -146,24 +163,6 @@
</informaltable>
</refsect1>
<refsect1 role="errors"><!-- {{{ -->
&reftitle.errors;
<para>
On failure the <parameter>error_code</parameter> and
<parameter>error_message</parameter> arguments will be populated with the actual
system level error that occurred in the system-level
<literal>connect()</literal> call. If the value returned in
<parameter>error_code</parameter> is <literal>0</literal> and the
function returned &false;, it is an indication that the error
occurred before the <literal>connect()</literal> call. This is
most likely due to a problem initializing the socket. Note that
the <parameter>error_code</parameter> and
<parameter>error_message</parameter> arguments will always be passed by
reference.
</para>
</refsect1><!-- }}} -->
<refsect1 role="examples"><!-- {{{ -->
&reftitle.examples;
<para>