svn commit: r1743259 - /maven/site/trunk/content/apt/guides/introduction/introduction-to-the-lifecycle.apt

[kh...@apache.org]

Author: khmarbaise
Date: Tue May 10 21:05:42 2016
New Revision: 1743259

URL: http://svn.apache.org/viewvc?rev=1743259&view=rev
Log:
[MNGSITE-282] Fixed typo.

Modified:
    maven/site/trunk/content/apt/guides/introduction/introduction-to-the-lifecycle.apt

Modified: maven/site/trunk/content/apt/guides/introduction/introduction-to-the-lifecycle.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/guides/introduction/introduction-to-the-lifecycle.apt?rev=1743259&r1=1743258&r2=1743259&view=diff
==============================================================================
--- maven/site/trunk/content/apt/guides/introduction/introduction-to-the-lifecycle.apt (original)
+++ maven/site/trunk/content/apt/guides/introduction/introduction-to-the-lifecycle.apt Tue May 10 21:05:42 2016
@@ -150,7 +150,7 @@ mvn clean dependency:copy-dependencies p
 
  Code coverage tools such as Jacoco and execution container plugins such as Tomcat, Cargo, and Docker bind goals to the
  <<<pre-integration-test>>> phase to prepare the integration test container environment. These plugins also bind goals
- to the <<<post-itegration-test>>> phase to collect coverage statistics or decommission the integration test container.
+ to the <<<post-integration-test>>> phase to collect coverage statistics or decommission the integration test container.
 
  Failsafe and code coverage plugins bind goals to <<<integration-test>>> and <<<verify>>> phases. The net result is
  test and coverage reports are available after the <<<verify>>> phase.  If <<<integration-test>>> were to be called from the