[maven-site] branch master updated: Fix indentation

[rf...@apache.org]

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

rfscholte 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 b2d4ccd  Fix indentation
b2d4ccd is described below

commit b2d4ccdad775d3121a85988e59531d17f7a85375
Author: rfscholte <rf...@apache.org>
AuthorDate: Sat Jan 18 12:12:30 2020 +0100

    Fix indentation
---
 .../introduction/introduction-to-the-lifecycle.apt     | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-the-lifecycle.apt b/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
index 4570a9d..78823cf 100644
--- a/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
+++ b/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
@@ -89,22 +89,22 @@ Introduction to the Build Lifecycle
 
 ** {Usual Command Line Calls}
 
-You should select the phase that matches your outcome. If you want your jar, run <<<package>>>. If you want to run the 
-unit tests, run <<<test>>>.
+  You should select the phase that matches your outcome. If you want your jar, run <<<package>>>. If you want to run the 
+  unit tests, run <<<test>>>.
 
-If you are uncertain what you want, the preffered phase to call is
+  If you are uncertain what you want, the preffered phase to call is
 
 ------
 mvn verify
 ------
 
-This command executes each default lifecycle phase in order (<<<validate>>>, <<<compile>>>, <<<package>>>, etc.), 
-before executing <<<verify>>>.  You only need to call the last build phase to be executed, in this case, <<<verify>>>.
-In most cases the effect is the same as <<<package>>>. However, in case there are integration-tests, these will be
-executed as well. And during the <<<verify>>> phase some additional checks can be done, e.g. if your code written
-according to the predefined checkstyle rules.
+  This command executes each default lifecycle phase in order (<<<validate>>>, <<<compile>>>, <<<package>>>, etc.), 
+  before executing <<<verify>>>.  You only need to call the last build phase to be executed, in this case, <<<verify>>>.
+  In most cases the effect is the same as <<<package>>>. However, in case there are integration-tests, these will be
+  executed as well. And during the <<<verify>>> phase some additional checks can be done, e.g. if your code written
+  according to the predefined checkstyle rules.
 
-In a build environment, use the following call to cleanly build and deploy artifacts into the shared repository.
+  In a build environment, use the following call to cleanly build and deploy artifacts into the shared repository.
 
 ------
 mvn clean deploy