[maven-site] 02/02: split the paragraph into smaller ones

[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

commit 859f5564d0bccb413afe80d2ce06db51f1cad745
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Tue Jan 15 16:31:31 2019 +0100

    split the paragraph into smaller ones
---
 .../introduction-to-dependency-mechanism.apt           | 18 ++++++++++++------
 1 file changed, 12 insertions(+), 6 deletions(-)

diff --git a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
index 0b451c1..d47099d 100644
--- a/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
+++ b/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt
@@ -104,15 +104,21 @@ Introduction to the Dependency Mechanism
 
  []
 
- Although transitive dependencies can help you to include desired dependencies, it is a good practice that you directly
+ Although transitive dependencies can help you to include implicitely desired dependencies, it is a good practice that you explicitely
  specify the dependencies you are directly using in your own source code. This best practice proves its value especially
- when the dependencies of your project constantly changes their dependencies. Assume that your project A specifies a
+ when the dependencies of your project changes their dependencies.
+ 
+ For example, assume that your project A specifies a
  dependency on another project B, and project B specifies a dependency on project C. If you are directly using components
  in project C, and you don't specify project C in your project A, it may cause build failure when project B suddenly
- updates/removes its dependency on project C. Another reason to directly specify dependencies is that it provides better
- documentation for your project: one can learn more information by just reading the POM file in your project. Maven also
- provides a plugin {{{https://maven.apache.org/plugins/maven-dependency-plugin/analyze-mojo.html}dependency:analyze mojo}}
- for analyzing the dependencies and making this best practice more achievable.
+ updates/removes its dependency on project C.
+ 
+ Another reason to directly specify dependencies is that it provides better
+ documentation for your project: one can learn more information by just reading the POM file in your project.
+ 
+ Maven also
+ provides {{{/plugins/maven-dependency-plugin/analyze-mojo.html}dependency:analyze}} plugin goal
+ for analyzing the dependencies: it helps making this best practice more achievable.
 
 * {Dependency Scope}