Fix a misleading word in containers/images.md#12553
Fix a misleading word in containers/images.md#12553k8s-ci-robot merged 2 commits intokubernetes:masterfrom
Conversation
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit 28b7576 https://deploy-preview-12553--kubernetes-io-master-staging.netlify.com |
|
Netlify preview for the changed section. |
|
Isn't base64 decoded more appropriate here? |
b40a6d0 to
28b7576
Compare
|
@rlenferink Thank you for the comment. I think you are right. I was confused. I updated PR as follows, |
|
This reads better and is easier to comprehend. I checked the preview and it looks good as well. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bradtopol The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Fix a misleading word in containers/images.md * Rev Fix a misleading word in containers/images.md
* Fix a misleading word in containers/images.md * Rev Fix a misleading word in containers/images.md
* Fix a misleading word in containers/images.md * Rev Fix a misleading word in containers/images.md
This PR update a minor misleading word in concepts/containers/images.md
(un-base64 encoded -> base64 decoded)
In https://kubernetes.io/docs/concepts/containers/images/#bypassing-kubectl-create-secrets ,
there is a sentence with "un-base64 encoded".
I updated PR as follows,
it means the data was successfully un-base64 encoded
->
it means the base64 encoded string in the data was successfully decoded