[gimp-help/gimp-help-2-10] Fix DocBook XML validation error.

[Jacob Boerema <jboerema src gnome org>]

commit b89112efc511c04d7543bc89ba5c3acb0bd73156
Author: Jacob Boerema <jgboerema gmail com>
Date:   Sun Jul 17 12:22:59 2022 -0400

    Fix DocBook XML validation error.

 src/concepts/plugins.xml | 58 +++++++++++++++++++++++++++---------------------
 1 file changed, 33 insertions(+), 25 deletions(-)
---
diff --git a/src/concepts/plugins.xml b/src/concepts/plugins.xml
index dfb852689..3fdb1d876 100644
--- a/src/concepts/plugins.xml
+++ b/src/concepts/plugins.xml
@@ -214,31 +214,39 @@
       </para>
     </sect3>
 
-    <para>
-      Once you have installed the plugin, how do you activate it? The menu
-      path is determined by the plugin itself, so to answer this you need to
-      either look at the documentation for the plugin (if there is any),
-      explore the menus, or use <acronym>GIMP</acronym>'s command search
-      function by pressing <keycap>/</keycap> and then entering the name of the
-      plugin. If you know how to read source code you could also check that to
-      see in what menu it registers itself.
-    </para>
-    <para>
-      For more complex plugins, organized as a directory with multiple
-      files, there usually is a file inside called either
-      <filename>INSTALL</filename> or <filename>README</filename>, with
-      instructions. If not, the best advice is to toss the plugin in the
-      trash and spend your time on something else: any code written with so
-      little concern for the user is likely to be frustrating in myriad
-      ways.
-    </para>
-    <para>
-      If you install a plugin in your personal plugin directory that has the
-      same name as one in the system plugin directory, only one can be
-      loaded, and it will be the one in your home directory. You will
-      receive messages telling you this each time you start
-      <acronym>GIMP</acronym>. This is probably a situation best avoided.
-    </para>
+    <!-- DocBook doesn't allow us to just add para's here after sect3, even
+         though the generated html looks perfectly fine.
+         Even a simplesect doesn't work here in 4.3, so let's just add
+         another sect3.
+    -->
+    <sect3>
+      <title>Running the installed plugin</title>
+      <para>
+        Once you have installed the plugin, how do you activate it? The menu
+        path is determined by the plugin itself, so to answer this you need to
+        either look at the documentation for the plugin (if there is any),
+        explore the menus, or use <acronym>GIMP</acronym>'s command search
+        function by pressing <keycap>/</keycap> and then entering the name of the
+        plugin. If you know how to read source code you could also check that to
+        see in what menu it registers itself.
+      </para>
+      <para>
+        For more complex plugins, organized as a directory with multiple
+        files, there usually is a file inside called either
+        <filename>INSTALL</filename> or <filename>README</filename>, with
+        instructions. If not, the best advice is to toss the plugin in the
+        trash and spend your time on something else: any code written with so
+        little concern for the user is likely to be frustrating in myriad
+        ways.
+      </para>
+      <para>
+        If you install a plugin in your personal plugin directory that has the
+        same name as one in the system plugin directory, only one can be
+        loaded, and it will be the one in your home directory. You will
+        receive messages telling you this each time you start
+        <acronym>GIMP</acronym>. This is probably a situation best avoided.
+      </para>
+    </sect3>
   </sect2>
 
   <sect2 id="plugins-write">