You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@flink.apache.org by sn...@apache.org on 2023/09/12 12:21:59 UTC
[flink] branch master updated: [hotfix][docs] Misprints in security-ssl.md (#23400)
This is an automated email from the ASF dual-hosted git repository.
snuyanzin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new 45f26c7a434 [hotfix][docs] Misprints in security-ssl.md (#23400)
45f26c7a434 is described below
commit 45f26c7a43481b9abc63be1e0853a96ddca9c0d6
Author: Sergey Nuyanzin <sn...@gmail.com>
AuthorDate: Tue Sep 12 14:21:51 2023 +0200
[hotfix][docs] Misprints in security-ssl.md (#23400)
---
docs/content.zh/docs/deployment/security/security-ssl.md | 4 ++--
docs/content/docs/deployment/security/security-ssl.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/content.zh/docs/deployment/security/security-ssl.md b/docs/content.zh/docs/deployment/security/security-ssl.md
index 49350ffae88..60ce3b2c677 100644
--- a/docs/content.zh/docs/deployment/security/security-ssl.md
+++ b/docs/content.zh/docs/deployment/security/security-ssl.md
@@ -113,7 +113,7 @@ need to be set up such that the truststore trusts the keystore's certificate.
Because internal communication is mutually authenticated between server and client side, keystore and truststore typically refer to a dedicated
certificate that acts as a shared secret. In such a setup, the certificate can use wild card hostnames or addresses.
-WHen using self-signed certificates, it is even possible to use the same file as keystore and truststore.
+When using self-signed certificates, it is even possible to use the same file as keystore and truststore.
```yaml
security.ssl.internal.keystore: /path/to/file.keystore
@@ -171,7 +171,7 @@ If these cipher suites are not supported on your setup, you will see that Flink
## Creating and Deploying Keystores and Truststores
-Keys, Certificates, and the Keystores and Truststores can be generatedd using the [keytool utility](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html).
+Keys, Certificates, and the Keystores and Truststores can be generated using the [keytool utility](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html).
You need to have an appropriate Java Keystore and Truststore accessible from each node in the Flink cluster.
- For standalone setups, this means copying the files to each node, or adding them to a shared mounted directory.
diff --git a/docs/content/docs/deployment/security/security-ssl.md b/docs/content/docs/deployment/security/security-ssl.md
index 64ba8f8d210..17795dfbf6f 100644
--- a/docs/content/docs/deployment/security/security-ssl.md
+++ b/docs/content/docs/deployment/security/security-ssl.md
@@ -113,7 +113,7 @@ need to be set up such that the truststore trusts the keystore's certificate.
Because internal communication is mutually authenticated between server and client side, keystore and truststore typically refer to a dedicated
certificate that acts as a shared secret. In such a setup, the certificate can use wild card hostnames or addresses.
-WHen using self-signed certificates, it is even possible to use the same file as keystore and truststore.
+When using self-signed certificates, it is even possible to use the same file as keystore and truststore.
```yaml
security.ssl.internal.keystore: /path/to/file.keystore
@@ -171,7 +171,7 @@ If these cipher suites are not supported on your setup, you will see that Flink
## Creating and Deploying Keystores and Truststores
-Keys, Certificates, and the Keystores and Truststores can be generatedd using the [keytool utility](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html).
+Keys, Certificates, and the Keystores and Truststores can be generated using the [keytool utility](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html).
You need to have an appropriate Java Keystore and Truststore accessible from each node in the Flink cluster.
- For standalone setups, this means copying the files to each node, or adding them to a shared mounted directory.