java: fixes from the CI bots

java/ql/test/query-tests/ThreadSafe/examples/LockExample.java

@@ -3,7 +3,7 @@
 // If the variable is involved in several different monitors, we get an alert for each monitor that
 // is not correctly used.
 // A single alert can have many related locations, since each conflicting access which is not
-// prpoerly synchronized is a related location.
+// properly synchronized is a related location.
 // This leads to many lines in the .expected file.
 package examples;
 

java/ql/test/query-tests/ThreadSafe/examples/Test.java

@@ -5,14 +5,14 @@ import java.util.concurrent.locks.ReentrantLock;
 @ThreadSafe
 public class Test {
   /**
-   * Escaping field due to public visuability.
+   * Escaping field due to public visibility.
    */
   int publicField;
   
   private int y;
   final int immutableField = 1;
 
-  // As of the below examples with synchronized as well. Except the incorretly placed lock.
+  // As of the below examples with synchronized as well. Except the incorrectly placed lock.
 
   private Lock lock = new ReentrantLock();
 
@@ -53,7 +53,7 @@ public class Test {
   }
 
   /**
-   * Incorretly locks y.
+   * Incorrectly locks y.
    * @param y
    */
   public void setYWrongLock(int y) {