iSharkFly-Docs
/
opensearch-docs-cn
mirror of https://github.com/iSharkFly-Docs/opensearch-docs-cn
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Language tweaks 

Signed-off-by: keithhc2 <keithhc2@users.noreply.github.com>
This commit is contained in:
keithhc2 2021-12-09 11:18:01 -08:00
parent 0ab79cbdb6
commit 8d1dfa5040
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_clients/java-rest-high-level.md
View File

@ -27,7 +27,7 @@ You can now start your OpenSearch cluster. The OpenSearch 1.x high-level REST cl
This code example uses basic credentials that come with the default OpenSearch configuration. If you’re using the OpenSearch Java high-level REST client with your own OpenSearch cluster, be sure to change the code to use your own credentials.
{: .note}
Before you can securely connect to an OpenSearch cluster, you need to first add your root certificates to a truststore:
Before you can securely connect to an OpenSearch cluster, you must first add your root certificates to a truststore. If you don't already have a custom truststore, the following command creates a truststore and adds in a certificate.
```bash
keytool -import <path-to-cert> -alias <alias-to-call-cert> -keystore <truststore-name>

2
_clients/java.md
View File

@ -46,7 +46,7 @@ You can now start your OpenSearch cluster.
This code example uses basic credentials that come with the default OpenSearch configuration. If you’re using the OpenSearch Java client with your own OpenSearch cluster, be sure to change the code to use your own credentials.
{: .note}
Before you can securely connect to an OpenSearch cluster, you need to first add your root certificates to a truststore:
Before you can securely connect to an OpenSearch cluster, you must first add your root certificates to a truststore. If you don't already have a custom truststore, the following command creates a truststore and adds in a certificate.
```bash
keytool -import <path-to-cert> -alias <alias-to-call-cert> -keystore <truststore-name>