Correct ssl-target-name-overrides for peers in connection profile ref…

…erence docs (#4470) Signed-off-by: Björn Tegelund <[email protected]>
hyperledger-archives · Oct 29, 2018 · 5f63223 · 5f63223
1 parent 76fe7ba
commit 5f63223
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/packages/composer-website/jekylldocs/reference/connectionprofile.md b/packages/composer-website/jekylldocs/reference/connectionprofile.md
@@ -164,7 +164,7 @@ Peer definitions are similar to orderer definitions in structure.
     "peer0.org1.example.com": {
         "url": "grpc://peer0.org1.example.com:7051",
         "grpcOptions": {
-            "ssl-target-name-override": "peer.org1.example.com"
+            "ssl-target-name-override": "peer0.org1.example.com"
         },
         "tlsCACerts": {
             "pem": "-----BEGIN CERTIFICATE----- <etc> "
@@ -306,7 +306,7 @@ For example a peer definition might look like:
 "peer0.org1.example.com": {
     "url": "grpcs://peer0.org1.example.com:7051",
     "grpcOptions": {
-        "ssl-target-name-override": "peer.org1.example.com",
+        "ssl-target-name-override": "peer0.org1.example.com",
         "grpc.keepalive_time_ms": 600000,
         "grpc.max_send_message_length": 15728640,
         "grpc.max_receive_message_length": 15728640