@@ -71,12 +71,11 @@ disk which is used to sign the certificates for the HTTP layer of the {es}
7171cluster.
7272
7373In order for the client to establish a connection with the cluster over HTTPS,
74- the CA certificate must be trusted by the client application. There are several
75- mechanisms for <<working-with-certificates, working with certificates>>, but the
76- simplest choice is to use the hex-encoded SHA-256 fingerprint of the CA
77- certificate. The CA fingerprint is output to the terminal when you start {es}
78- for the first time. You'll see a distinct block like the one
79- below in the output from {es} (you may have to scroll up if it's been a while):
74+ the CA certificate must be trusted by the client application. The simplest
75+ choice is to use the hex-encoded SHA-256 fingerprint of the CA certificate. The
76+ CA fingerprint is output to the terminal when you start {es} for the first time.
77+ You'll see a distinct block like the one below in the output from {es} (you may
78+ have to scroll up if it's been a while):
8079
8180```sh
8281----------------------------------------------------------------
@@ -144,9 +143,7 @@ nodes for each request in a round robin fashion. The client also tracks
144143unhealthy nodes and avoids sending requests to them until they become healthy.
145144
146145This configuration is best suited to connect to a known small sized cluster,
147- where you do not require sniffing to detect the cluster topology. Refer to the
148- <<connection-pooling,node pool documentation>> for more information about the
149- types of node pool available in the {es} .NET client.
146+ where you do not require sniffing to detect the cluster topology.
150147
151148The following snippet shows you how to connect to multiple nodes by using a
152149static node pool:
0 commit comments