[maven-site] branch master updated: Small spelling correction

[mi...@apache.org]

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

michaelo 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 ed6db4f  Small spelling correction
ed6db4f is described below

commit ed6db4fdf566bfcabad597aa5f92314cd1179834
Author: Ryan Cloherty <cl...@gmail.com>
AuthorDate: Thu Jul 4 20:44:55 2019 -0400

    Small spelling correction
    
    Correcting a tiny typo I noticed on my travels through the Maven docs.
---
 content/apt/guides/mini/guide-default-execution-ids.apt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/apt/guides/mini/guide-default-execution-ids.apt b/content/apt/guides/mini/guide-default-execution-ids.apt
index 18ee882..1a3b6cb 100644
--- a/content/apt/guides/mini/guide-default-execution-ids.apt
+++ b/content/apt/guides/mini/guide-default-execution-ids.apt
@@ -124,7 +124,7 @@ Guide to Configuring Default Mojo Executions
   Without such an entry point, the user would be confronted with a stacktrace in the event he tried to run this application with a 1.4 or older
   JRE.
   
-  Therefore, the user needs to compile tha bulk of his application to target the 1.5 Java specification, then compile the rest (the entry point)
+  Therefore, the user needs to compile the bulk of his application to target the 1.5 Java specification, then compile the rest (the entry point)
   to target an older specification...say, 1.3. The first execution will specify the <<<source>>> and <<<target>>> values at <<<1.5>>>, 
   and add an <<<excludes>>> section to avoid compiling the entry point for the application. The second pass will then re-specify <<<source>>>
   and <<<target>>> to <<<1.3>>>, and basically invert the original <<<excludes>>> section to be an <<<includes>>> section, so as to compile <only>