Nits and docs improvements

Author: alexsa

core/src/main/java/com/datastax/oss/driver/internal/core/addresstranslation/SubnetAddressTranslator.java

@@ -192,7 +192,6 @@ private static IPAddress parseSubnet(String subnetCIDR) {
         throw new IllegalArgumentException("Invalid subnet: " + subnetCIDR);
       }
       if (!subnet.isPrefixBlock()) {
-
         throw new IllegalArgumentException(
             String.format(
                 "Subnet %s must be represented as a network prefix block %s",

core/src/main/resources/reference.conf

@@ -1028,7 +1028,7 @@ datastax-java-driver {
     # The driver provides the following implementations out of the box:
     # - PassThroughAddressTranslator: returns all addresses unchanged.
     # - FixedHostNameAddressTranslator: translates all addresses to a specific hostname.
-    # - SubnetAddressTranslator: translates addresses to hostname based on the subnet matches.
+    # - SubnetAddressTranslator: translates addresses to hostname based on the subnet match.
     # - Ec2MultiRegionAddressTranslator: suitable for an Amazon multi-region EC2 deployment where
     #   clients are also deployed in EC2. It optimizes network costs by favoring private IPs over
     #   public ones whenever possible.
@@ -1048,7 +1048,7 @@ datastax-java-driver {
     #   # "::ffff:6440:0/111" = "cassandra.datacenter1.com:9042"
     #   # "::ffff:6442:0/111" = "cassandra.datacenter2.com:9042"
     # }
-    # Optional. When configured, addresses not matching the configured subnets are translated this address.
+    # Optional. When configured, addresses not matching the configured subnets are translated to this address.
     # default-address = "cassandra.datacenter1.com:9042"
     # Note: `advanced.resolve-contact-points` (see below) is used to determine whether to resolve subnet
     # and default address on translation. 

manual/core/address_resolution/README.md

@@ -139,8 +139,8 @@ proxy, we have an option to use `FixedHostNameAddressTranslator`. But for multi-
 want to have more control over routing queries to a specific datacenter (eg. for optimizing latencies), which requires
 setting up a separate proxy per datacenter.
 
-Normally, each Cassandra datacenter nodes are deployed to a separate subnet to support internode communications in the
-cluster and avoid IP addresses collisions. So when Cassandra broadcasts its nodes IP addresses, we can determine which
+Normally, each Cassandra datacenter nodes are deployed to a different subnet to support internode communications in the
+cluster and avoid IP address collisions. So when Cassandra broadcasts its nodes IP addresses, we can determine which
 datacenter that node belongs to by checking its IP address against the given datacenter subnet.
 
 For such scenarios you can use `SubnetAddressTranslator` to translate node IPs to the datacenter proxy address
@@ -152,13 +152,15 @@ datastax-java-driver.advanced.address-translator {
   class = SubnetAddressTranslator
   subnet-addresses {
     "100.64.0.0/15" = "cassandra.datacenter1.com:9042"
-    "100.66.0.0/15" = "cassandra.datacenter2.com"  # port defaults to 9042 if not specified
+    "100.66.0.0/15" = "cassandra.datacenter2.com:9042"
     # IPv6 example:
     # "::ffff:6440:0/111" = "cassandra.datacenter1.com:9042"
-    # "::ffff:6442:0/111" = "cassandra.datacenter2.com"  # port defaults to 9042 if not specified
+    # "::ffff:6442:0/111" = "cassandra.datacenter2.com:9042"
   }
-  # Optional. When configured, addresses not matching the configured subnets are translated to it. Port defaults to 9042 if not specified.
+  # Optional. When configured, addresses not matching the configured subnets are translated to this address.
   default-address = "cassandra.datacenter1.com:9042"
+  # Note: `advanced.resolve-contact-points` is used to determine whether to resolve subnet and default address
+  # on translation.
 }
 ```