Minor javadoc fixes

Author: adutra

core/src/main/java/com/datastax/oss/driver/api/core/connection/BusyConnectionException.java

@@ -25,7 +25,7 @@
  * requests.
  *
  * <p>This might happen under heavy load. The driver will automatically try the next node in the
- * query plan. Therefore the only way that the client can observe this exception is as part of a
+ * query plan. Therefore, the only way that the client can observe this exception is as part of a
  * {@link AllNodesFailedException}.
  */
 public class BusyConnectionException extends DriverException {

core/src/main/java/com/datastax/oss/driver/internal/core/adminrequest/AdminRequestHandler.java

@@ -47,7 +47,7 @@
 import org.slf4j.Logger;
 import org.slf4j.LoggerFactory;
 
-/** Handles the lifecyle of an admin request (such as a node refresh or schema refresh query). */
+/** Handles the lifecycle of an admin request (such as a node refresh or schema refresh query). */
 @ThreadSafe
 public class AdminRequestHandler<ResultT> implements ResponseCallback {
   private static final Logger LOG = LoggerFactory.getLogger(AdminRequestHandler.class);

core/src/main/java/com/datastax/oss/driver/internal/core/pool/ChannelPool.java

@@ -143,7 +143,6 @@ public boolean isInvalidKeyspace() {
    *     request path, and we want to avoid complex check-then-act semantics; therefore this might
    *     race and return a channel that is already closed, or {@code null}. In those cases, it is up
    *     to the caller to fail fast and move to the next node.
-   *     <p>There is no need to return the channel.
    */
   public DriverChannel next() {
     return channels.next();