Update plugins.adoc

Author: stefano-ottolenghi

modules/ROOT/pages/kubernetes/plugins.adoc

@@ -86,7 +86,7 @@ This way, you can ensure when building the container that the correct plugin ver
 [NOTE]
 ====
 link:link:{neo4j-download-center-uri}?bloom[The Neo4j Bloom] plugin requires a license activation key, which needs to be placed in a directory accessible by the Neo4j Docker container, for example, mounted to _/licenses_ (default).
-To obtain a valid license, reach out to your Neo4j account representative or use the form https://neo4j.com/contact-us//[Contact Neo4j].
+To obtain a valid license, reach out to your Neo4j account representative or use the form https://neo4j.com/contact-us/[Contact Neo4j].
 ====
 
 Building a Docker container image that is based on the official Neo4j Docker image and does not override the official image's `ENTRYPOINT` and `COMMAND` is the recommended method to use with the Neo4j Helm chart, as shown in this example Dockerfile:
@@ -137,7 +137,7 @@ With this method, the plugin jar files are stored on a Persistent Volume that is
 [NOTE]
 ====
 link:https://neo4j.com/deployment-center/?bloom[The Neo4j Bloom] plugin requires a license activation key, which needs to be placed in a directory accessible by the Neo4j Docker container, for example, mounted to _/licenses_ (default).
-To obtain a valid license, reach out to your Neo4j account representative or use the form https://neo4j.com/contact-us//[Contact Neo4j].
+To obtain a valid license, reach out to your Neo4j account representative or use the form https://neo4j.com/contact-us/[Contact Neo4j].
 ====
 
 The simplest way to set up a persistent `plugins` volume is to share the Persistent Volume that is used for storing Neo4j data.