Fix JavaDoc formatting

Author: jarrodcodes

src/main/java/com/bettercloud/vault/VaultConfig.java

@@ -60,10 +60,10 @@ public class VaultConfig implements Serializable {
      * constructing a <code>VaultConfig</code> instance using the builder pattern approach rather than the convenience
      * constructor.  This method's access level was therefore originally set to <code>protected</code>, but was bumped
      * up to <code>public</code> due to community request for the ability to disable environment loading altogether
-     * (see https://github.com/BetterCloud/vault-java-driver/issues/77).
-     * <p>
-     * Note that if you do override this, however, then obviously all of the environment checking discussed in the
-     * documentation becomes disabled.
+     * (see https://github.com/BetterCloud/vault-java-driver/issues/77).</p>
+     *
+     * <p>Note that if you do override this, however, then obviously all of the environment checking discussed in the
+     * documentation becomes disabled.</p>
      *
      * @param environmentLoader An environment variable loader implementation (presumably a mock)
      * @return This object, with environmentLoader populated, ready for additional builder-pattern method calls or else finalization with the build() method

src/test-integration/java/com/bettercloud/vault/api/LeasesTests.java

@@ -29,7 +29,7 @@
  * <p>In the future, we may be shifting to an integration testing approach that uses a "real" Vault server
  * instance, running in a Docker container (see: https://github.com/BetterCloud/vault-java-driver/pull/25).  At
  * that time, these tests should be re-visited and better implemented.</p>
- * <p>
+ *
  * TODO:  Revisit, now that we're using testcontainers
  */
 public class LeasesTests {

src/test-integration/java/com/bettercloud/vault/util/VaultContainer.java

@@ -90,10 +90,10 @@ public Statement apply(final Statement base, final Description description) {
      * when placed inside of the constructor or {@link this#apply(Statement, Description)} methods here, presumably
      * because the Docker container spawned by TestContainers is not ready to accept commonds until after those
      * methods complete.
-     * <p>
-     * This method initializes the Vault server, capturing the unseal key and root token that are displayed on the
+     *
+     * <p>This method initializes the Vault server, capturing the unseal key and root token that are displayed on the
      * console.  It then uses the key to unseal the Vault instance, and stores the token in a member field so it
-     * will be available to other methods.
+     * will be available to other methods.</p>
      *
      * @throws IOException
      * @throws InterruptedException