Bob Ward feedback

Author: HeidiSteen

docs/advanced-analytics/java/java-first-sample.md

@@ -220,7 +220,7 @@ Grant 'Read and Execute' permissions to **SQLRUserGroup** and the **All applicat
    + Click **Object Types** and make sure *Built-in security principles* and *Groups* are selected.
    + Click **Locations** to select the local computer name at the top of the list.
 5. Enter **SQLRUserGroup**, check the name, and then click OK to add the group.
-6. Enter **all application packages**, check the name, and then click OK to add. If the name doesn't resolve, revisit the Locations step. The SID is local to your machine.
+6. Enter **ALL APPLCIATION PACKAGES**, check the name, and then click OK to add. If the name doesn't resolve, revisit the Locations step. The SID is local to your machine.
 
 Make sure both security identities have 'Read and Execute' permissions on the folder and "pkg" subfolder.
 
@@ -262,7 +262,14 @@ After executing the call, you should get a result set showing the two columns:
 
 ![Results from Java sample](../media/java/java-sample-results.png "Sample results")
 
-If you get an error, check classpath. The path should include a "pkg" subfolder containing the compiled code. The parent folder, not the "pkg" subfolder, should be in classpath. The length of classpath cannot exceed the declared value (`DECLARE @myClassPath nvarchar(50)`). If it does, the path is truncated to the first 50 characters and your compiled code will not be loaded. You can increase the length if 50 characters is insufficinent. Finally, check permissions on each folder, from root to "pkg" subfolder, to ensure that the security identities running the external process have permission to read and execute your code.
+## If you get an error
+
+Rule out any issues related to the classpath. 
+
++ Classpath should consist of the parent folder and any subfolders, but not the "pkg" subfolder. While the pkg subfolder must exist, it's not supposed to be in classpath value specified in the stored procedure.
++ The "pkg" subfolder should contain the compiled code for all three classes.
++ The length of classpath cannot exceed the declared value (`DECLARE @myClassPath nvarchar(50)`). If it does, the path is truncated to the first 50 characters and your compiled code will not be loaded. You can do a `SELECT @myClassPath` to check the value. Increase the length if 50 characters is insufficient. 
++ Finally, check permissions on *each* folder, from root to "pkg" subfolder, to ensure that the security identities running the external process have permission to read and execute your code.
 
 ## See also