Looks fine to me.
P.S. Looks like your doccheck has already started to pay off.
> On 15 Nov 2018, at 00:01, Jonathan Gibbons <jonathan.gibb...@oracle.com>
> wrote:
>
> Please review the removal of two extraneous </a> in HttpClient.java.
>
> $ hg diff -R open
> diff -r 40098289d580
> src/java.net.http/share/classes/java/net/http/HttpClient.java
> --- a/src/java.net.http/share/classes/java/net/http/HttpClient.java Wed Nov
> 14 12:25:15 2018 -0800
> +++ b/src/java.net.http/share/classes/java/net/http/HttpClient.java Wed Nov
> 14 15:56:04 2018 -0800
> @@ -104,7 +104,7 @@
> * .thenApply(HttpResponse::body)
> * .thenAccept(System.out::println); }</pre>
> *
> - * <p> <a id="securitychecks"></a><b>Security checks</b></a>
> + * <p> <a id="securitychecks"><b>Security checks</b></a>
> *
> * <p> If a security manager is present then security checks are performed by
> * the HTTP Client's sending methods. An appropriate {@link URLPermission} is
> @@ -327,7 +327,7 @@
> * then newly built clients will use the {@linkplain
> * ProxySelector#getDefault() default proxy selector}, which is
> usually
> * adequate for client applications. The default proxy selector
> supports
> - * a set of system properties</a> related to
> + * a set of system properties related to
> * <a
> href="{@docRoot}/java.base/java/net/doc-files/net-properties.html#Proxies">
> * proxy settings</a>. This default behavior can be disabled by
> * supplying an explicit proxy selector, such as {@link #NO_PROXY} or
>
>
> JBS: https://bugs.openjdk.java.net/browse/JDK-8213910
>
> -- Jon
>
