Remove monospace formatting inside link text

russcam · russcam · commit 49b788b13bd3 · 2018-01-10T22:37:59.000+11:00
AsciiDocNet incorrectly parses this
diff --git a/docs/client-concepts/certificates/working-with-certificates.asciidoc b/docs/client-concepts/certificates/working-with-certificates.asciidoc
@@ -80,7 +80,7 @@ public class AllowAllCertificatesCluster : SslAndKpiXPackCluster
 If your client application has access to the public CA certificate locally, Elasticsearch.NET and NEST ship with some handy helpers
 that can assert that a certificate the server presents is one that came from the local CA.
 
-If you use X-Pack's {ref_current}/certutil.html`certutil` tool] to generate SSL certificates, the generated node certificate
+If you use X-Pack's {ref_current}/certutil.html[certutil tool] to generate SSL certificates, the generated node certificate
 does not include the CA in the certificate chain, in order to cut down on SSL handshake size. In those case you can use`CertificateValidations.AuthorityIsRoot` and pass it your local copy of the CA public key to assert that
 the certificate the server presented was generated using it
 
diff --git a/src/Tests/ClientConcepts/Certificates/WorkingWithCertificates.doc.cs b/src/Tests/ClientConcepts/Certificates/WorkingWithCertificates.doc.cs
@@ -110,7 +110,7 @@ public AllowAllSslCertificatesApiTests(AllowAllCertificatesCluster cluster, Endp
 		 * If your client application has access to the public CA certificate locally, Elasticsearch.NET and NEST ship with some handy helpers
 		 * that can assert that a certificate the server presents is one that came from the local CA.
 		 *
-		 * If you use X-Pack's {ref_current}/certutil.html[`certutil` tool] to generate SSL certificates, the generated node certificate
+		 * If you use X-Pack's {ref_current}/certutil.html[certutil tool] to generate SSL certificates, the generated node certificate
 		 * does not include the CA in the certificate chain, in order to cut down on SSL handshake size. In those case you can use
 		 * `CertificateValidations.AuthorityIsRoot` and pass it your local copy of the CA public key to assert that
 		 * the certificate the server presented was generated using it

Original file line number	Diff line number	Diff line change
`@@ -110,7 +110,7 @@ public AllowAllSslCertificatesApiTests(AllowAllCertificatesCluster cluster, Endp`
`110`	`110`	`* If your client application has access to the public CA certificate locally, Elasticsearch.NET and NEST ship with some handy helpers`
`111`	`111`	`* that can assert that a certificate the server presents is one that came from the local CA.`
`112`	`112`	`*`
`113`		- * If you use X-Pack's {ref_current}/certutil.html[`certutil` tool] to generate SSL certificates, the generated node certificate
	`113`	`+ * If you use X-Pack's {ref_current}/certutil.html[certutil tool] to generate SSL certificates, the generated node certificate`
`114`	`114`	`* does not include the CA in the certificate chain, in order to cut down on SSL handshake size. In those case you can use`
`115`	`115`	* `CertificateValidations.AuthorityIsRoot` and pass it your local copy of the CA public key to assert that
`116`	`116`	`* the certificate the server presented was generated using it`