Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos in Trino Kubernetes install docs #15523

Merged
merged 1 commit into from
Dec 23, 2022
Merged

Fix typos in Trino Kubernetes install docs #15523

merged 1 commit into from
Dec 23, 2022

Conversation

Erzangel
Copy link
Contributor

Description

Fixing small typos in the documentation of the Trino Kubernetes install with Helm, as well as a wrong Kubernetes label in the query example

Additional context and related issues

Simply a docs-related PR which I noticed while deploying Trino in my Kubernetes cluster

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot
Copy link

cla-bot bot commented Dec 23, 2022

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to cla@trino.io. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@github-actions github-actions bot added the docs label Dec 23, 2022
@ebyhr ebyhr merged commit 7123e2f into trinodb:master Dec 23, 2022
@github-actions github-actions bot added this to the 404 milestone Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants