Merge pull request #26474 from shahincsejnu/master
fixed some typos and grammatical mistakes
This commit is contained in:
@@ -28,7 +28,7 @@ a private certificate authority (CA), or based on a public key infrastructure li
|
||||
to a generally recognized CA.
|
||||
|
||||
If your cluster uses a private certificate authority, you need a copy of that CA
|
||||
certifcate configured into your `~/.kube/config` on the client, so that you can
|
||||
certificate configured into your `~/.kube/config` on the client, so that you can
|
||||
trust the connection and be confident it was not intercepted.
|
||||
|
||||
Your client can present a TLS client certificate at this stage.
|
||||
@@ -135,7 +135,7 @@ for the corresponding API object, and then written to the object store (shown as
|
||||
The previous discussion applies to requests sent to the secure port of the API server
|
||||
(the typical case). The API server can actually serve on 2 ports:
|
||||
|
||||
By default the Kubernetes API server serves HTTP on 2 ports:
|
||||
By default, the Kubernetes API server serves HTTP on 2 ports:
|
||||
|
||||
1. `localhost` port:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user