Update Java lab

labs/java/mavenpmvsts/readme.md

@@ -10,7 +10,7 @@ In this exercise, you are going to set up package management with Maven in VSTS.
 
 This exercise assumes you have completed the exercises to create a Team Project, have set up the Docker private VSTS agent, and imported the MyShuttleCalc and MyShuttle2 GitHub repos into your VSTS team project. This exercise also assumes that you have cloned the repos in either IntelliJ or Eclipse. This exercise uses a team project named **jdev-labs**, though your team project name may differ.
 
-{% include note.html content="This exercise shows how to do a Maven build using VSTS. To see how to perform a Maven build using Jenkins that still integrates into the VSTS Package Feed, please refer to the [**Maven Package Management with Jenkins**](../mavenpmjenkins) lab %}
+{% include note.html content="This exercise shows how to do a Maven build using VSTS. To see how to perform a Maven build using Jenkins that still integrates into the VSTS Package Feed, please refer to the [**Maven Package Management with Jenkins**](../mavenpmjenkins) lab" %}
 
 ## Create a Maven Package Feed
 
@@ -148,4 +148,4 @@ In this task you will create a build that will publish the MyShuttleCalc library
 
 1. Navigate back to the Maven package feed. There you will see the MyShuttleCalc package.
 
-    ![The MyShuttleCalc package in the feed](images/package-in-feed.png)
+    ![The MyShuttleCalc package in the feed](images/package-in-feed.png)

labs/java/settingvstsproject/readme.md

@@ -33,7 +33,7 @@ In this task you will generate a Personal access token for yourself. PATs essent
 
 1. On the Personal access tokens page, click **Add**. Enter "java" (or whatever you want) for the *Description*. Scroll to the bottom of the page and click **Create token**.
 
-1. When the token is created, make a note of it as it cannot viewed again. Copy it from the browser into the clipboard.
+1. When the token is created, make a note of it as it cannot be viewed again. Copy it from the browser into the clipboard.
 
 1. Click on the Visual Studio Code icon in the toolbar to open Visual Studio Code.
 
@@ -93,4 +93,4 @@ If you have not provisioned the team project using the VSTS demo generator in th
 
    {% include note.html content="It is not necessary to clone GitHub repos into the VSTS. VSTS will work just fine with GitHub (or other Git hoster) repos. However, some linkages from source code to other aspects of the DevOps pipeline (such as work items, builds or releases) works best if the code is in VSTS" %}
 
-You have now created the project and ready to move to the next exercise [**Setting up a CI/CD private agent**](../dockerbuildagent/)
+You have now created the project and ready to move to the next exercise [**Setting up a CI/CD private agent**](../dockerbuildagent/)