[maven-site] branch master updated: fixed typo and code sections

[hb...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git


The following commit(s) were added to refs/heads/master by this push:
     new ea67b9b7 fixed typo and code sections
ea67b9b7 is described below

commit ea67b9b77950bcfaf0e73c00bc89be8fd8254258
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Sat May 28 23:11:55 2022 +0200

    fixed typo and code sections
---
 .../apt/guides/mini/guide-configuring-plugins.apt  | 26 +++++++++++-----------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/content/apt/guides/mini/guide-configuring-plugins.apt b/content/apt/guides/mini/guide-configuring-plugins.apt
index 26888cf7..a3588bcd 100644
--- a/content/apt/guides/mini/guide-configuring-plugins.apt
+++ b/content/apt/guides/mini/guide-configuring-plugins.apt
@@ -167,9 +167,9 @@ public class MyQueryMojo
   Mojo above, the parameter <<<url>>> is associated with the expression <<<$\{query.url\}>>>, meaning its value can
   be specified by the system property <<<query.url>>> as shown below:
 
-+----+
+------
 mvn myquery:query -Dquery.url=http://maven.apache.org
-+----+
+------
 
   The name of the system property does not necessarily match the name of the mojo parameter. While this is
   a rather common practice, you will often notice plugins that employ some prefix for the system properties to avoid
@@ -183,9 +183,9 @@ mvn myquery:query -Dquery.url=http://maven.apache.org
   of the plugin and its parameters and types. For instance, to see help
   for the javadoc goal, type:
 
-+----+
+------
 mvn javadoc:help -Ddetail -Dgoal=javadoc
-+----+
+------
 
   And you will see all parameters for the javadoc:javadoc goal, similar to this
   {{{/plugins/maven-javadoc-plugin/javadoc-mojo.html}page}}.
@@ -560,9 +560,9 @@ public class MyBoundQueryMojo
   run the above plugin and it's specific execution1's configuration from the
   command-line, you can execute:
 
-+----+
+------
 mvn myqyeryplugin:queryMojo@execution1
-+----+
+------
 
 ** {Using the <<<\<dependencies\>>>> Tag}
 
@@ -630,15 +630,15 @@ mvn myqyeryplugin:queryMojo@execution1
 
 ** {Using the <<<\<reporting\>>>> Tag VS <<<\<build\>>>> Tag}
 
-  Configuring a reporting plugin in the \<reporting\> or \<build\> elements in the pom does not exactly have the same results.
+  Configuring a reporting plugin in the <<<\<reporting\>>>> or <<<\<build\>>>> elements in the pom does not exactly have the same results.
 
-  [<<<mvn site>>>] Sine maven-site-plugin 3.4, it uses the parameters defined in the \<configuration\> element of each reporting Plugin
-  specified in the \<reporting\> element, in addition to the parameters defined in the
-  \<configuration\> element of each plugin specified in \<build\> (parameters from \<build\> section were previously ignored).
+  [<<<mvn site>>>] Since maven-site-plugin 3.4, it uses the parameters defined in the <<<\<configuration\>>>> element of each reporting Plugin
+  specified in the <<<\<reporting\>>>> element, in addition to the parameters defined in the
+  <<<\<configuration\>>>> element of each plugin specified in <<<\<build\>>>> (parameters from <<<\<build\>>>> section were previously ignored).
 
-  [<<<mvn aplugin:areportgoal>>>] It <<ignores>> the parameters defined in the \<configuration\> element of each
-  reporting Plugin specified in the \<reporting\> element; only parameters
-  defined in the \<configuration\> element of each plugin specified in \<build\> are used.
+  [<<<mvn aplugin:areportgoal>>>] It <<ignores>> the parameters defined in the <<<\<configuration\>>>> element of each
+  reporting Plugin specified in the <<<\<reporting\>>>> element; only parameters
+  defined in the <<<\<configuration\>>>> element of each plugin specified in <<<\<build\>>>> are used.
 
   []