address comments

Author: yanancai

articles/hdinsight/spark/apache-spark-manage-jar-dependency.md renamed to articles/hdinsight/spark/manage-jar-dependency.md

@@ -1,6 +1,6 @@
 ---
-title: Manage Jar dependencies best practice for Azure HDInsight 
-description: Best practice of how to manage Jar dependencies for HDInsight applications safely.
+title: Manage JAR dependencies - Azure HDInsight  
+description: This article discusses best practices for managing Java Archive (JAR) dependencies for HDInsight applications.
 author: hrasheed-msft
 ms.author: hrasheed
 ms.reviewer: jasonh
@@ -10,24 +10,24 @@ ms.topic: conceptual
 ms.date: 02/05/2020
 ---
 
-# Jar dependency management best practice
+# JAR dependency management best practices
 
-Components in HDInsight cluster have dependencies on third-party libraries. Usually, a specific version of common modules like Guava is referenced by these built-in components. When customers submit an application with its dependencies, they can bring a conflict version of the same module. If customer’s version is in the classpath first, built-in components may throw exceptions because of version incompatibility. While if built-in components inject the dependency to classpath first, customer’s application may throw errors like NoSuchMethod.
+Components installed on HDInsight clusters have dependencies on third-party libraries. Usually, a specific version of common modules like Guava is referenced by these built-in components. When you submit an application with its dependencies, it can cause a conflict between different versions of the same module. If the component version that you reference in the classpath first, built-in components may throw exceptions because of version incompatibility. However, if built-in components inject their dependencies to the classpath first, your application may throw errors like `NoSuchMethod`.
 
 To avoid version conflict, consider shading your application dependencies.
 
 ## What does package shading mean?
 Shading provides a way to include and rename dependencies. It relocates the classes and rewrites affected bytecode and resources to create a private copy of your dependencies.
 
-## How to shade package?
+## How to shade a package?
 
 ### Use uber-jar
-Uber-jar is a single jar file that contains both the application jar and its dependencies. The dependencies in Uber-jar are by-default not shaded. In some cases, this may introduce version conflict if other components or applications reference a different version of those libraries. To avoid this, customer can build Uber-Jar file with some (or all) of their dependencies shaded.
+Uber-jar is a single jar file that contains both the application jar and its dependencies. The dependencies in Uber-jar are by-default not shaded. In some cases, this may introduce version conflict if other components or applications reference a different version of those libraries. To avoid this, you can build an Uber-Jar file with some (or all) of the dependencies shaded.
 
 ### Shade package using Maven
 Maven can build applications written both in Java and Scala. Maven-shade-plugin can help you create a shaded uber-jar easily.
 
-Below example in `pom.xml` shows how to shade package using maven-shade-plugin. `<relocation>…</relocation>` moves classes from package `com.google.guava` into package `com.google.shaded.guava` by moving the corresponding JAR file entries and rewriting the affected bytecode.
+The example below shows a file `pom.xml` which has been updated to shade a package using maven-shade-plugin.  The XML section `<relocation>…</relocation>` moves classes from package `com.google.guava` into package `com.google.shaded.guava` by moving the corresponding JAR file entries and rewriting the affected bytecode.
 
 After changing `pom.xml`, you can execute `mvn package` to build the shaded uber-jar.
 
@@ -61,7 +61,8 @@ After changing `pom.xml`, you can execute `mvn package` to build the shaded uber
 
 ### Shade package using SBT
 SBT is also a build tool for Scala and Java. SBT doesn't have a shade plugin like maven-shade-plugin. You can modify `build.sbt` file to shade packages. 
-For example, to shade `com.google.guava`, you can add below command to `build.sbt` file:
+
+For example, to shade `com.google.guava`, you can add the below command to the `build.sbt` file:
 
 ```scala
 assemblyShadeRules in assembly := Seq(
@@ -70,3 +71,9 @@ assemblyShadeRules in assembly := Seq(
 ```
 
 Then you can run `sbt clean` and `sbt assembly` to build the shaded jar file. 
+
+## Next steps
+
+* [Use HDInsight IntelliJ Tools](https://docs.microsoft.com/azure/hdinsight/hadoop/hdinsight-tools-for-intellij-with-hortonworks-sandbox)
+
+* [Create a Scala Maven application for Spark in IntelliJ](https://docs.microsoft.com/azure/hdinsight/spark/apache-spark-create-standalone-application)